Reply
Highlighted
New Member
Posts: 13
Registered: ‎07-05-2017
Accepted Solution

Losing connectivity from certain clients

I have 2 UniFi AP-Pro units and one UniFi AP unit spread out across a 2 story home. The AP-Pro units handle 5GHz and all 3 handle 2.4GHz each one allocated to channels 1 6 and 11. There is a minor amount of competing networks on 2.4GHz and almost none on 5Ghz.

 

Over the past few months I've been having intermittent issues with one of my android clients frequently disconnecting on wifi. This is the only Android P device(Pixel XL) I have. The error keeps stating "network_selection_disabled_dhcp_failure". I have almost no issues on other wireless networks. My office network is exclusively 5GHz and I have no trouble on 2.4Ghz networks.

 

At this point I'm thinking it's either something wonky with my 5GHz setup on the AP-Pros or IPv6 but I'm having a hard time narrowing down which is the source. Disabling either for an extended period for testing would be less than ideal.

 

I've attached a log dump of the syslogs on the APs that gets forwarded to my router(desktop build with plenty of storage). Any suggestions/insight would be appreciated. Thanks.


Accepted Solutions
Senior Member
Posts: 10,544
Registered: ‎08-04-2017
Kudos: 1711
Solutions: 513

Re: Losing connectivity from certain clients

Hello @survient,

 

Thanks for reporting back!

 

 

Regards,

Glenn R.

Cloud Hosted Controllers | Glenn R. | UniFi Installation/Easy Update Scripts | UniFi-Video Installation/Easy Update Scripts | UniFi-VoIP Installation Scripts
USG-4-PRO • USG
USW-48-500W • USW-24-POE-250W 2x • USW-16-POE-150W • USW-24 • USW-8-150W • USW-8
UAP XG • UAP-SHD • UAP-HD • UAP-NanoHD • UAP-AC-PRO 2x • UAP-AC-LITE • UAP-AC-IW • UAP-AC-M
UCK-G2 • UCK

View solution in original post


All Replies
Established Member
Posts: 2,077
Registered: ‎04-21-2015
Kudos: 279
Solutions: 92

Re: Losing connectivity from certain clients

Do the Android phones complete disconnect from the wireless SSID and unable to join it back automatically or they actually stay connected with no internet access?

Thanks,
Myky
--------------------------------------------------------------------------------------------------------------------------------------------------
Don`t blame the device as it`s always doing what you have asked it to do, this is not always the same as what you want.
Senior Member
Posts: 10,544
Registered: ‎08-04-2017
Kudos: 1711
Solutions: 513

Re: Losing connectivity from certain clients

Hello @survient,

 

Could you share your system config?

Settings > Maintenance > Support Info > Show System Config

 

You may aswell update the UAP to 4.0.9

 

 

Regards,

Glenn R.

Cloud Hosted Controllers | Glenn R. | UniFi Installation/Easy Update Scripts | UniFi-Video Installation/Easy Update Scripts | UniFi-VoIP Installation Scripts
USG-4-PRO • USG
USW-48-500W • USW-24-POE-250W 2x • USW-16-POE-150W • USW-24 • USW-8-150W • USW-8
UAP XG • UAP-SHD • UAP-HD • UAP-NanoHD • UAP-AC-PRO 2x • UAP-AC-LITE • UAP-AC-IW • UAP-AC-M
UCK-G2 • UCK
New Member
Posts: 13
Registered: ‎07-05-2017

Re: Losing connectivity from certain clients

It disconnects completely and then tries to reconnect. It may stay connected for around 30 seconds to a minute and then disconnects afterwards. It seems to have internet connectivity while connected. I have Enable Wi-Fi Verbose Logging so I see the error as it happens and it doesn't say "Connected, no internet". The behavior is fairly intermittent and either it has these series of connectivity "fits" or it connects and stays connected for a period of time. I'm running controller version 5.9.29 (Build: atag_5.9.29_11384) and the latest firmware my controller seems to want to pull down is 3.9.54.9373. I can manually push the 4.09 release but I'm not sure if that's the best idea or whether to let the controller software determine that. Thanks again for the help so far.
systemConfig.png
Established Member
Posts: 2,077
Registered: ‎04-21-2015
Kudos: 279
Solutions: 92

Re: Losing connectivity from certain clients

Ohh boy, TX power level is too high. Wait for Glenn’s response and reduce it
Thanks,
Myky
--------------------------------------------------------------------------------------------------------------------------------------------------
Don`t blame the device as it`s always doing what you have asked it to do, this is not always the same as what you want.
Senior Member
Posts: 10,544
Registered: ‎08-04-2017
Kudos: 1711
Solutions: 513

Re: Losing connectivity from certain clients

Hello @survient,

 

I have been running 4.0.9 on all my clients and it works great, I highly recommend upgrading to it.

 

Also please use the following Radio Settings ( different channels on each UAP )

Devices > UAP > Config > Radios

 

2.4 GHz

Channel width: HT20

Chanel: 1/6/11 | Choose one of these channels, a RF scan will help you choose the most clean one.

Transmit Power: Low/Medium

 

5GHz

Channel width: VHT40 | Optional VHT80 might decrease wireless stability

Chanel: 36/44 | Optional (149/157) Choose one of these channels, a RF scan will help you choose the most clean one. Avoid using DFS Channels

Transmit Power: Medium/High

 

 

Regards,

Glenn R.

Cloud Hosted Controllers | Glenn R. | UniFi Installation/Easy Update Scripts | UniFi-Video Installation/Easy Update Scripts | UniFi-VoIP Installation Scripts
USG-4-PRO • USG
USW-48-500W • USW-24-POE-250W 2x • USW-16-POE-150W • USW-24 • USW-8-150W • USW-8
UAP XG • UAP-SHD • UAP-HD • UAP-NanoHD • UAP-AC-PRO 2x • UAP-AC-LITE • UAP-AC-IW • UAP-AC-M
UCK-G2 • UCK
New Member
Posts: 13
Registered: ‎07-05-2017

Re: Losing connectivity from certain clients

I upgraded to 4.09 and adjusted the settings but I'm still getting the same repeats:

Dec 05 17:53:55 qrouter socat[2980]: <30>Dec  5 17:53:55 ("BZ2,dc9fdbf07e5c,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: sta_stats
Dec 05 17:53:55 qrouter socat[2980]: <30>Dec  5 17:53:55 ("BZ2,dc9fdbf07e5c,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: disassociated
Dec 05 17:53:55 qrouter socat[2980]: <14>Dec  5 17:53:55 ("BZ2,dc9fdbf07e5c,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath1: 40:4e:36:1e:e5:f2 / 1
Dec 05 17:53:58 qrouter socat[2980]: <30>Dec  5 17:53:59 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 26:a4:3c:03:06:f1 DRIVER: Sead AUTH addr=40:4e:36:1e:e5:f2 status_code=0
Dec 05 17:53:58 qrouter socat[2980]: <30>Dec  5 17:53:59 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: associated
Dec 05 17:53:58 qrouter socat[2980]: <14>Dec  5 17:53:59 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath1: 40:4e:36:1e:e5:f2 / 1
Dec 05 17:53:58 qrouter socat[2980]: <30>Dec  5 17:53:59 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 WPA: pairwise key handshake completed (RSN)
Dec 05 17:53:59 qrouter socat[2980]: <14>Dec  5 17:53:59 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_IP ath1: 40:4e:36:1e:e5:f2 / 192.168.10.218
Dec 05 17:54:08 qrouter socat[2980]: <14>Dec  5 17:54:09 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 1 event_type: success vap: ath1 sta_mac: 40:4e:36:1e:e5:f2 auth_ts: 31628.826267 auth_delta: 1000 assoc_delta: 5000 wpa_auth_delta: 22000 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: 99000 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: yes dns_status: yes
Dec 05 17:54:08 qrouter socat[2980]: <30>Dec  5 17:54:09 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 RADIUS: starting accounting session 14248A9668780DAA
Dec 05 17:55:11 qrouter socat[2980]: <30>Dec  5 17:55:11 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: sta_stats
Dec 05 17:55:11 qrouter socat[2980]: <30>Dec  5 17:55:11 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: disassociated
Dec 05 17:55:11 qrouter socat[2980]: <14>Dec  5 17:55:11 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath1: 40:4e:36:1e:e5:f2 / 1
Dec 05 17:55:14 qrouter socat[2980]: <30>Dec  5 17:55:14 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 26:a4:3c:03:06:f1 DRIVER: Sead AUTH addr=40:4e:36:1e:e5:f2 status_code=0
Dec 05 17:55:14 qrouter socat[2980]: <30>Dec  5 17:55:14 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: associated
Dec 05 17:55:14 qrouter socat[2980]: <14>Dec  5 17:55:14 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath1: 40:4e:36:1e:e5:f2 / 1
Dec 05 17:55:14 qrouter socat[2980]: <30>Dec  5 17:55:14 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 WPA: pairwise key handshake completed (RSN)
Dec 05 17:55:14 qrouter socat[2980]: <14>Dec  5 17:55:15 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_IP ath1: 40:4e:36:1e:e5:f2 / 192.168.10.218
Dec 05 17:55:24 qrouter socat[2980]: <14>Dec  5 17:55:24 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 2 event_type: success vap: ath1 sta_mac: 40:4e:36:1e:e5:f2 auth_ts: 31704.325098 auth_delta: 0 assoc_delta: 4000 wpa_auth_delta: 17000 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: 99000 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: yes dns_status: yes
Dec 05 17:55:24 qrouter socat[2980]: <30>Dec  5 17:55:24 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 RADIUS: starting accounting session 08A660B610C704D5
Dec 05 17:55:51 qrouter socat[2980]: <30>Dec  5 17:55:52 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: sta_stats
Dec 05 17:55:51 qrouter socat[2980]: <30>Dec  5 17:55:52 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: disassociated
Dec 05 17:55:51 qrouter socat[2980]: <14>Dec  5 17:55:52 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath1: 40:4e:36:1e:e5:f2 / 1
Dec 05 17:55:54 qrouter socat[2980]: <30>Dec  5 17:55:54 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 26:a4:3c:03:06:f1 DRIVER: Sead AUTH addr=40:4e:36:1e:e5:f2 status_code=0
Dec 05 17:55:54 qrouter socat[2980]: <30>Dec  5 17:55:54 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: associated
Dec 05 17:55:54 qrouter socat[2980]: <14>Dec  5 17:55:54 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath1: 40:4e:36:1e:e5:f2 / 1
Dec 05 17:55:54 qrouter socat[2980]: <30>Dec  5 17:55:54 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 WPA: pairwise key handshake completed (RSN)
Dec 05 17:55:54 qrouter socat[2980]: <14>Dec  5 17:55:55 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_IP ath1: 40:4e:36:1e:e5:f2 / 192.168.10.218
Dec 05 17:56:01 qrouter socat[2980]: <30>Dec  5 17:56:02 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: sta_stats
Dec 05 17:56:01 qrouter socat[2980]: <30>Dec  5 17:56:02 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: disassociated
Dec 05 17:56:01 qrouter socat[2980]: <14>Dec  5 17:56:02 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath1: 40:4e:36:1e:e5:f2 / 1
Dec 05 17:56:04 qrouter socat[2980]: <30>Dec  5 17:56:05 ("U7P,24a43c020485,v4.0.9.9636") hostapd: ath1: STA 26:a4:3c:03:04:85 DRIVER: Sead AUTH addr=40:4e:36:1e:e5:f2 status_code=0
Dec 05 17:56:04 qrouter socat[2980]: <30>Dec  5 17:56:05 ("U7P,24a43c020485,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: associated
Dec 05 17:56:04 qrouter socat[2980]: <14>Dec  5 17:56:05 ("U7P,24a43c020485,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath1: 40:4e:36:1e:e5:f2 / 3
Dec 05 17:56:04 qrouter socat[2980]: <14>Dec  5 17:56:04 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 3 event_type: success vap: ath1 sta_mac: 40:4e:36:1e:e5:f2 auth_ts: 31744.329317 auth_delta: 0 assoc_delta: 4000 wpa_auth_delta: 33000 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: 143000 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
Dec 05 17:56:04 qrouter socat[2980]: <30>Dec  5 17:56:05 ("U7P,24a43c020485,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 WPA: pairwise key handshake completed (RSN)
Dec 05 17:56:04 qrouter socat[2980]: <14>Dec  5 17:56:05 ("U7P,24a43c020485,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_IP ath1: 40:4e:36:1e:e5:f2 / 192.168.10.218
Dec 05 17:56:14 qrouter socat[2980]: <14>Dec  5 17:56:15 ("U7P,24a43c020485,v4.0.9.9636") syslog: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 1 event_type: success vap: ath1 sta_mac: 40:4e:36:1e:e5:f2 auth_ts: 31757.406046 auth_delta: 0 assoc_delta: 5000 wpa_auth_delta: 23000 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: 134000 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: yes dns_status: yes
Dec 05 17:56:14 qrouter socat[2980]: <30>Dec  5 17:56:15 ("U7P,24a43c020485,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 RADIUS: starting accounting session E636796110D948E3
Dec 05 17:56:16 qrouter socat[2980]: <14>Dec  5 17:56:17 ("U7P,24a43c0206f1,v4.0.9.9636") kernel: [31766.903000] ar9300_abort_tx_dma[938]: ar9300_stop_dma_receive failed
Dec 05 17:56:16 qrouter socat[2980]: <14>Dec  5 17:56:17 ("U7P,24a43c0206f1,v4.0.9.9636") kernel: [31766.904000] ar9300_reset[6063]: ar9300_stop_dma_receive failed
Dec 05 17:56:45 qrouter socat[2980]: <14>Dec  5 17:56:46 ("U7P,24a43c0206f1,v4.0.9.9636") kernel: [31795.774000] ar9300_abort_tx_dma[938]: ar9300_stop_dma_receive failed
Dec 05 17:56:45 qrouter socat[2980]: <14>Dec  5 17:56:46 ("U7P,24a43c0206f1,v4.0.9.9636") kernel: [31795.774000] ar9300_reset[6063]: ar9300_stop_dma_receive failed
Dec 05 17:57:08 qrouter socat[2980]: <14>Dec  5 17:57:09 ("U7P,24a43c0206f1,v4.0.9.9636") kernel: [31818.712000] ar9300_abort_tx_dma[938]: ar9300_stop_dma_receive failed
Dec 05 17:57:08 qrouter socat[2980]: <14>Dec  5 17:57:09 ("U7P,24a43c0206f1,v4.0.9.9636") kernel: [31818.712000] ar9300_reset[6063]: ar9300_stop_dma_receive failed
Dec 05 17:57:16 qrouter socat[2980]: <30>Dec  5 17:57:17 ("U7P,24a43c020485,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: sta_stats
Dec 05 17:57:16 qrouter socat[2980]: <30>Dec  5 17:57:17 ("U7P,24a43c020485,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: disassociated
Dec 05 17:57:16 qrouter socat[2980]: <14>Dec  5 17:57:17 ("U7P,24a43c020485,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath1: 40:4e:36:1e:e5:f2 / 3
Dec 05 17:58:00 qrouter socat[2980]: <30>Dec  5 17:58:00 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 26:a4:3c:03:06:f1 DRIVER: Sead AUTH addr=40:4e:36:1e:e5:f2 status_code=0
Dec 05 17:58:00 qrouter socat[2980]: <30>Dec  5 17:58:00 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 IEEE 802.11: associated
Dec 05 17:58:00 qrouter socat[2980]: <14>Dec  5 17:58:00 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath1: 40:4e:36:1e:e5:f2 / 1
Dec 05 17:58:00 qrouter socat[2980]: <30>Dec  5 17:58:00 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 WPA: pairwise key handshake completed (RSN)
Dec 05 17:58:00 qrouter socat[2980]: <14>Dec  5 17:58:00 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_custom_event(): EVENT_STA_IP ath1: 40:4e:36:1e:e5:f2 / 192.168.10.218
Dec 05 17:58:10 qrouter socat[2980]: <14>Dec  5 17:58:10 ("U7P,24a43c0206f1,v4.0.9.9636") syslog: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 1 event_type: success vap: ath1 sta_mac: 40:4e:36:1e:e5:f2 auth_ts: 31870.78040 auth_delta: 1000 assoc_delta: 5000 wpa_auth_delta: 30000 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: 119000 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: yes dns_status: yes
Dec 05 17:58:10 qrouter socat[2980]: <30>Dec  5 17:58:10 ("U7P,24a43c0206f1,v4.0.9.9636") hostapd: ath1: STA 40:4e:36:1e:e5:f2 RADIUS: starting accounting session B7F2021D3CB22FCA
Dec 05 17:58:23 qrouter socat[2980]: <14>Dec  5 17:58:24 ("U7P,24a43c0206f1,v4.0.9.9636") kernel: [31893.685000] ar9300_abort_tx_dma[938]: ar9300_stop_dma_receive failed
Dec 05 17:58:23 qrouter socat[2980]: <14>Dec  5 17:58:24 ("U7P,24a43c0206f1,v4.0.9.9636") kernel: [31893.686000] ar9300_reset[6063]: ar9300_stop_dma_receive failed

systemConfig (1).png

New Member
Posts: 13
Registered: ‎07-05-2017

Re: Losing connectivity from certain clients

I did some further troubleshooting and it looks like it's a bug with Android P and IPv6. As soon as I updated my firewall to block all IPv6 traffic from the affected client using the MAC ID it was able to connect and stay connected just fine. I will escalate to the vendor. Thanks for the suggestions I think regardless my wifi coverage has improved.

Senior Member
Posts: 10,544
Registered: ‎08-04-2017
Kudos: 1711
Solutions: 513

Re: Losing connectivity from certain clients

Hello @survient,

 

Thanks for reporting back!

 

 

Regards,

Glenn R.

Cloud Hosted Controllers | Glenn R. | UniFi Installation/Easy Update Scripts | UniFi-Video Installation/Easy Update Scripts | UniFi-VoIP Installation Scripts
USG-4-PRO • USG
USW-48-500W • USW-24-POE-250W 2x • USW-16-POE-150W • USW-24 • USW-8-150W • USW-8
UAP XG • UAP-SHD • UAP-HD • UAP-NanoHD • UAP-AC-PRO 2x • UAP-AC-LITE • UAP-AC-IW • UAP-AC-M
UCK-G2 • UCK
New Member
Posts: 13
Registered: ‎07-05-2017

Re: Losing connectivity from certain clients

It looks like it may have been the "Private DNS" setting on the phone in tandem with ipv6. As soon as I set "Private DNS" to off and re-enabled ipv6(opened firewall rule, turned wifi on/off) it was able to connect just fine and stay connected. I don't really use the private DNS feature but I'll probably still escalate to the vendor just in case.

 

Thanks again for the assistance!

Senior Member
Posts: 10,544
Registered: ‎08-04-2017
Kudos: 1711
Solutions: 513

Re: Losing connectivity from certain clients

Hello @survient,

 

I heard that Private DNS screws up alot of users....

Thanks for reporting back! Hurray

 

 

Regards,

Glenn R.

Cloud Hosted Controllers | Glenn R. | UniFi Installation/Easy Update Scripts | UniFi-Video Installation/Easy Update Scripts | UniFi-VoIP Installation Scripts
USG-4-PRO • USG
USW-48-500W • USW-24-POE-250W 2x • USW-16-POE-150W • USW-24 • USW-8-150W • USW-8
UAP XG • UAP-SHD • UAP-HD • UAP-NanoHD • UAP-AC-PRO 2x • UAP-AC-LITE • UAP-AC-IW • UAP-AC-M
UCK-G2 • UCK
New Member
Posts: 13
Registered: ‎07-05-2017

Re: Losing connectivity from certain clients

.... and it's back, though it took a bit longer. Definitely something ipv6 related so for now I've disabled it for the affected client by mac address and reported to the vendor.

Reply