Scheduled maintenance: Community will be offline Monday June 17th, 1:00 AM - 6:00 AM (PT)
Reply
New Member
Posts: 3
Registered: ‎11-04-2018

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

Yes, you right elinden. I can't ping to internet/gateway 192.168.1.1 from access point. But I can ping lan to it. So how to fix this problem. I got 9  access point have this problem Man Sad

 

PS: I used using DHCP or Static IP for 9 access point but can't ping to internet/gateway

 

2018-12-16_16-06-23.jpg
Established Member
Posts: 824
Registered: ‎01-21-2016
Kudos: 121
Solutions: 25

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

I don't know your network, @tranduyhungdung. It's either making sure that the accesspoints have access to Internet, or upload the firmware manually (through WinSCP). Up to you to decide which is the best approach.

Controller (5.11.29): CK 1.0.4
Unifi (ca-framework-hap2.8-spf53-4.0.4.10592): UAP-AC-IW-Pro, UAP-AC-LR, UAP-AC-M & USW8-60W (4.0.43.10459)

Better WiFi coverage is not achieved by increasing transmission power, but by increasing the number of accesspoints.
Member
Posts: 110
Registered: ‎09-30-2014
Kudos: 11
Solutions: 4

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

UAP AP-HD running 4.0.10.x:

During some speed tests (on speedtest.net) from device A, AP is kicking out client B: 10:7b:44:55:c1:11 (both clients in same wlan):

 

Sun Dec 16 18:14:37 2018 kern.warn kernel: [15806.987542] === Reducing pace for error prints ====
Sun Dec 16 18:14:37 2018 kern.warn kernel: [15806.987598] PN check failed - TID 0, peer d769b000 (10:7b:44:55:c1:11) ucast
Sun Dec 16 18:14:37 2018 kern.warn kernel: [15806.987598]     old PN (u64 x2)= 0xbf9461b000000001 00002d28 (LSBs = 11560)
Sun Dec 16 18:14:37 2018 kern.warn kernel: [15806.987598]     new PN (u64 x2)= 0xbf9461b000000001 0000012c (LSBs = 300)
Sun Dec 16 18:14:37 2018 kern.warn kernel: [15806.987598]     global PN (u64 x2)= 0xbf9461b000000001 00002d28 (LSBs = 11560)
Sun Dec 16 18:14:37 2018 kern.warn kernel: [15806.987598]     suspect PN (u64 x2)= 0x00000000 00000000 (LSBs = 0)
Sun Dec 16 18:14:37 2018 kern.warn kernel: [15806.987598]     htt_status = 1
Sun Dec 16 18:14:37 2018 kern.warn kernel: [15806.987598]     PN in BA = 100  - PN in no BA = 0
Sun Dec 16 18:14:37 2018 kern.warn kernel: [15806.987598]     prev seq num = 299    new seq num = 299 - Error occured 300 times
Sun Dec 16 18:14:46 2018 kern.warn kernel: [15816.721652] [wifi0] FWLOG: [697155] WAL_DBGID_TX_BA_SETUP ( 0x4567f4, 0x8e010006, 0x46, 0x40, 0x1 )
Sun Dec 16 18:14:48 2018 kern.warn kernel: [15818.331036] Kicking out node 10:7b:44:55:c1:11 due to excessive PN replays
Sun Dec 16 18:14:48 2018 daemon.info hostapd: ath2: STA 10:7b:44:55:c1:11 IEEE 802.11: sta_stats
Sun Dec 16 18:14:48 2018 daemon.info hostapd: ath2: STA 10:7b:44:55:c1:11 IEEE 802.11: disassociated
Sun Dec 16 18:14:48 2018 daemon.info hostapd: ath2: STA 10:7b:44:55:c1:11 IEEE 802.11: disassociated
Sun Dec 16 18:14:48 2018 user.info libubnt[21756]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath2: 10:7b:44:55:c1:11 / 1

 

Also, AP lost ntp config from controler; i was forced to re-provisioning couple of times the AP to get the correct date/time (can be checked in the attached logs the sudden change of date).

Attached is the log with all errors from last couple of day - AP is serving only 8-10 clients.

 

UAP AP-AC-PRO

Suddenly, AP disconnected from controler and reaperead 4-5 mins after: oddly enough, there is no log about this but I saw the red message (disconected) in the controller device page. I've also attached errors log from last days related to PRO.

 

Let me mention that i do not have a big experience with HD "behavior" (i have it only from couple of days) but the PRO was 100% stable in the past year (only problem was couple of beta firmware ago when i was forced to do a full tftp recovery) but with this version 4.0.10.x lots of problems appeared: kernel panic, no more dhcp request from AP for his own IP address for guest portal wlan (only discover even if the server send it dhcp offer) and the "disconnected" message without logs.

 

Unifi CloudKey 0.12.1

Controller: 5.9.32

 

UAP AP-HD error log.png
UAP AP-AC-PRO error log.png
New Member
Posts: 2
Registered: ‎12-17-2018

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

Updated my 4 UAP-AC-M from 3.9.54.9373 to 4.0.10.9653 on Saturday.

 

Afterwards had a huge Amount of reconnects from my Clients , including my Doorbird (wifi video doorbell).

It was barely usable after the Upgrade.

 

I downgraded 2 of the 4 APs(which are in Range of the Doorbird) back to 3.9.54 and everything is well again.

ubnt.jpg

New Member
Posts: 1
Registered: ‎06-03-2015

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

Hi,

 

The SNMP service stop working after upgrade, rest ok...

 

Kind regards

Member
Posts: 270
Registered: ‎08-07-2018
Kudos: 87
Solutions: 4

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


@mikepiko wrote:

Updated my 4 UAP-AC-M from 3.9.54.9373 to 4.0.10.9653 on Saturday.

 

Afterwards had a huge Amount of reconnects from my Clients , including my Doorbird (wifi video doorbell).

It was barely usable after the Upgrade.

 

I downgraded 2 of the 4 APs(which are in Range of the Doorbird) back to 3.9.54 and everything is well again.

ubnt.jpg


 

If you have multiple access points it may be that the doorbell was connecting to the wrong one. I have 3 APs and after updating all of them I found that my Wemo smart likghts were all connecting to the wrong APs, not the closest ones. What apparently happened in the upgrade process is that when an AP went offline for the upgrade the lights connected to another AP. Then, when the original one comes back online, they don't default to the more powerful AP that is closer, they hang on the further AP and you end up with lots of dropped packets and issues.

 

I had to reset the lights. When I ran a reset, the lights then grabbed the closest AP and we were back in business, the dropped packets stopped. It might be worth updating the APs and then doing a reset on the doorbell to see if that helps the issue.

New Member
Posts: 2
Registered: ‎12-17-2018

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

Already tried that yesterday.

 

Resetting doesn´t help. 

 

i even changed the setting to prevent it from connecting if rssi is under -60, which made the bell switch back to it´s original ap.

But it doesn´t stay there, it keeps trying to reconnect to the other one.

 

Now that everything is back to the old FW everything is fine again.

 

 

 

New Member
Posts: 18
Registered: ‎11-08-2015
Kudos: 2

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

[ Edited ]

What first brought me to this thread was that I use PRTG to keep an eye on everything on the network and after the upgrade, I saw the attached.  All my WAP's (UAP-AC-PRO's) went from a basically unmeasurable "response time index" to very measurable (the red peak is the alarm that was triggered during the upgrade).  My WAPs are under almost no load, the 2.4 ghz radios are all off, and utilization on the 5GHZ is extremely low.  Yet they respond to pings with much more latency than with previous builds.

 

Also, I did a little expreiment where I pushed fake traffic from a desktop PC to a laptop connected to one of the WAP's using Passmarp Perf Test's built-in network tester and with 75% channel utilization in the transmit direction, the WAP's CPU use jumped from around 4% up to about 50-60%.  I see your utilization is similar and CPU use is similar.  I'm surprised utilization=CPU use like that.  I don't remember that being the case as much with previous builds.

 

 

Untitled.png
Ubiquiti Employee
Posts: 4,054
Registered: ‎01-11-2016
Kudos: 1204
Solutions: 29

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

@ogo What hardware are you running the controller on, and how many sites do you have on it?
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
Member
Posts: 110
Registered: ‎09-30-2014
Kudos: 11
Solutions: 4

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

@UBNT-jeff 

Controller is runing on Unifi Cloud Key (1st generation) and i have only 1 site.  I have only 10 to 12 regular wifi clients, mostly cell phones, ipads and couple of laptops (most of my home is wired).

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

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

[ Edited ]

As I mentioned in the beta topic of 4.0.9 I noticed a big problem with disconneted devices, which are not comming back by themselves.

It happens on both wireless uplinks, where a unifi switch UniFi Switch 8 POE-60W is connected behind the UAP-AC M oder UAP-AC M Pro. I can see it getting offline both for UAPs and the connected switch. 

 

It´s getting more woth than before. In earlier releases the same switches will only disconnect and came back after a few hours, together with running uptime by 0 (seems it resests himself)

 

I am still waiting for an explanaition for this behavior and reason, and at least for a solution...

 

I am able to connect by ssh to the affected UAP (Mobaxterm), but I wouldn´t get a sucsessful login. I receive a timeout. Same with the Unifi switch

best regards
Torsten

Ubiquiti Employee
Posts: 4,054
Registered: ‎01-11-2016
Kudos: 1204
Solutions: 29

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

@ogo Going to go out on a limb, but have you tried backing up your config, and then restoring? If the controller is responding that it's busy in a site that small, something seems off with the database/controller.
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: 9
Registered: ‎07-11-2018
Kudos: 1

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

It seems baresip is broken on the EDU-AP in the 4.10.x release. This is the output when attempting to install

 

UniFi-040-BZ.v4.0.10# opkg install baresip

Installing baresip (0.4.19-1) to root...

Collected errors:

* verify_pkg_installable: Only have 0kb available on filesystem /overlay, pkg baresip needs 202

* opkg_install_cmd: Cannot install package baresip.

UniFi-040-BZ.v4.0.10#

 

This AP worked fine in 3.9.x. Any ideas? 

New Member
Posts: 16
Registered: ‎03-16-2017
Kudos: 1

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

My Ring Floodlight camera lost connection to my UAP-HD after upgrade to 4.0.10.9653. All other wifi devices work fine. Only this camera is having trouble connecting after upgrade. Tried factory reset the Ring Floodlight cam and it won't connect. Downgraded it back to 3.9.54.9373 and all is fine.

New Member
Posts: 8
Registered: ‎03-20-2016
Kudos: 2

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

[ Edited ]

Revert to 3.9.54.9373.

Firmware 4.0.10.9653 is to unstable (disconnect) with my AP AC LR and two wireless connected AP AC Meshes.

Mesh AP´s disconnected after 2-3 hours and only a restart from my AP AC LR take the mesh back to connect.

Emerging Member
Posts: 60
Registered: ‎07-05-2017
Kudos: 17
Solutions: 7

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

[ Edited ]

@markpleasance

the message clear show you have no disk space left to do any install, try df command to identify your disk usage, if it's full or readonly you have to take care of that.

 

New Member
Posts: 31
Registered: ‎02-10-2014
Kudos: 3

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

I have rolled back the firmware to the 3.9-release and things seem, SEEM, to be better. We will need to wait and see how it responds when students are back on campus.

Member
Posts: 111
Registered: ‎05-10-2017
Kudos: 21
Solutions: 1

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

Bandwidth speed limit still broken for wirelessly uplinked devices. My wired UAP-AC-M's all obey bandwidth limits as specified, but those UAP-AC-M's on a wireless uplink only obey Download limit (Upload works full speed). This behaviour is replicated on all devices and has been the same for some time, so can't really advise on a recent firmware version where this has worked properly. 

 

https://community.ubnt.com/t5/UniFi-Routing-Switching/Bandwidth-limitations-for-upload-not-working/t...

New Member
Posts: 22
Registered: ‎03-13-2017
Kudos: 10

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

After upgrading to 4.0.10.9653 (AC PRO) we started seeing many WPA association failures...

 

Log from the AP if it helps...

	Line 388: Tue Dec 18 14:04:21 2018 daemon.info hostapd: ath3: STA 04:52:f3:dd:00:76 IEEE 802.11: disassociated
	Line 396: Tue Dec 18 14:04:24 2018 user.info libubnt[2009]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath3: 04:52:f3:dd:00:76 / 12
	Line 400: Tue Dec 18 14:04:25 2018 daemon.info hostapd: ath3: STA 82:2a:a8:58:a3:cc DRIVER: Sead AUTH addr=04:52:f3:dd:00:76 status_code=0
	Line 401: Tue Dec 18 14:04:25 2018 daemon.info hostapd: ath3: STA 04:52:f3:dd:00:76 IEEE 802.11: associated
	Line 402: Tue Dec 18 14:04:25 2018 daemon.info hostapd: ath3: STA 04:52:f3:dd:00:76 WPA: pairwise key handshake completed (RSN)
	Line 404: Tue Dec 18 14:04:25 2018 user.info libubnt[2009]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath3: 04:52:f3:dd:00:76 / 2
	Line 406: Tue Dec 18 14:04:25 2018 kern.warn kernel: [69934.284286] ieee80211_ioctl_set_ratelimit: node with aid 2 and mac 04:52:f3:dd:00:76 has been tagged non rate-limiting
	Line 407: Tue Dec 18 14:04:25 2018 user.info libubnt[2009]: wevent.ubnt_custom_event(): EVENT_STA_IP ath3: 04:52:f3:dd:00:76 / 10.1.3.159
	Line 445: Tue Dec 18 14:04:35 2018 daemon.info hostapd: ath3: STA 04:52:f3:dd:00:76 RADIUS: starting accounting session 629AC66F642CD383
	Line 447: Tue Dec 18 14:04:35 2018 user.info libubnt[2009]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 6 event_type: soft failure vap: ath3 sta_mac: 04:52:f3:dd:00:76 auth_ts: 69934.198900 auth_delta: 0 assoc_delta: 0 wpa_auth_delta: 10000 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: 10000 disassoc_count: 0 ip_assign_type: roamed auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 acl_status: allowed arp_status: N/A dns_status: N/A 
	Line 660: Tue Dec 18 14:05:36 2018 daemon.info hostapd: ath3: STA 04:52:f3:dd:00:76 IEEE 802.11: disassociated
	Line 661: Tue Dec 18 14:05:36 2018 user.info libubnt[2009]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath3: 04:52:f3:dd:00:76 / 2
	Line 670: Tue Dec 18 14:05:38 2018 daemon.info hostapd: ath3: STA 82:2a:a8:58:a3:cc DRIVER: Sead AUTH addr=04:52:f3:dd:00:76 status_code=0
	Line 671: Tue Dec 18 14:05:38 2018 daemon.info hostapd: ath3: STA 04:52:f3:dd:00:76 IEEE 802.11: associated
	Line 673: Tue Dec 18 14:05:38 2018 user.info libubnt[2009]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath3: 04:52:f3:dd:00:76 / 30
	Line 675: Tue Dec 18 14:05:38 2018 kern.warn kernel: [70008.105933] ieee80211_ioctl_set_ratelimit: node with aid 30 and mac 04:52:f3:dd:00:76 has been tagged non rate-limiting
	Line 694: Tue Dec 18 14:05:44 2018 user.info libubnt[2009]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath3: 04:52:f3:dd:00:76 / 30
	Line 703: Tue Dec 18 14:05:48 2018 daemon.info hostapd: ath3: STA 04:52:f3:dd:00:76 IEEE 802.11: deauthenticated due to local deauth request
	Line 708: Tue Dec 18 14:05:51 2018 user.info libubnt[2009]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 7 event_type: failure vap: ath3 sta_mac: 04:52:f3:dd:00:76 auth_ts: 70008.8618 auth_delta: 0 assoc_delta: 20000 wpa_auth_delta: -1 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: -1 disassoc_count: 0 ip_assign_type: N/A auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 1 ip_failures: 0 acl_status: allowed arp_status: N/A dns_status: N/A 
	Line 1416: Tue Dec 18 14:11:16 2018 daemon.info hostapd: ath3: STA 82:2a:a8:58:a3:cc DRIVER: Sead AUTH addr=04:52:f3:dd:00:76 status_code=0
	Line 1418: Tue Dec 18 14:11:16 2018 daemon.info hostapd: ath3: STA 04:52:f3:dd:00:76 IEEE 802.11: associated
	Line 1423: Tue Dec 18 14:11:16 2018 user.info libubnt[2009]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath3: 04:52:f3:dd:00:76 / 12
	Line 1425: Tue Dec 18 14:11:16 2018 kern.warn kernel: [70345.578803] ieee80211_ioctl_set_ratelimit: node with aid 12 and mac 04:52:f3:dd:00:76 has been tagged non rate-limiting
	Line 1445: Tue Dec 18 14:11:20 2018 user.info libubnt[2009]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath3: 04:52:f3:dd:00:76 / 12
	Line 1450: Tue Dec 18 14:11:25 2018 daemon.info hostapd: ath3: STA 04:52:f3:dd:00:76 IEEE 802.11: deauthenticated due to local deauth request
	Line 1454: Tue Dec 18 14:11:29 2018 user.info libubnt[2009]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 1 event_type: failure vap: ath3 sta_mac: 04:52:f3:dd:00:76 auth_ts: 70345.449138 auth_delta: 0 assoc_delta: 10000 wpa_auth_delta: -1 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: -1 disassoc_count: 0 ip_assign_type: N/A auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 1 ip_failures: 0 acl_status: allowed arp_status: N/A dns_status: N/A 
	Line 1458: Tue Dec 18 14:11:34 2018 daemon.info hostapd: ath3: STA 82:2a:a8:58:a3:cc DRIVER: Sead AUTH addr=04:52:f3:dd:00:76 status_code=0
	Line 1459: Tue Dec 18 14:11:34 2018 daemon.info hostapd: ath3: STA 04:52:f3:dd:00:76 IEEE 802.11: associated
	Line 1462: Tue Dec 18 14:11:35 2018 user.info libubnt[2009]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath3: 04:52:f3:dd:00:76 / 12
	Line 1464: Tue Dec 18 14:11:35 2018 kern.warn kernel: [70364.687666] ieee80211_ioctl_set_ratelimit: node with aid 12 and mac 04:52:f3:dd:00:76 has been tagged non rate-limiting
	Line 1471: Tue Dec 18 14:11:38 2018 user.info libubnt[2009]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath3: 04:52:f3:dd:00:76 / 12
	Line 1478: Tue Dec 18 14:11:43 2018 daemon.info hostapd: ath3: STA 04:52:f3:dd:00:76 IEEE 802.11: deauthenticated due to local deauth request
	Line 1491: Tue Dec 18 14:11:44 2018 user.info libubnt[2009]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 2 event_type: failure vap: ath3 sta_mac: 04:52:f3:dd:00:76 auth_ts: 70363.320737 auth_delta: 0 assoc_delta: 10000 wpa_auth_delta: -1 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: -1 disassoc_count: 0 ip_assign_type: N/A auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 1 ip_failures: 0 acl_status: allowed arp_status: N/A dns_status: N/A 
	Line 1521: Tue Dec 18 14:11:52 2018 daemon.info hostapd: ath1: STA 82:2a:a8:57:a3:cc DRIVER: Sead AUTH addr=04:52:f3:dd:00:76 status_code=0
	Line 1522: Tue Dec 18 14:11:52 2018 daemon.info hostapd: ath1: STA 04:52:f3:dd:00:76 IEEE 802.11: associated
	Line 1523: Tue Dec 18 14:11:52 2018 daemon.info hostapd: ath1: STA 04:52:f3:dd:00:76 WPA: pairwise key handshake completed (RSN)
	Line 1537: Tue Dec 18 14:11:53 2018 user.info libubnt[2009]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath1: 04:52:f3:dd:00:76 / 12
	Line 1539: Tue Dec 18 14:11:53 2018 kern.warn kernel: [70383.117200] ieee80211_ioctl_set_ratelimit: node with aid 12 and mac 04:52:f3:dd:00:76 has been tagged non rate-limiting
	Line 1540: Tue Dec 18 14:11:53 2018 user.info libubnt[2009]: wevent.ubnt_custom_event(): EVENT_STA_IP ath1: 04:52:f3:dd:00:76 / 10.1.3.159
	Line 1562: Tue Dec 18 14:12:00 2018 daemon.info hostapd: ath1: STA 04:52:f3:dd:00:76 IEEE 802.11: disassociated
	Line 1565: Tue Dec 18 14:12:05 2018 user.info libubnt[2009]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath1: 04:52:f3:dd:00:76 / 12
	Line 1567: Tue Dec 18 14:12:05 2018 user.info libubnt[2009]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 1 event_type: success vap: ath1 sta_mac: 04:52:f3:dd:00:76 auth_ts: 70381.969522 auth_delta: 0 assoc_delta: 50000 wpa_auth_delta: 150000 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: 1560000 disassoc_count: 0 ip_assign_type: dhcp auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 acl_status: allowed arp_status: N/A dns_status: N/A 
Ubiquiti Employee
Posts: 4,054
Registered: ‎01-11-2016
Kudos: 1204
Solutions: 29

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

@rpesta Is 04:52:f3:dd:00:76 something that should be allowed on your network? Do they have the right passphrase, etc?
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
Reply