New firmwares will be added to this page as they're released.  To submit bug reports and features requests, please submit a ticket on this portal.


Latest stable n/a
Latest beta v1.12.2, beta-4 

Version 1.12.2 (beta-4)


This is a service release targeting the new model TNA-303L-65.  beta-4 is expected to be the final beta and will be promoted to stable in August or September.


Changes (TNA-303L-X-beta-4, rev 7663) 7/28/25:

  1. Fixed the ethernet link status LED.
  2. Fixed a bug related to PTP mode (see known issue #5 below).
  3. Other misc improvements.


Changes (TNA-303L-X-beta-3, rev 7620) 7/8/25:

  1. Internal speedtest results are now accurate in both TX and RX directions. 
  2. A bug has been fixed which prevented network settings from taking affect when changing from DHCP static to client mode, without changing any other settings. 
  3. Fixed the site survey and temp channel change actions on the 303L.
  4. Fixed a web UI issue where a missing or misconfigured 60GHz radio caused the dashboard to show a system/internal error.  


Changes (TNA-303L-X-beta-2, rev 7613) 6/24/25:

  1. Added support for the 2.4GHz Mediatek MT7610U USB Wi-Fi dongle for device management.  Once inserted, the 2.4GHz radio will come up with an SSID of tachyon-mgmt<last 3 octets of eth0 mac> and can be access with the passphrase 00000000 at 192.168.5.1.  Any clients will get a DHCP address within the 192.168.5.x range.
  2. Added significant throughput increases when data VLAN is enabled.  Non-data VLAN modes are also accelerated.


Known issues (TNA-303L-X):

  1. Internal speed test results are not currently accurate on the 303L-65. [Fixed in beta-3]
  2. Site survey and temp channel change are currently not working for the 303L-65.  [Fixed in beta-3]
  3. Traffic control limits for the 303L-65 no longer function.  [Present in beta-2 and later]
  4. Ethernet status LED is not currently functioning on the 303L-65.  This will be addressed in the final firmware release. [Fixed in beta-4]
  5. PTP slave mode is not being set correctly internally.  A client configured as PTP slave will still connect to a PTP master, but it will not be optimized. This will be addressed in the final firmware release. [Fixed in beta-4]