Legacy Open Mesh: Access Point firmware release notes

Stable Release

Release 6.4.15 (Maintenance update, released as new stable on February 4th, 2019)

Bug Fixes:

• Resolved an issue which could cause Access Points to check in every ten minutes instead of every five minutes
• Resolved an issue in which the date defaulted to February 5, 2017 on first boot, causing check-in failure when NTP is broken

Vulnerability Fixes:

• Update curl to address CVE-2018-16839 and CVE-2018-16842 on ng6.4.x

Known Issues:

• DNS intercept does not work without Alternate DNS when multiple SSIDs are in a bridged state
• The http://logout function does not work with Bridge to LAN enabled

6.4.14 - 2018-09-26 - Released as stable on 2018-10-08

Version 6.4.14

• Allow external splash page pre-authentication to be turned off. GUI

Bug Fixes:

• Enabling Band Steering may result in high processor load and/or client connection issues

Known Issues:

• On the A62, the AP might not bring up the DNS server on boot, preventing it from serving clients or upgrading firmware
• CloudTrax may incorrectly report some clients as having a 169.x.x.x IP address
• WPA password may not work on SSIDs set to 2.4GHz or 5GHz only
• Unblocked clients that were previously blocked via Manage -> Clients may remain blocked until reboot
• 5Ghz Meshing always uses 80Mhz channel width, regardless of CloudTrax channel settings
• Hostname reported via syslog might report as "lede", instead of actual hostname
• Roaming VLANs may become re-enabled after reboot, even when they are turned off in CloudTrax
• The A42 802.3af port now uses the MAC address shown on the underside sticker, instead of the sticker MAC address +1. This results in a different MAC address being used for DHCP requests compared to 6.4.2/6.4.1

Release 2018-03-12

Version 6.4.6

New Features:

• Remote syslog server support
• Removed outdated crypto algorithms from SSH implementation

Bug Fixes:

• Some clients may report being connected to the wrong band(e.g. 2.4Ghz instead of 5Ghz)
• "2.4Ghz only" and "5Ghz only" band setting may not be honored if another SSID is set to use the "Both - Combined SSID". The AP may continue to broadcast both bands
• Disabling Application Reporting breaks throttling on non-bridged SSIDs
• Some wireless repeaters may report 0 hops on large mesh networks
• Some APs may stop reporting client traffic
• Throttling does not work on non-bridged SSIDs with Application Reporting disabled
• Captive portal may prevent client connections on busy networks due to not clearing its clients list when Application Reporting is disabled
• Setting throttle to 100mbit/sec resulted in 10mbit/sec throttle
• Auto channel mode may fail due to incorrect channel values reported by AP

Known Issues:

• CloudTrax may incorrectly report some clients as having a 169.x.x.x IP address
• Enabling Band Steering may result in high processor load and/or client connection issues
• Unblocked clients that were previously blocked via Manage Clients may remain blocked until reboot
• Hostname reported via syslog might report as "lede", instead of actual hostname
• The IP address of wired clients is not reported when Application Reporting is turned off
• 5Ghz Meshing always uses 80Mhz channel width, regardless of CloudTrax channel settings
• Roaming VLANs may become re-enabled after reboot, even when they are turned off in CloudTrax
• The A42 802.3af port now uses the MAC address shown on the underside sticker, instead of the sticker MAC address +1. This results in a different MAC address being used for DHCP requests compared to 6.4.2/6.4.1

Release 2018-01-08

Version 6.4.5

Bug Fixes:

• Using the SSID Band setting "Both - Unique SSIDs", results in the first character of each SSID name being truncated
• AP may report N/A N/A for channels, despite broadcasting correctly

Known Issues:

• Some clients may report being connected to the wrong band(e.g. 2.4Ghz instead of 5Ghz)
• Disabling Application Reporting breaks throttling on non-bridged SSIDs
• "2.4Ghz only" and "5Ghz only" band setting may not be honored if another SSID is set to use the "Both - Combined SSID". The AP may continue to broadcast both bands
• Some wireless repeaters may report 0 hops on large mesh networks
• Some APs may stop reporting client traffic
• Setting throttle to 100mbit/sec results in 10mbit/sec throttle
• Auto channel mode may fail due to incorrect channel values reported by AP
• The IP address of wired clients is not reported when Application Reporting is turned off
• The A42 802.3af port now uses the MAC address shown on the underside sticker, instead of the sticker MAC address +1. This results in a different MAC address being used for DHCP requests compared to 6.4.2/6.4.1

Release 2017-12-27

Version 6.4.4

New Features:

• Unused splash page images are now deleted automatically from the access point when SSID settings are saved.
• Bridge Loop Avoidance is now more aggressive to avoid looping scenarios on complex networks.
• If AP Mesh is disabled, access point will reconfigure channel changes immediately.

Bug Fixes:

• Facebook WiFi would not pop-up automatically or would be displayed incorrectly on iOS and macOS devices.
• Clients w/ hostnames may cause malformed JSON, resulting in striped pattern on the outage graph due to check-in failure.
• External splash pages that worked in 6.3 firmware fail to work on 6.4 firmware due to internal CONN_ERR.
• SSIDs may fail to broadcast with WiFi Scheduling enabled.
• Disabled LED lights may turn back on after firmware upgrade.

Known Issues:

• "2.4Ghz only" and "5Ghz only" band setting may not be honored if another SSID is set to use "Both - Combined SSID". The AP may continue to broadcast both bands.
• Using the SSID Band setting "Both - Unique SSIDs", results in the first character of each SSID name being truncated.
• Traffic for wired clients not reported when Application Reporting is turned off.
• IP address for wired clients not reported.
• AP may report N/A N/A for channels, despite broadcasting correctly.
• The A42 802.3af port now uses the MAC address shown on the underside sticker, instead of the sticker MAC address +1. This results in a different MAC address being used for DHCP requests compared to 6.4.2/6.4.1.

Release 2017-12-04

Version 6.4.3

New Features:

• Client IP addresses reported to CloudTrax.
• Prefer 5Ghz 802.11ac meshing, if available.
• Firmware upgrade delay reduced and firmware can upgrade when in orphan mode, allowing for faster firmware updates.
• BATMAN Mesh Protocol reverted to BATMAN IV, due to instability seen with BATMAN V.
• Bridge multiple SSIDs to LAN. (GUI Coming Soon...)

Fixes:

• Bandwidth throttling was not always being applied to some clients, when the SSID was bridged to a VLAN or after a WiFi Scheduling event.
• Upload/Download usage reporting could get reversed.
• Mesh interface could get set to managed mode, leaving repeaters orphaned.
• When Status LEDs were turned off, the LEDs would remain off even during reconfiguration or an error events.
• LED may get stuck showing white color.
• Channel scan could send incorrect channel values causing Auto channel mode to fail.

Known Issues:

• "2.4Ghz only" and "5Ghz only" band setting may not be honored if another SSID is set to use "Both - Combined SSID". The AP may continue to broadcast both bands.
• Disabled LEDs could turn themselves back on after upgrade.
• Traffic for wired clients not reported when Application Reporting is turned off.
• IP address for wired clients not reported.
• The A42 802.3af port now uses the MAC address shown on the underside sticker, instead of the sticker MAC address +1. This results in a different MAC address being used for DHCP requests compared to 6.4.2/6.4.1.
• AP may report N/A N/A for channels, despite broadcasting correctly.
• Clients w/ hostnames may cause malformed JSON, resulting in striped pattern on the outage graph due to check-in failure.
• External splash pages that worked in 6.3 firmware fail to work on 6.4 firmware due to internal CONN_ERR.

Release 2017-10-20

Version 6.4.2

Bug Fixes:

• WPA2 "Key Reinstallation Attack (KRACK)" exploit (CVE-2017-13077, CVE-2017-13078, CVE-2017-13079, CVE-2017-13080, CVE-2017-13081, CVE-2017-13082, CVE-2017-13084, CVE-2017-13086, CVE-2017-13087, CVE-2017-13088)
• Dnsmasq remote code execution vulnerability identified by Google (CVE-2017-14492, CVE-2017-14493, CVE-2017-14494, CVE-2017-14495, CVE-2017-14496, CVE-2017-13704, CVE-2017-14491)
• When using RADIUS for external splash page, you'll no longer see an "[acct_unique] WARNING: Attribute User-Name was not found in request, unique ID MAY be inconsistent" error in your server logs
• APs will no longer show “striping” due to an issue causing missed check-ins