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. Archived firmwares can be found on the TNA-300 series firmwares archive page.


These firmwares are applicable to all TNA models: TNA-301, TNA-302, TNA-303X.


Latest stable version  v1.12.0
Latest beta version  n/a

Version 1.12.X Firmwares


Version 1.12.0 Sept 6, 2024:


This is a major version release that includes wireless driver improvements and the other new features listed below.  Please read the full release notes carefully before upgrading.


Important notes about 1.12.0:  

  • If using half channels only, v1.12.0 will NOT be compatible with v1.11.x. In this case, update your stations first!

  • Beta-2 and later have important changes that address critical security vulnerabilities reported by @semaja2.  A full report will be released in the upcoming months, so please make sure your units are updated to the latest beta or stable firmware!

  • After upgrading to this version, a new IP address called the alternative local IP will be created on the data bridge.  It is set to 169.254.1.1. by default and can be disabled it from the Network-> Device management & VLANs configuration tab. It is only accessible over the wired interfaces, however, if you'd like a version of the firmware where this IP is disabled please contact support.

  • The wireless driver has been updated with some optimizations and stability fixes.  Once you upgrade your devices, the radio modem firmware will be flashed after bootup.  This process takes around 5 or 10 seconds, during which all LEDs will be fast flashing.

  • Devices running older 1.11.x firmwares will link successfully with 1.12.x firmwares (unless you're using half channels), but we still recommend updating both sides of your links.  Configurations between these two versions are also compatible.


Known issues:

  1. Disabling data on the eth1 port works once initially applied, but does not remain disabled after a reboot.  This will be fixed in a later service release - if you need it sooner, please contact support@tachyon-networks.com. This bug is present in all previous firmwares as well.

  2. Websockets can randomly stop working in the web UI - this breaks certain features such as speedtest, the aiming tool, and some stats.  We're working on a fix for this on a future version.  To work around this for now, you can restart the webserver from the Services config page.

  3. SNMP sysUpTime is incorrect at bootup and will only show the correct value once the snmp service is restarted (this will happen if you disable/enable SNMP, or change some other settings which will trigger it to reload).  If you need a fix for this ASAP, it is available in a hotfix version which can be requested from the support team.

Changes (final, revision 54573) 9/6/24:

  1. SNMP: Expose peer name, model, and antenna kit in the wireless peers lists.  The MIB has been updated here.
  2. Fix memory leak in the wireless driver when 20+ stations are connected.
  3. Add support for the AK-150 antenna kit.
  4. Minor UI fixes were added.


Changes (beta-3, revision 54564) 8/9/24:

  1. The 60GHz wireless driver has been updated to better handle edge-case connection issues.
  2. We have added "config test mode" to the UI to allow you to test settings before committing them.
  3. Management VLAN can now be set to 1 under Network Settings.  This is useful when you enable data VLAN and want the device's management network to be on the native network instead of the data VLAN network. Warning: once management VLAN is set to 1, you will need to reset to defaults if you choose to downgrade to a previous firmware to avoid ending up with an inaccessible device.
  4. Various bugs were fixed related to target RSSI calculations in the UI.
  5. The initial change password form was updated to allow special characters.
  6. A "restart" button has been added to the HTTP server settings as a temporary workaround to deal with non-functioning websockets during aiming/speedtests.
  7. Management VLAN Data Bridge settings have been moved below management IP settings in the UI to help prevent mis-configurations.

Changes (beta-2, revision 54534) 6/30/24:

  1. Fixed issue where point-to-point modes don't function correctly at longer distances: this will require a firmware upgrade for the 60GHz radio, so please allow an extra 10 seconds for device firmware upgrade to complete.
  2. Fixed the alternative local IP accessibility issue from beta-1.
  3. Critical reported security vulnerabilities have been patched.  Credit goes to @semaja2 for helping us find these security issues!
  4. We now will force users to change their password from the defaults. 
  5. Fixed an issue where the wireless interface does not come up after firmware upgrade in certain cases when half channels are enabled. 
  6. Added expected RSSI to the aiming tool in the UI.


Changes (beta-1,  revision 54500) 5/14/24:

  1. The wireless driver has been updated with some optimizations and stability fixes. 
  2. Half channel frequencies (see compatibility note above) have been re-worked.
  3. Wireless settings changes: 
    • For the TNA-303X, we've added the ability to "lock to the boresight" beam to prevent the device from beamforming.  (This is useful for fine tuning a link while aiming with an antenna kit). 
    • Also for the TNA-303X, we added support for some new antenna kits.
  4. Network settings changes: 
    • Added support for "Alternative local IP"(a changeable 169.254.1.1 IP accessible over the wired ports).   This setting is enabled by default, and will be available after you upgrade your firmware.
    • Reworked the network settings of the UI to make management vs data bridge configuration more clear, and moved some settings into separate tabs for better organization.
    • Added additional DHCP option 82 settings, such as the ability to append a label indicating the ethernet port to which a client is connected to the end of the DHCP option 82 remote and/or circuit id fields.
  5. Users/Authentication: added RADIUS web UI authentication as a new option to authenticate your web UI users.
  6. System settings: changed hostname validation to allow underscores.
  7. Web UI dashboard changes:
    1. Added estimated Target RSSI to all signals.  This value is based off device model/antenna kit and link distance. Please refer to the web UI manual to learn more about this.
    2. Decreased step time from 5 to 3 seconds to help make throughput graphs more accurate for short bursts of traffic.
    3. Added a peer's model+antenna kit, as well as firmware version to the station list (LLDP is required for this to work).
    4. Fixed a bug where system uptime display string shows a lower value than the actual internal value.
    5. We now show all IP addresses on the network widget for management and data bridge(s).
    6. Other minor changes/fixes.
  8. Sector tool: Added options to toggle device label between hostname, device name, or MAC, and the sector map for the 303X were also adjusted to be more accurate.
  9. SNMP: We now expose additional device temperatures, serial number, device model and firmwares. The private MIB has been updated and can be downloaded here.
  10. Discovery changes:
    1. Discovery packets containing the device's management IPs are now broadcasted on both the management and data bridge (when they exist).  
    2. Increased interval at which discovery packets are sent from once a minute to once every 15 seconds.
    3. MNDP: the platform field now shows "Tachyon Networks" instead of the device hostname.
    4. Other small modifications to the discovery fields have been made.
  11. Bumped up the public API to version v1.0.5 to support the new config keys mentioned above.

Version 1.11.X Firmwares


Version 1.11.5 June 28, 2024 


This is a security patch release and will replace 1.11.4 and earlier versions.  


Please update your devices to 1.11.5 or higher as soon as possible.


Changes:

  1. Updates to resolve critical security vulnerabilities. A full report will be released in the upcoming months.  Credit goes to @semaja2 for helping us find these security issues!

  2. Force users to change their password from the defaults.