Scheduled maintenance: Community will be offline Monday June 17th, 1:00 AM - 6:00 AM (PT)
Reply
Highlighted
Ubiquiti Employee
Posts: 4,051
Registered: ‎01-11-2016
Kudos: 1204
Solutions: 29

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

@nrempe In order to attempt to reproduce this, can you tell me what order you upgraded things in? This issue should not be anything new/specific to this release, but might be possible if certain conditions are met.
Want to try out new features or fixes before they're released as Stable? Sign up for Beta here: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Signup-for-Beta-Access
Having connectivity issues? See: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
New Member
Posts: 12
Registered: ‎02-03-2018
Kudos: 1

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

The first time around, I started with the APs first and worked into the core. After that was unsuccessful, I started with my core switch and then worked out to the second switch and to the APs from there. The second time was slightly less chaotic, but neither was clean. In both cases I reverted back to current stable version.

New Member
Posts: 14
Registered: ‎02-04-2016
Kudos: 1

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

[ Edited ]

Tried updating to this firmware today. Successful, initially, but then started having issues. Main issue was with a Flo device (TexasIns chipset) that refused to complete connection.

 

 

Apr 19 17:12:57 downstairs U7PG2,44d9e7f93e50,v4.0.30.10217: hostapd: ath1: STA 46:d9:e7:fa:3e:50 DRIVER: Sead AUTH addr=f4:84:4c:5e:fc:31 status_code=0
Apr 19 17:12:57 downstairs U7PG2,44d9e7f93e50,v4.0.30.10217: hostapd: ath1: STA f4:84:4c:5e:fc:31 IEEE 802.11: associated
Apr 19 17:13:06 downstairs U7PG2,44d9e7f93e50,v4.0.30.10217: hostapd: ath1: STA f4:84:4c:5e:fc:31 IEEE 802.11: deauthenticated due to local deauth request
Apr 19 17:13:07 downstairs U7PG2,44d9e7f93e50,v4.0.30.10217: libubnt[2397]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 7 vap: ath1 sta_mac: f4:84:4c:5e:fc:31 auth_ts: 4275.736475 auth_delta: -1 assoc_delta: -1 wpa_auth_delta: -1 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: -1 ip_assign_type: N/A disassoc_count: 0 auth_failures: 1 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 assoc_status: 0 arp_status: N/A dns_status: N/A event_type: failure

 

After downgrade:

Apr 19 17:17:10 downstairs U7PG2,44d9e7f93e50,v4.0.21.9965: hostapd: ath1: STA 46:d9:e7:fa:3e:50 DRIVER: Sead AUTH addr=f4:84:4c:5e:fc:31 status_code=0
Apr 19 17:17:10 downstairs U7PG2,44d9e7f93e50,v4.0.21.9965: hostapd: ath1: STA 46:d9:e7:fa:3e:50 DRIVER: Sead AUTH addr=f4:84:4c:5e:fc:31 status_code=0
Apr 19 17:17:10 downstairs U7PG2,44d9e7f93e50,v4.0.21.9965: hostapd: ath1: STA f4:84:4c:5e:fc:31 IEEE 802.11: associated
Apr 19 17:17:10 downstairs U7PG2,44d9e7f93e50,v4.0.21.9965: hostapd: ath1: STA f4:84:4c:5e:fc:31 WPA: pairwise key handshake completed (RSN)
Apr 19 17:17:10 downstairs U7PG2,44d9e7f93e50,v4.0.21.9965: libubnt[2387]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath1: f4:84:4c:5e:fc:31 / 1
Apr 19 17:17:10 downstairs U7PG2,44d9e7f93e50,v4.0.21.9965: kernel: [   52.491555] ieee80211_ioctl_set_ratelimit: node with aid 1 and mac f4:84:4c:5e:fc:31 has been tagged non rate-limiting
Apr 19 17:17:11 downstairs U7PG2,44d9e7f93e50,v4.0.21.9965: libubnt[2387]: wevent.ubnt_custom_event(): EVENT_STA_IP ath1: f4:84:4c:5e:fc:31 / 10.x.x.x
Apr 19 17:17:20 downstairs U7PG2,44d9e7f93e50,v4.0.21.9965: libubnt[2387]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 1 event_type: success vap: ath1 sta_mac: f4:84:4c:5e:fc:31 auth_ts: 52.28947 auth_delta: 0 assoc_delta: 40000 wpa_auth_delta: 170000 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: 750000 disassoc_count: 0 ip_assign_type: dhcp auth_failures: 1 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 acl_status: allowed arp_status: yes dns_status: yes

I downgraded to the original firmware and the device was able to successfully connect once more.

 

Controller:5.10.21

Original firmware: 4.0.21.9965

Device: UniFi AP-AC-Pro (U7PG2)

 

Regular Member
Posts: 343
Registered: ‎10-16-2017
Kudos: 38
Solutions: 5

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

My reply on beta forum:

We have many user online since beginning of easter holidays. It was a heavy load test for this firmware, and it was a nightmare:

 

- Constantly crashing UAP AC-M, under load and higher user loads and activity (>4-6)

- DFS channel changes kills MESH M downlinks (rebooting)

- after a few hours of running, band steering is not working any more. A reboot later and devices connects again with 5Ghz. 

- downgrading UAP AC-M solves crashing APs

 

Users are reporting slow or no connection although the ISP load is low. I can´t see really a reason for it. Channel load is not as much as I expect. Retry rate for AP is 50% good 40% fine and maybe 10% between 80-90% but not more.

I think DHCP and DNS Errors are more likely the reason. (Wifi Experince is showing this issue)

 

I downgraded all UAP AC-M, only UAP-AC M pro are keeping on 4.0.30, now they are for more than a day online.

 

I can´t recommend to use this firmware on UAP AC-M and UAP AC M pro in production use! Switches and UAP AC pro / lite are running without problems. 

Many users are reporting problems with stability issues, I can´t understand, why these version is going to release candidate ...

best regards
Torsten

Deleted Account
Posts: 0

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

Having issues with 802.11w/PMF on an iPad Mini 5 running iOS 12.2, using a UAP-IW-HD and Cloud Key on 5.10.21-11661-1. The device will associate momentarily but then drop off when PMF is set to Required. An iPhone 7 on iOS 12.2 and a MacBook Pro on 10.14.4 Mojave both work fine. The iPad Mini 5 works fine on a couple of Cisco APs set for PMF required as well. An iPad Mini 4 worked fine with PMF required.

 

Issue is consistent between 4.0.30.10217 and 4.0.21.9965.

New Member
Posts: 40
Registered: ‎11-10-2013
Kudos: 11
Solutions: 4

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

[ Edited ]
  • issues with 4.0.21 memmory/leak not passing traffic
  • CTO was going onto our owners personal property today and reported 4.0.21 was completely unusable.
  • did an emergency upgrade to 4.0.30.10217 on all access points
  • everything seemed fine, but had to disable 802.11r for some reason for roaming to working, regardless that wasnt a show stopper so no big deal
  • CTO was in an area that was pretty isolated from any other access points except for the access point reference in these logs:.
    • CTO could not connect
    • CTO tried multiple times to multiple SSID's we have broadcasting with the same issue
    • CTO worked on something else, and about 15 minutes later he noticed his phone had connected.

I got a call about this so i went ahead and logged into the AP itself and pulled the following info from syslog.  was hoping one of the wizards here could walk me through what is going on in these messages.

 

 

 

please see the attached file Man Happy

 

New Member
Posts: 34
Registered: ‎04-02-2019

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

[ Edited ]

I am on Controller 5.10.21 but not getting this Firmware updates. our AP FW V is 4.0.21.9965

Emerging Member
Posts: 53
Registered: ‎09-22-2018
Kudos: 16
Solutions: 5

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

[ Edited ]

@cyberbot wrote:

I am on Controller 5.10.21 but not getting this Firmware updates. our AP FW V is 4.0.21.9965


4.0.30 is a Stable Candidate. It won't show up in your controller for maintanence until it is elevated to Stable status and released to the repository.

 

New Member
Posts: 38
Registered: ‎01-08-2018
Kudos: 6

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

Breaks 2ghz if you disable 5ghz. 

You end up being unable to connect. Most bloody annoying. Spent the last 2 nights trying to figure this with a clean new install only for it to be the firmware

New Member
Posts: 10
Registered: ‎03-24-2018
Kudos: 9

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

@UBNT-MikeD  - any news? current workarounds of...

 

1. no ipv6 wifi

2. no guest wlan

3. prayer

 

are only buying me a limited lifeline with customers!

 

please?

 

dave

Regular Member
Posts: 531
Registered: ‎05-10-2008
Kudos: 54
Solutions: 1

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

It seems that minRSSI is not working correctly, some clients hang around at -90dBm forever. There are some ieee80211_ioctl_kickmac[14968] lines in dmesg on that AP, but I think there should be more of them. Is there a way to debug this, for example check rssi limit directly on AP console?

New Member
Posts: 5
Registered: ‎04-23-2019

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

Back to 4.21 here. Thought it was working fine until i tried using my devices. Phones (Pixel 3) cant connect etc.

 

New Member
Posts: 3
Registered: ‎08-15-2016

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

When we upgraded our AC Pros to this version we had issues with older Lenovo 500 series laptops not connecting. We tried driver and firmware updates with no luck. Just an FYI.

New Member
Posts: 4
Registered: ‎12-12-2016
Kudos: 1

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate


@waterside wrote:
@toiletbowl wrote:

 

im using controller 5.10.20 but no firmware available 4.0.30 see attached file.

This release is a Stable Candidate, not a GA Stable release.  As such it would not be available via the controller and would only be available via the blog posting.

 

This sticky post at the top of this forum may be of some help:


 

You are 100% right. Since this issue comes up so frequently with mostly newer users believing that "Stable Candidate" means "stable/production ready", maybe it would be a positive change for the Ubiquiti developer team to rename the release statuses and avoid putting the word "Stable" in "Stable Candidate"? Just a thought, but I think this would avoid much confusion for newer users going forward and make it explicitly clear what cycle a release is in. Something like "Alpha Release" or "Beta Release" or even "Beta-Test Release".

Model: UAP-AC-Pro-Gen2
Version: 4.0.30.10217
Controller: 5.10.23
New Member
Posts: 8
Registered: ‎02-13-2019
Kudos: 4

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

Any news on when the Stable firmware will be released?

I read on the forum that it's usually a week after the candidate unless other bugs are found etc.

 

Has anyone updated to the Stable Candidate and found that it addresses the DHCP Timeout and WPA Authentication Timeout issues on the Dashboard?

New Member
Posts: 2
Registered: ‎03-04-2019

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

After I updated an Unifi UAP from firmware 4.0.20 to 4.0.30, it started to reboot very fast. This is what I see when I start the AP:

- after a couple of seconds the circle light turns on and it become yellow

- then after a couple of seconds the circle light become green

- after another couple of seconds the AP turns off and the loop starts again

 

I tried to execute the procedure for manual upgrade, but I'm not able to do it because the AP is restarting very fast. Could somebody help me? Do I need to ask for an RMA?

 

Regards, thanks in advance
Matteo Zaffonato

Regular Member
Posts: 374
Registered: ‎04-22-2018
Kudos: 82
Solutions: 4

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate


@ashleylewisms wrote:

Any news on when the Stable firmware will be released?

I read on the forum that it's usually a week after the candidate unless other bugs are found etc.

 

Has anyone updated to the Stable Candidate and found that it addresses the DHCP Timeout and WPA Authentication Timeout issues on the Dashboard?


Seems their has been some big issues with the beta testing. So far I think they've had 4 or 5 builds put out since .30 and people still having issues.  So an educated guess would be early June, unless they push something out with known bugs/issues.

 

Like you I'm stuck with this FW as anything else, my Apple Watch won't connect to wifi, and drains the battery.

 


AP AC LITE
UAP nanoHD (x2)
Edgerouter 4
New Member
Posts: 4
Registered: ‎12-12-2016
Kudos: 1

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

[ Edited ]

@ashleylewisms wrote:

Any news on when the Stable firmware will be released?

I read on the forum that it's usually a week after the candidate unless other bugs are found etc.

 

Has anyone updated to the Stable Candidate and found that it addresses the DHCP Timeout and WPA Authentication Timeout issues on the Dashboard?


Yes 4.0.30 addressed the DHCP timeout on the dashboard for me. Actually come to think of it I did also update the controller to 5.10.23 so not sure which one did it.

Model: UAP-AC-Pro-Gen2
Version: 4.0.30.10217
Controller: 5.10.23
New Member
Posts: 8
Registered: ‎02-13-2019
Kudos: 4

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

Thanks, I'm currently on controller version 5.10.23 but the AC-PROs I have are still running 4.0.21 for the time being, and still have the timeout issues.
Looking forward to an actual stable release for 4.0.30
Established Member
Posts: 943
Registered: ‎06-17-2015
Kudos: 188
Solutions: 56

Re: [FIRMWARE] 4.0.30.10217 for UAP/USW has been released | Stable Candidate

[ Edited ]

I'm running 4.0.30 on some AC -Pro's and AC-M's. Until this release, I never had to worry about clients jumping onto 2.4ghz, as I sadly have had to enable for some 2.4ghz devices, last summer.

 

Now,  as in this release, out of the blue, IOS devices automatically connect to 2.4gz, as opposed to 5ghz, which is enabled on the same AP. I enabled prefer 5G.  For some reason, the clients seemd to have missed the message. Perhaps enable 5G is currently in placebo mode. This is the first version of firmware where this has become an issue since I have been running Unifi gear.  Controller 5.10.23.

Reply