09-09-2017 10:53 PM
upgraded without issue so far; USG (non-pro). haven't tested if the PPPoE offload issue on centurylink is fixed, but will try that later (I don't see anything in the release notes about it, so guessing not in this release).
09-10-2017 12:33 PM
Upgraded; all seems ok for now. Memory & CPU normal; connection with controller stable and internet on full speed.
Simplicity is the ultimate sophistication.
09-11-2017 11:03 AM
Updated my private USG by inserting CDN link (https://dl.ubnt-ut.com/cmb/UGW3.v22.214.171.12412138.tar) into custom upgrade button on 5.5.20 controller
Everything is working fine, and now i will need to see if "DHCP recovery after Ethernet link loss." is fixed for me, i have had some strange outtakes where manualle renewing WAN lease has fixed connectivity.
09-11-2017 11:46 AM
also i like:
- Implemented new local web UI on USG. Fixes a variety of long-standing bugs with the old UI, and adds ability to configure LAN IP and DHCP server.
To improve, access to various logs and tables for debugging purposes would be handsome, i miss them from my old pfSense days. This might also make it easyer for people to get support in the forums, on issues with networking in general, that are not always related to the devices not working as intented.
09-12-2017 03:13 PM - edited 09-12-2017 03:18 PM
upgraded ok but WAN1 gateway address is being overwritten with WAN2 gateway address. I have WAN2 setup in failover mode.
EDIT: running Unifi 5.5.23.
09-13-2017 08:52 AM
Running Unifi 5.6.16 on a CK, USG Pro 4 on 4.3.46. I have WAN2 set up on our ELAN (192.168.0.0/16), WAN1 for Internet.
I have a firewall rule on WAN_LOCAL to allow traffic from my ELAN to the LAN IP of the USG (192.168.107.254), so I can SSH to it, ping it, etc. This works on 4.3.46, but stopped working when I upgraded to 4.3.60. I have reverted back for now. I hadn't tried any of the intermediary versions, so I don't know exactly where it stopped working.
09-15-2017 10:43 AM
I only have one USG-Pro in my managed devices inventory, just been installed yesterday, so would quite like to test a remote upgrade before it goes fully live on Monday. I could push the .tar directly but sometimes it's kind of nice seeing the notification in the Unifi controller and doing it the 'proper' way
09-15-2017 04:22 PM - edited 09-15-2017 05:35 PM
I'm unable to access any secure sites on this version, using PPPoE. DHCP works fine accessing secure sites. I've revereted back to 4.3.41 where i'm able to access sites that requre SSL using PPPoE.
09-18-2017 12:59 PM
I'm having an issue with the VPN client after upgrading to 4.3.60. https://community.ubnt.com/t5/UniFi-Routing-Switching/USG-VPN-Client-Issues-No-Traffic-to-LAN/td-p/2...
I can't ping from datacenter to USG LAN over VPN client, but can ping from device on USG LAN to datacenter over VPN client. I have a device running 4.3.46 that is not having this issue.
09-23-2017 08:25 AM
To everyone running the 'latest' stable 4.3.60 - did you push a manual upgrade to your USG/USGPro's or were you able to push using the in-built controller update functionality?
I'm kind of waiting out for the upgrade to appear in my controller, but so far it's not happening and it's been a couple of weeks since this was released... not sure if it's just not been put on the repo's or if something's not right with my controller firmware update (though it's worked for APs and switches up until now).
First customer I have with a USG so want to check the normal firmware update method is happening as it should.
I did privmsg UBNT-cmb about this but so far no reply after several days of waiting.
09-23-2017 08:44 AM
I cannot upgrade past 126.96.36.19993089, and I'm not sure why. Automatic upgrades offers me 188.8.131.5201150, but each time I try to upgrade, it appears to work (i.e., no error messages), yet after USG 3P re-appears in controller, it still says 184.108.40.20693089.
I read about the 4.3.60 update and thought "I'll just bypass this mess and custom upgrade." Shut off Auto updates, dropped this URL https://dl.ubnt-ut.com/cmb/UGW3.v220.127.116.1112138.tar into custom upgrade path, same result. Indicators switched to "Upgrading," but afterwards, still shows 18.104.22.16893089 in controller. What am I missing??
09-23-2017 09:11 AM
OK, so now, with the help of Daryl in support via LiveChat, I SSH'ed into the USG and upgraded that way...whereupon now, my Controller is STILL offering me the chance to "upgrade"...to version 22.214.171.12401150.
Should I be concerned about this? Or just leave it be?