Note: Those running 5.9.24 controller should restart the controller service, or reboot the controller's OS, before upgrading to work around a device cache bug which could cause a problem on next provision of devices (which will happen on USG post-upgrade).
Changes since 4.4.26 release (last version posted to controllers) as follows.
Hashes
Verder lezen...
Changes since 4.4.26 release (last version posted to controllers) as follows.
- USG local web UI changes
- Added VLAN tagging capability on WAN. 5.9.17 and newer controller versions required to pull this into the controller configuration the same as all other WAN config parameters.
- Populate PPPoE username and password from saved config where they exist. Those fields were previously empty where configured, leading people to wrongly think it lost the config.
- Added DHCP leases and ARP cache display to Main page. Primary reason is to help find cloud key's IP when setting up a new network and not using the discovery tool, but could be helpful in a variety of other circumstances.
- PPPoE allowed character restrictions in usernames relaxed to allow some characters previously forbidden.
- Guest control authenticated status reporting fixed where hardware offload disabled. This was the cause of non-stop guest deauthentication with offload disabled in all previous versions.
- USG3 and USG Pro updated kernel to 3.10.107 (same as USG-XG has been using for a while).
- Greatly improves achievable throughput with IDS/IPS enabled
- Most USG3 users could always hit 1 Gbps throughput with hardware offload enabled, but this is confirmed to fix edge cases where those speeds were not achievable with offload enabled.
- Significant VPN performance improvements in some cases
- USG Pro specific changes
- Automatic bootloader upgrade added. All USG Pros will have their bootloader upgraded after booting this version, including those who used the previous bootloader upgrade. This only applies to USG Pro, not the other models.
- Bundled updated u-boot version with fix for USG Pro crashing issues some have experienced. This is functionally no different from the previously released version, but all USG Pros will have the upgrade installed regardless, as this version includes a version string the OS can read to better determine the installed version.
- Manual reboot is required post-upgrade to apply the bootloader upgrade. To avoid any possibility for a never-ending reboot loop, there is no automatic reboot at the end of the bootloader upgrade. There is no requirement to immediately reboot it after upgrade, however doing so is recommended as the changes do not become active until another reboot. Upon logging into USG via SSH or serial console after a bootloader update, you will see a prompt that the bootloader has been upgraded and a reboot is required to apply. That message will no longer appear after the second reboot.
- USG-XG-8 specific changes
- LCM firmware update with several improvements
- Improvements in stats and interface status displayed on the screen. The most commonly reported issue this resolves is correcting the interface disabled or disconnected status.
- Added auto-detection of speed (SFP or SFP+) for eth1 and eth8 when in default state. Known UBNT modules are set to 1000 or 10000 accordingly for SFP or SFP+. DACs and unknown modules have their speed switched back and forth until they obtain link.
- Added back end for reporting interface speed configuration to the controller, for import to retain settings upon adoption from default state. Controller support not yet publicly released.
Hashes
- USG
- USG Pro
- USG-XG-8
Verder lezen...
