Jetzt geht die generations Trennung los
UAP Firmware 6.2.16 / nur für Gen 6 (U6-Pro/Mesh/IW)
* This release is only for the Gen6 AP's.
This version provides a new High-Performance Devices (band steering) logic. This new logic is less strict than the implementation in previous versions and allows dual-band devices join the 2.4GHz network under certain conditions. Users should expect better interoperability, more reliable access for all device types and extended range in case of insufficient 5GHz signal level.
- [UAP] Revamp Band Steering (previously called High Performance Devices).
- [UAP] Improve overall stability by fixing a number of kernel crashes.
- [UAP] Restructure the impact of DNS timeouts on the Wireless Experience Score.
- [UAP] Update packages (openssl, dropbear, zlib).
- [UAP] Update regulatory data for Israel and Bahrain to align with country requirements.
- [UAP] Allow ARP traffic on WLAN even if Multicast and Broadcast block is enabled to avoid hindering device discovery."
- [UAP-Gen6] Fix WPA3 connectivity issues.
- [UAP-Gen6] Fix radios not broadcasting in certain countries.
- [UAP-Gen6] Fix untagged RADIUS clients experiencing packet loss.
- [UAP-Gen6] Fix incorrect signal strength reporting for 5GHz clients.
- [UAP] Fix wireless uplink issues when uplink monitor is set to check connectivity to 127.0.0.1 (localhost).
- [UAP] Partly fix hostnames in guest preauthorized access list not working. Full fix will be rolled in via a Network Application update. This partial fix covers cases where guest VLANs are in use.
- [UAP] Fix occasional adoption failures.
- [UAP] Fix WLANs not broadcasting a few minutes after boot in certain topologies. This was introduced in 6.0.18.
- U6-Pro/Mesh needs to be upgraded to 5.67.0 first before upgrading to 5.68.0+.
- Instead of using the manual links, you can also subscribe to your desired firmware channel, as described here.
- Please refer to this article to find more details on how to identify your Access Point generation.
- Your device built-in display may turn black or unresponsive for ~10 minutes after firmware upgrades to upgrade LCM firmware.
- All URLs use HTTPS. This assumes your device(s) are running 3.7.56 or later and that the device's date is properly set. Please change URLs to HTTP for device(s) running earlier firmware or if the date is incorrect (e.g. if device can't reach a NTP server).
Any and all feedback is welcome, including lettings us know about successful device upgrades. When reporting an issue, please ensure that you include the following information:
- Network Application version.
- Firmware version (previous and current).
- Device model(s).