Reply
Ubiquiti Employee
Posts: 1,435
Registered: ‎12-16-2015
Kudos: 310
Solutions: 10

Re: Problems with Wireless Uplink users

@andrewhotlab after your wireless AP disconnects and re-connects, will you ssh in and run grep 'received packet on' /varlog/messages and post  the result?

If you'd like to try our latest features, consider signing up for beta: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Sign-Up-for-Beta-Access

If you're trying to debug a network issue, take a look at this help article: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
Emerging Member
Posts: 45
Registered: ‎03-07-2014
Kudos: 5
Solutions: 2

Re: Problems with Wireless Uplink users

[ Edited ]

@UBNT-BenBuckley  Thanks Ben. There are no 'received packet on' occurrence when the client connects and the link is dropped. Here is what is logged when an iPhone tries to connect and fails:

 

Tue May  7 12:18:03 2019 daemon.info hostapd: ath2: STA 12:27:22:b3:e2:82 DRIVER: Sead AUTH addr=a0:d7:95:18:76:b7 status_code=0
Tue May  7 12:18:03 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: associated
Tue May  7 12:18:04 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 12:18:04 2019 kern.warn kernel: [50279.539746] ieee80211_ioctl_set_ratelimit: node with aid 1 and mac a0:d7:95:18:76:b7 has been tagged for rate-limiting
Tue May  7 12:18:04 2019 kern.warn kernel: [50280.069691]  ieee80211_ioctl_setparam: VLANID32 = 0
Tue May  7 12:18:04 2019 kern.warn kernel: [50280.069739] a0:d7:95:18:76:b7: node vid=0 rsn_authmode=0x00000040, ni_authmode=0x00
Tue May  7 12:18:04 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 WPA: pairwise key handshake completed (RSN)
Tue May  7 12:18:04 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.1X: authenticated - EAP type: 25 (PEAP)
Tue May  7 12:18:04 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_IP ath2: a0:d7:95:18:76:b7 / 172.21.3.235
Tue May  7 12:18:13 2019 user.info libubnt[1732]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 5 vap: ath2 sta_mac: a0:d7:95:18:76:b7 auth_ts: 50279.231649 auth_delta: 0 assoc_delta: 20000 wpa_auth_delta: 810000 radius_auth_delta: 800000 radius_auth_status: success ip_delta: 2300000 ip_assign_type: dhcp disassoc_count: 0 auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 assoc_status: 0 arp_status: yes dns_status: yes event_type: success
Tue May  7 12:18:14 2019 daemon.info hostapd: ath2: STA 12:27:22:b3:e2:82 DRIVER: Sead AUTH addr=a0:d7:95:18:76:b7 status_code=0
Tue May  7 12:18:14 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: associated
Tue May  7 12:18:15 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.1X: authenticated - EAP type: 25 (PEAP)
Tue May  7 12:18:15 2019 kern.warn kernel: [50290.901497]  ieee80211_ioctl_setparam: VLANID32 = 0
Tue May  7 12:18:15 2019 kern.warn kernel: [50290.901545] a0:d7:95:18:76:b7: node vid=0 rsn_authmode=0x00000040, ni_authmode=0x00
Tue May  7 12:18:15 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 WPA: pairwise key handshake completed (RSN)
Tue May  7 12:18:16 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 12:18:17 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 12:18:17 2019 kern.warn kernel: [50292.492958] ieee80211_ioctl_set_ratelimit: node with aid 1 and mac a0:d7:95:18:76:b7 has been tagged for rate-limiting
Tue May  7 12:18:17 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_IP ath2: a0:d7:95:18:76:b7 / 172.21.3.235
Tue May  7 12:18:22 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: sta_stats
Tue May  7 12:18:22 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: disassociated
Tue May  7 12:18:22 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 12:18:24 2019 user.info libubnt[1732]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 6 vap: ath2 sta_mac: a0:d7:95:18:76:b7 auth_ts: 50289.557297 auth_delta: 0 assoc_delta: 30000 wpa_auth_delta: 1330000 radius_auth_delta: 1310000 radius_auth_status: success ip_delta: 2860000 ip_assign_type: dhcp disassoc_count: 0 auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 assoc_status: 0 arp_status: N/A dns_status: N/A event_type: success

Then I restarded the UAP and made the same iPhone connect through it (successfully):

 

Tue May  7 12:25:49 2019 daemon.info hostapd: ath2: STA 12:27:22:b3:e2:82 DRIVER: Sead AUTH addr=a0:d7:95:18:76:b7 status_code=0
Tue May  7 12:25:49 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: associated
Tue May  7 12:25:49 2019 daemon.info hostapd: ath2: RADIUS Authentication server 172.21.1.1:1812
Tue May  7 12:25:49 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 12:25:49 2019 kern.warn kernel: [  154.321747] ieee80211_ioctl_set_ratelimit: node with aid 1 and mac a0:d7:95:18:76:b7 has been tagged for rate-limiting
Tue May  7 12:25:50 2019 kern.warn kernel: [  154.883501]  ieee80211_ioctl_setparam: VLANID32 = 0
Tue May  7 12:25:50 2019 kern.warn kernel: [  154.883547] a0:d7:95:18:76:b7: node vid=0 rsn_authmode=0x00000040, ni_authmode=0x00
Tue May  7 12:25:50 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 WPA: pairwise key handshake completed (RSN)
Tue May  7 12:25:50 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.1X: authenticated - EAP type: 25 (PEAP)
Tue May  7 12:25:52 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_IP ath2: a0:d7:95:18:76:b7 / 172.21.3.235
Tue May  7 12:25:59 2019 user.info libubnt[1732]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 1 vap: ath2 sta_mac: a0:d7:95:18:76:b7 auth_ts: 154.120099 auth_delta: 0 assoc_delta: 0 wpa_auth_delta: 740000 radius_auth_delta: 720000 radius_auth_status: success ip_delta: 2850000 ip_assign_type: dhcp disassoc_count: 0 auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 assoc_status: 0 arp_status: yes dns_status: yes event_type: success
Tue May  7 12:26:00 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 RADIUS: starting accounting session EB3C07D717A49A75
Tue May  7 12:26:00 2019 daemon.info hostapd: ath2: RADIUS Accounting server 172.21.1.1:1813

 

After this, usually after a time frame between 20 minutes to 2 hours, wireless clients start disconnecting again from the UAP. This time I waited with the same iPhone connected until got disconnected. Here is what is logged:

 

Tue May  7 12:30:24 2019 kern.warn kernel: [  428.642475] ubnt_calc_airtime_average[1428] tick counter wrapped, time_delta:21305
Tue May  7 12:32:20 2019 kern.warn kernel: [  544.900803] ubnt_calc_airtime_average[1428] tick counter wrapped, time_delta:28293
Tue May  7 12:39:49 2019 daemon.info hostapd: ath2: STA 12:27:22:b3:e2:82 DRIVER: Sead AUTH addr=a0:d7:95:18:76:b7 status_code=0
Tue May  7 12:39:49 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: associated
Tue May  7 12:39:49 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 RADIUS: stopped accounting session EB3C07D717A49A75
Tue May  7 12:39:50 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 12:39:50 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 12:39:50 2019 kern.warn kernel: [  994.740919] ieee80211_ioctl_set_ratelimit: node with aid 1 and mac a0:d7:95:18:76:b7 has been tagged for rate-limiting
Tue May  7 12:39:50 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.1X: authenticated - EAP type: 25 (PEAP)
Tue May  7 12:39:50 2019 kern.warn kernel: [  995.099765]  ieee80211_ioctl_setparam: VLANID32 = 0
Tue May  7 12:39:50 2019 kern.warn kernel: [  995.099812] a0:d7:95:18:76:b7: node vid=0 rsn_authmode=0x00000040, ni_authmode=0x00
Tue May  7 12:39:50 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 WPA: pairwise key handshake completed (RSN)
Tue May  7 12:39:50 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_IP ath2: a0:d7:95:18:76:b7 / 172.21.3.235
Tue May  7 12:39:56 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: sta_stats
Tue May  7 12:39:56 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: disassociated
Tue May  7 12:39:56 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 12:39:59 2019 user.info libubnt[1732]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 2 vap: ath2 sta_mac: a0:d7:95:18:76:b7 auth_ts: 994.335703 auth_delta: 0 assoc_delta: 20000 wpa_auth_delta: 740000 radius_auth_delta: 730000 radius_auth_status: success ip_delta: 800000 ip_assign_type: dhcp disassoc_count: 0 auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 assoc_status: 0 arp_status: N/A dns_status: N/A event_type: success
Tue May  7 12:40:17 2019 daemon.info hostapd: ath2: STA 12:27:22:b3:e2:82 DRIVER: Sead AUTH addr=a0:d7:95:18:76:b7 status_code=0
Tue May  7 12:40:17 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: associated
Tue May  7 12:40:17 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 12:40:17 2019 kern.warn kernel: [ 1021.959892] ieee80211_ioctl_set_ratelimit: node with aid 1 and mac a0:d7:95:18:76:b7 has been tagged for rate-limiting
Tue May  7 12:40:17 2019 kern.warn kernel: [ 1022.317690]  ieee80211_ioctl_setparam: VLANID32 = 0
Tue May  7 12:40:17 2019 kern.warn kernel: [ 1022.317737] a0:d7:95:18:76:b7: node vid=0 rsn_authmode=0x00000040, ni_authmode=0x00
Tue May  7 12:40:17 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 WPA: pairwise key handshake completed (RSN)
Tue May  7 12:40:17 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.1X: authenticated - EAP type: 25 (PEAP)
Tue May  7 12:40:17 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_IP ath2: a0:d7:95:18:76:b7 / 172.21.3.235
Tue May  7 12:40:22 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: sta_stats
Tue May  7 12:40:22 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: disassociated
Tue May  7 12:40:22 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 12:40:27 2019 user.info libubnt[1732]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 3 vap: ath2 sta_mac: a0:d7:95:18:76:b7 auth_ts: 1021.745301 auth_delta: 0 assoc_delta: 10000 wpa_auth_delta: 550000 radius_auth_delta: 540000 radius_auth_status: success ip_delta: 610000 ip_assign_type: dhcp disassoc_count: 0 auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 assoc_status: 0 arp_status: N/A dns_status: N/A event_type: success
Tue May  7 12:40:41 2019 user.info libubnt[1732]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 1 vap: ath0 sta_mac: 9a:8a:20:8d:6e:a5 auth_ts: 0.0 auth_delta: 0 assoc_delta: 219060000 wpa_auth_delta: 60000 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: -1 ip_assign_type: N/A disassoc_count: 0 auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 1 assoc_status: 0 arp_status: N/A dns_status: N/A event_type: fixup

Let me remind you: this issue come only with UAP models connected via wireless uplinks to others AP (any other model) and with firmware version newer than 3.9.54.9373.

 

Thanks for any suggestion you may give me!

 

Ubiquiti Employee
Posts: 1,435
Registered: ‎12-16-2015
Kudos: 310
Solutions: 10

Re: Problems with Wireless Uplink users

@andrewhotlab 4.0.32+ has a change that is likely to help with this.  Are you willing to try the latest tag (4.0.35 as of right now), it's currently in Beta?

If you'd like to try our latest features, consider signing up for beta: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Sign-Up-for-Beta-Access

If you're trying to debug a network issue, take a look at this help article: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
Emerging Member
Posts: 45
Registered: ‎03-07-2014
Kudos: 5
Solutions: 2

Re: Problems with Wireless Uplink users

@UBNT-BenBuckley  No problem, I just upgraded from 4.0.30 to 4.0.35... all seems ok after UAP's reboot. I'll be back to you as soon as I'll get any news. Thanks!

Emerging Member
Posts: 45
Registered: ‎03-07-2014
Kudos: 5
Solutions: 2

Re: Problems with Wireless Uplink users

[ Edited ]

@UBNT-BenBuckley  Even with the latest beta firmware the problem is not solved. Here are the logs when I first connected with an iPhone (just a couple of minutes after UAP boot):

 

Tue May  7 19:10:26 2019 daemon.info hostapd: ath2: STA 12:27:22:b3:e2:82 DRIVER: Sead AUTH addr=a0:d7:95:18:76:b7 status_code=0
Tue May  7 19:10:26 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: associated
Tue May  7 19:10:27 2019 daemon.info hostapd: ath2: RADIUS Authentication server 172.21.1.1:1812
Tue May  7 19:10:27 2019 kern.warn kernel: [  133.976475]  ieee80211_ioctl_setparam: VLANID32 = 0
Tue May  7 19:10:27 2019 kern.warn kernel: [  133.976521] a0:d7:95:18:76:b7: node vid=0 rsn_authmode=0x00000040, ni_authmode=0x00
Tue May  7 19:10:27 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 WPA: pairwise key handshake completed (RSN)
Tue May  7 19:10:27 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.1X: authenticated - EAP type: 25 (PEAP)
Tue May  7 19:10:27 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 19:10:27 2019 kern.warn kernel: [  134.034703] ieee80211_ioctl_set_ratelimit: node with aid 1 and mac a0:d7:95:18:76:b7 has been tagged for rate-limiting
Tue May  7 19:10:27 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_IP ath2: a0:d7:95:18:76:b7 / 172.21.3.235
Tue May  7 19:10:37 2019 user.info libubnt[1732]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 1 vap: ath2 sta_mac: a0:d7:95:18:76:b7 auth_ts: 133.824960 auth_delta: 0 assoc_delta: 10000 wpa_auth_delta: 130000 radius_auth_delta: 110000 radius_auth_status: success ip_delta: 130000 ip_assign_type: roamed disassoc_count: 0 auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 assoc_status: 0 arp_status: N/A dns_status: N/A event_type: soft failure
Tue May  7 19:10:37 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 RADIUS: starting accounting session 6C807E5D937A17AE
Tue May  7 19:10:37 2019 daemon.info hostapd: ath2: RADIUS Accounting server 172.21.1.1:1813
Tue May  7 19:11:35 2019 user.info libubnt[1732]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 1 vap: ath2 sta_mac: a0:d7:95:18:76:b7 auth_ts: 0.0 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: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 assoc_status: 0 arp_status: N/A dns_status: yes event_type: fixup

 

Here is what happened just after 17 minutes of uptime:

 

Tue May  7 19:24:43 2019 daemon.info hostapd: ath2: STA 12:27:22:b3:e2:82 DRIVER: Sead AUTH addr=a0:d7:95:18:76:b7 status_code=0
Tue May  7 19:24:43 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: associated
Tue May  7 19:24:43 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 RADIUS: stopped accounting session 6C807E5D937A17AE
Tue May  7 19:24:43 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 19:24:43 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 19:24:43 2019 kern.warn kernel: [  990.734813] ieee80211_ioctl_set_ratelimit: node with aid 1 and mac a0:d7:95:18:76:b7 has been tagged for rate-limiting
Tue May  7 19:24:44 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.1X: authenticated - EAP type: 25 (PEAP)
Tue May  7 19:24:44 2019 kern.warn kernel: [  991.112400]  ieee80211_ioctl_setparam: VLANID32 = 0
Tue May  7 19:24:44 2019 kern.warn kernel: [  991.112446] a0:d7:95:18:76:b7: node vid=0 rsn_authmode=0x00000040, ni_authmode=0x00
Tue May  7 19:24:44 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 WPA: pairwise key handshake completed (RSN)
Tue May  7 19:24:44 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_IP ath2: a0:d7:95:18:76:b7 / 172.21.3.235
Tue May  7 19:24:53 2019 user.info libubnt[1732]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 2 vap: ath2 sta_mac: a0:d7:95:18:76:b7 auth_ts: 990.342871 auth_delta: 0 assoc_delta: 20000 wpa_auth_delta: 740000 radius_auth_delta: 730000 radius_auth_status: success ip_delta: 810000 ip_assign_type: dhcp disassoc_count: 0 auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 assoc_status: 0 arp_status: yes dns_status: yes event_type: success
Tue May  7 19:24:53 2019 daemon.info hostapd: ath2: STA 12:27:22:b3:e2:82 DRIVER: Sead AUTH addr=a0:d7:95:18:76:b7 status_code=0
Tue May  7 19:24:53 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: associated
Tue May  7 19:24:54 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.1X: authenticated - EAP type: 25 (PEAP)
Tue May  7 19:24:54 2019 kern.warn kernel: [ 1001.799149]  ieee80211_ioctl_setparam: VLANID32 = 0
Tue May  7 19:24:54 2019 kern.warn kernel: [ 1001.799195] a0:d7:95:18:76:b7: node vid=0 rsn_authmode=0x00000040, ni_authmode=0x00
Tue May  7 19:24:54 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 WPA: pairwise key handshake completed (RSN)
Tue May  7 19:24:56 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 19:24:56 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 19:24:56 2019 kern.warn kernel: [ 1003.550344] ieee80211_ioctl_set_ratelimit: node with aid 1 and mac a0:d7:95:18:76:b7 has been tagged for rate-limiting
Tue May  7 19:24:56 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_IP ath2: a0:d7:95:18:76:b7 / 172.21.3.235
Tue May  7 19:25:03 2019 user.info libubnt[1732]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 3 vap: ath2 sta_mac: a0:d7:95:18:76:b7 auth_ts: 1000.714611 auth_delta: 0 assoc_delta: 20000 wpa_auth_delta: 1070000 radius_auth_delta: 1050000 radius_auth_status: success ip_delta: 1190000 ip_assign_type: dhcp disassoc_count: 0 auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 assoc_status: 0 arp_status: yes dns_status: yes event_type: success
Tue May  7 19:25:04 2019 daemon.info hostapd: ath2: STA 12:27:22:b3:e2:82 DRIVER: Sead AUTH addr=a0:d7:95:18:76:b7 status_code=0
Tue May  7 19:25:04 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: associated
Tue May  7 19:25:04 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.1X: authenticated - EAP type: 25 (PEAP)
Tue May  7 19:25:04 2019 kern.warn kernel: [ 1011.754670]  ieee80211_ioctl_setparam: VLANID32 = 0
Tue May  7 19:25:04 2019 kern.warn kernel: [ 1011.754715] a0:d7:95:18:76:b7: node vid=0 rsn_authmode=0x00000040, ni_authmode=0x00
Tue May  7 19:25:04 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 WPA: pairwise key handshake completed (RSN)
Tue May  7 19:25:06 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 19:25:07 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 19:25:07 2019 kern.warn kernel: [ 1013.909408] ieee80211_ioctl_set_ratelimit: node with aid 1 and mac a0:d7:95:18:76:b7 has been tagged for rate-limiting
Tue May  7 19:25:07 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_IP ath2: a0:d7:95:18:76:b7 / 172.21.3.235
Tue May  7 19:25:13 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: sta_stats
Tue May  7 19:25:13 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: disassociated
Tue May  7 19:25:13 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 19:25:14 2019 user.info libubnt[1732]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 4 vap: ath2 sta_mac: a0:d7:95:18:76:b7 auth_ts: 1011.80291 auth_delta: 0 assoc_delta: 20000 wpa_auth_delta: 650000 radius_auth_delta: 630000 radius_auth_status: success ip_delta: 700000 ip_assign_type: dhcp disassoc_count: 0 auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 assoc_status: 0 arp_status: N/A dns_status: N/A event_type: success
Tue May  7 19:25:42 2019 daemon.info hostapd: ath2: STA 12:27:22:b3:e2:82 DRIVER: Sead AUTH addr=a0:d7:95:18:76:b7 status_code=0
Tue May  7 19:25:43 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: associated
Tue May  7 19:25:43 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 19:25:43 2019 kern.warn kernel: [ 1050.037044] ieee80211_ioctl_set_ratelimit: node with aid 1 and mac a0:d7:95:18:76:b7 has been tagged for rate-limiting
Tue May  7 19:25:43 2019 kern.warn kernel: [ 1050.757386]  ieee80211_ioctl_setparam: VLANID32 = 0
Tue May  7 19:25:43 2019 kern.warn kernel: [ 1050.757432] a0:d7:95:18:76:b7: node vid=0 rsn_authmode=0x00000040, ni_authmode=0x00
Tue May  7 19:25:43 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 WPA: pairwise key handshake completed (RSN)
Tue May  7 19:25:43 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.1X: authenticated - EAP type: 25 (PEAP)
Tue May  7 19:25:43 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_IP ath2: a0:d7:95:18:76:b7 / 172.21.3.235
Tue May  7 19:25:48 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: sta_stats
Tue May  7 19:25:48 2019 daemon.info hostapd: ath2: STA a0:d7:95:18:76:b7 IEEE 802.11: disassociated
Tue May  7 19:25:48 2019 user.info libubnt[1732]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath2: a0:d7:95:18:76:b7 / 1
Tue May  7 19:25:53 2019 user.info libubnt[1732]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 5 vap: ath2 sta_mac: a0:d7:95:18:76:b7 auth_ts: 1049.830204 auth_delta: 0 assoc_delta: 20000 wpa_auth_delta: 900000 radius_auth_delta: 890000 radius_auth_status: success ip_delta: 950000 ip_assign_type: dhcp disassoc_count: 0 auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 0 ip_failures: 0 assoc_status: 0 arp_status: N/A dns_status: N/A event_type: success

Can I send you any other debug info to help you get deeper into the matter?

 

Ubiquiti Employee
Posts: 1,435
Registered: ‎12-16-2015
Kudos: 310
Solutions: 10

Re: Problems with Wireless Uplink users

@andrewhotlab the logs look normal, except that the station shows as being authenticated then de-authenticated in the second file.  But there's no indication as to why.

 

Can you clarify a couple of things for me?  You've said the issue is that clients who are connected to the mesh AP start getting disconnected.  How do you know this is happening?  Do clients lose their WiFi connection?  Or do they lose the ability to pass internet traffic, etc.

 

Also, I'm not 100% clear from the thread if the issue is just with clients being disconnected, or if the wireless AP is losing it's link.  Can you clarify if that's happening or not?

 

Do you see the same behavior on the RADIUS and guest network?  Or is it isolated to only RADIUS?

If you'd like to try our latest features, consider signing up for beta: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Sign-Up-for-Beta-Access

If you're trying to debug a network issue, take a look at this help article: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
Emerging Member
Posts: 40
Registered: ‎07-27-2016
Kudos: 4

Re: Problems with Wireless Uplink users


@UBNT-BenBuckley wrote:

@andrewhotlab the logs look normal, except that the station shows as being authenticated then de-authenticated in the second file.  But there's no indication as to why.

 

Can you clarify a couple of things for me?  You've said the issue is that clients who are connected to the mesh AP start getting disconnected.  How do you know this is happening?  Do clients lose their WiFi connection?  Or do they lose the ability to pass internet traffic, etc.

 

Also, I'm not 100% clear from the thread if the issue is just with clients being disconnected, or if the wireless AP is losing it's link.  Can you clarify if that's happening or not?

 

Do you see the same behavior on the RADIUS and guest network?  Or is it isolated to only RADIUS?


@UBNT-BenBuckley 

 

This is a very old problem. Answering your question this is what happens: the clients get disconnected because the wireless signal just disapear all of sudden. Usually after 5 or 10 seconds connected. After that it won't reconnect anymore or it will reconnect and get disconnected again shortly.

It started to happen after the BETA mesh implementation called " Allow meshing to another access point" in newer controllers. I think, above 5.7 version. I repeat> I'm pretty sure the problem is related to the CONTROLLER and not the firmware!

 

After I downgrade the controller, keeping the firmware version, everything got back to work beautifully. One more thing, in my case the problem occurs with UAP models.

 

Now I'm using the unifi controller 5.6.22 with firmware 3.9.19.8123. I've tested this controller version with newer firmware (3.9.42.9152) and everything worked fine. However, when I install the new controller (for instance 5.8.23), which has the new feature called "allow meshing to another access point" it wouldn't work out anymore.

 

I'm sending attached a printscreen of my controller, which shows the wireless uplink in the old version, the one that works fine.

 

Regards,

 

Sandrigo.

Capturar.PNG
Emerging Member
Posts: 45
Registered: ‎03-07-2014
Kudos: 5
Solutions: 2

Re: Problems with Wireless Uplink users

[ Edited ]

@UBNT-BenBuckley  Ok... lets start again from the beginning:

 

  1. clients lose wifi connection, and it's clearly visible to users (wifi indicator icon disappear on iOS devices and laptops), in consequence to this, smartphones switch to mobile data network (LTE, 3G, etc.), while laptops became unable to connect to any network;
  2. the wireless uplink never stops working AFAIK (I can always reach the IP address of the UAP, even when clients became unable to reconnect to it);
  3. same issue with WPA2 Enterprise, WPA2 PSK, and Guest wireless SIDs;
  4. the problem raised after upgrading UAP model's firmware to 3.9.27, was solved in firmware 3.9.45, then came back again with firmware 4.0.10 (please read my previous posts on 8-21-2018, 8-22-2018 and 12-30-2018).

This issue has dropped the trust level our customers had in UBNT products... it would be nice to finally put this trouble to end. Please ask me any debug info you may need. Thanks!

Ubiquiti Employee
Posts: 1,435
Registered: ‎12-16-2015
Kudos: 310
Solutions: 10

Re: Problems with Wireless Uplink users

@seven2016 the reason that the old controller works, where the new one doesn't, is because the new controller uses MeshV3, and the old controller uses MeshV2.

 

Allow meshing to another access point is functionality that is part of the new (MeshV3) system.

 

In MeshV2, estabilishing a wireless link between Base Station and Mesh required provisioning both the Base Station and mesh, and the link between them was fixed.  In MeshV3 this has changed.  The new system allows a mesh ap to establish a connection to different base stations without the need to provision the base station.  This makes failover much faster and not disruptive to the network.  It also requires less manual configuration.

 

The change of architecture has admittedly requried sorting out some issues, but for the majority of users that I've talked to (I know you and others in this thread are the exception) this new system is much more stable and functional.

 

The best path forward is to push through with the newer versions and fix the underlying issue.  I know we were working together a while ago and never got a conclusion.  Are you open to updating to the latest controller and firmware, and going from there?

If you'd like to try our latest features, consider signing up for beta: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Sign-Up-for-Beta-Access

If you're trying to debug a network issue, take a look at this help article: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
Ubiquiti Employee
Posts: 1,435
Registered: ‎12-16-2015
Kudos: 310
Solutions: 10

Re: Problems with Wireless Uplink users

@andrewhotlab thank you for the summary.  Is it possible for me to get remote access to your site that is having the issue?  Controller access and SSH access to the devices is preferable.

 

Also, are you willing to upgrade to the latest controller and FW?  There have been a number of fixes that might (though not guaranteed) help the issue, and starting with the newest FW is the most helpful for debug.

 

Another step we can take is that you can enable syslog server in the controller and point it to our local development log server.  From there, I just need to know your public IP address.  This makes collecting/examining logs much much easier.

If you'd like to try our latest features, consider signing up for beta: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Sign-Up-for-Beta-Access

If you're trying to debug a network issue, take a look at this help article: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
Emerging Member
Posts: 45
Registered: ‎03-07-2014
Kudos: 5
Solutions: 2

Re: Problems with Wireless Uplink users

@UBNT-BenBuckley   At this time I can make you access via web only to a controller which manages both production and test sites. I can give you admin access to the test site, where there are only two AP (one UAP and one AP-AC-LR). The controller is running 5.10.21, and here is APs status:

 

Screenshot_2019-05-07_21-05-38.png

 

As for SSH access to APs and to the server which hosts the controller (FreeBSD 11.2), I can share my screen and you can access them from there if it's ok for you.

 

No problem to upgrade firmwares to beta versions, while I'd need a bit of planning for controller's version changes.

No problem to send my controller's logs to you syslog server.

 

Thus I can send you privately my public IP address, credentials for accessing my controller and web meeting IDs (AnyDesk/TeamViewer/GoToMeeting, planning the right time for both of us), if you agree.

 

Thank you so much Ben!

Emerging Member
Posts: 40
Registered: ‎07-27-2016
Kudos: 4

Re: Problems with Wireless Uplink users


@UBNT-BenBuckley wrote:

@seven2016 the reason that the old controller works, where the new one doesn't, is because the new controller uses MeshV3, and the old controller uses MeshV2.

 

Allow meshing to another access point is functionality that is part of the new (MeshV3) system.

 

In MeshV2, estabilishing a wireless link between Base Station and Mesh required provisioning both the Base Station and mesh, and the link between them was fixed.  In MeshV3 this has changed.  The new system allows a mesh ap to establish a connection to different base stations without the need to provision the base station.  This makes failover much faster and not disruptive to the network.  It also requires less manual configuration.

 

The change of architecture has admittedly requried sorting out some issues, but for the majority of users that I've talked to (I know you and others in this thread are the exception) this new system is much more stable and functional.

 

The best path forward is to push through with the newer versions and fix the underlying issue.  I know we were working together a while ago and never got a conclusion.  Are you open to updating to the latest controller and firmware, and going from there?


You said "The change of architecture has admittedly requried sorting out some issues, but for the majority of users that I've talked to (I know you and others in this thread are the exception) this new system is much more stable and functional."

 

I ask: Are their topology similar to mine? Are they using UAP models in newer controller (MeshV3)? I don't believe it will work in the same scenery.  

 

Yes, we were working together and you didn't reply me anymore!! haha.

 

Well, I have 140 APs in the hotel. Among them, I have arround 20 wireless uplinks. I know that if I just upgrade controller and firmware to the latest version I'm going to have problems because I tried it recently. It is very complicate to change the version and have to downgrade it again if it doesn't work out. There are too many APs.

 

Couldn't you simulate this in the lab? You could use the UAP with the firmware and controller I'm using.

 

Regards,

 

Sandrigo.

Ubiquiti Employee
Posts: 1,435
Registered: ‎12-16-2015
Kudos: 310
Solutions: 10

Re: Problems with Wireless Uplink users

@seven2016 you're right, and sorry about that.  

 

I agree, using a large deployment like that for debug is not safe.  And we have tried reproducing your issue without success.  I have a couple of ideas on where to go from here, I'll go back to private message to discuss.

If you'd like to try our latest features, consider signing up for beta: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Sign-Up-for-Beta-Access

If you're trying to debug a network issue, take a look at this help article: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
Ubiquiti Employee
Posts: 1,435
Registered: ‎12-16-2015
Kudos: 310
Solutions: 10

Re: Problems with Wireless Uplink users

@andrewhotlab awesome, send me an invite to the controller.  Enable syslog and point it to 192.76.255.30 (ubnt-ut.com) and DM me with your IP address.  

 

In the meantime, I'll set-up a UAP in wireless uplink and continue trying to re-produce.

If you'd like to try our latest features, consider signing up for beta: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Sign-Up-for-Beta-Access

If you're trying to debug a network issue, take a look at this help article: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
Ubiquiti Employee
Posts: 1,435
Registered: ‎12-16-2015
Kudos: 310
Solutions: 10

Re: Problems with Wireless Uplink users

@seven2018 and @andrewhotlab I believe I have reproduced the issue, please standby.

If you'd like to try our latest features, consider signing up for beta: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Sign-Up-for-Beta-Access

If you're trying to debug a network issue, take a look at this help article: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
Ubiquiti Employee
Posts: 1,435
Registered: ‎12-16-2015
Kudos: 310
Solutions: 10

Re: Problems with Wireless Uplink users

@seven2018 and @andrewhotlab I think I've isolated where the issue was introduced.  Are you guys willing to help me confirm?  I'd like to have you install 4.0.17, which for me is last version that I cannot re-produce the issue.

 

Then I have an intermediate build, the one that I think brings in the issue, I'd like you to try.  Before I go trying to fix it, I'd like to get a confirmation that what I'm seeing in my test is also what you see in your environments.

 

If you'd like to try our latest features, consider signing up for beta: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Sign-Up-for-Beta-Access

If you're trying to debug a network issue, take a look at this help article: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
Emerging Member
Posts: 45
Registered: ‎03-07-2014
Kudos: 5
Solutions: 2

Re: Problems with Wireless Uplink users

@UBNT-BenBuckley  Thanks Ben, but unfortunately it seems to me that 4.0.17 still has the same issue: I downgraded to 4.0.17.9910 and after half an hour I found that clients were disconnecting... Man Sad

 

The latest firmware I see working in wireless uplink scenario is in the 3.9.x branch.

 

Do you need any additional log/debug info about UAP with 4.0.17?

Ubiquiti Employee
Posts: 1,435
Registered: ‎12-16-2015
Kudos: 310
Solutions: 10

Re: Problems with Wireless Uplink users

@andrewhotlab Do you have any AP's still on 4.0.10 or earlier?  For Gen1, the switch to a newer kernel came after 4.0.10, so isolating the tagged version where the issue started would be very very helpful.  I have been unable to re-produce the issue on 4.017 or earlier.

 

I have not seen anything in the logs that help spot the issue, so they won't be helpful.  I'm going to have to think a little bit about what I can change in the logging to capture useful information.

 

If you'd like to try our latest features, consider signing up for beta: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Sign-Up-for-Beta-Access

If you're trying to debug a network issue, take a look at this help article: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
Emerging Member
Posts: 45
Registered: ‎03-07-2014
Kudos: 5
Solutions: 2

Re: Problems with Wireless Uplink users

@UBNT-BenBuckley  In my experience, things started "going wrong" after upgrading UAP models from 3.9.45 to 4.0.10... howover, even if I'm pretty confident that it wouldn't work again, I just tried to force the downgrade from 4.0.17 to 4.0.10, but it failed with this error: "upgrade failed: firmware check failed (error: 130)".

 

At this very moment I have no UAP with an older firmware... do you think I'll be able to downgrade that same UAP using the TFTP method?

New Member
Posts: 19
Registered: ‎11-16-2018

Re: Problems with Wireless Uplink users

I recently upgraded my APs from 3.9.54 to 4.0.30 and controller from 5.6.40 to 5.10.23 -- and started experiencing the same symptoms as documented in this thread.  This is after over a year of stability on the 3.9 setup.  The transition from Mesh V2 to Mesh V3 was rocky (to say the least for me.)

 

I am running a single wired AP and a single AP with a wireless uplink.  The wireless one was bouncing between disconnected/isolated/connected.  I downgraded the wired AP to 4.10 and problems magically went away.  Hopefully this is helpful as you work to resolve this issue?

Reply