Reply
New Member
Posts: 24
Registered: ‎10-18-2017
Kudos: 1
Solutions: 1

Continued problems with iPads and only iPads

I have a home UNIFI setup with a USG3, two AP-AC-Lite, an AP-AC-Mesh, and an AP-AC-In wall.  

 

Everything has worked great except the two iPads in the house periodically do not get an IP.  Of the 20 or so wireless clients these two iPads are the only devices to exhibit this problem.

 

I can be actively using the iPad, watching YouTube for example, and the video will pause.  At that point I notice that the wifi signal strenght symbol is missing from the top menu and I have to enter settings, turn off wifi, and turn it back on.  The iPad then connects to my network and gets and IP and is generally fine for another day or so.  Sometimes the problem happens right off again, other times it seems to go days.

 

I have seen other threads dedicated to the problem but have yet to come upon a solution.

 

Here are the syslogs from the most recent event.  Is there anything here that points to the problem and a solution?

 

Mar 13 14:32:00 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") hostapd: ath4: STA 02:9f:c2:25:6a:77 DRIVER: Sead AUTH addr=d0:4f:7e:39:4f:28 status_code=0
Mar 13 14:32:00 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") syslog: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath4: d0:4f:7e:39:4f:28 / 10
Mar 13 14:32:00 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") kernel: [2392019.740000] wmi_unified_event_rx : no registered event handler : event id 0x901b
Mar 13 14:32:00 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") hostapd: ath4: STA d0:4f:7e:39:4f:28 IEEE 802.11: associated
Mar 13 14:32:02 192.168.15.13 ("U7IW,f09fc2fce2ed,v3.9.19.8123") hostapd: ath4: STA d0:4f:7e:39:4f:28 IEEE 802.11: disassociated
Mar 13 14:32:02 192.168.15.13 ("U7IW,f09fc2fce2ed,v3.9.19.8123") syslog: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath4: d0:4f:7e:39:4f:28 / 1
Mar 13 14:32:00 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") kernel: [2392020.420000] [wifi1] FWLOG: [33498142] RATE: ChainMask 3, phymode 1044489, ni_flags 0x02233006, vht_mcs_set 0xfffa, ht_mcs_set 0xffff, legacy_rate_set 0x1f20401
Mar 13 14:32:04 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") syslog: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath4: d0:4f:7e:39:4f:28 / 10
Mar 13 14:32:09 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") hostapd: ath4: STA d0:4f:7e:39:4f:28 IEEE 802.11: deauthenticated due to local deauth request
Mar 13 14:32:27 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") hostapd: ath1: STA f2:9f:c2:24:6a:77 DRIVER: Sead AUTH addr=d0:4f:7e:39:4f:28 status_code=0
Mar 13 14:32:27 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") syslog: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath1: d0:4f:7e:39:4f:28 / 4
Mar 13 14:32:27 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") hostapd: ath1: STA d0:4f:7e:39:4f:28 IEEE 802.11: associated
Mar 13 14:32:27 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") hostapd: ath1: STA d0:4f:7e:39:4f:28 WPA: pairwise key handshake completed (RSN)
Mar 13 14:32:27 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") syslog: wevent.ubnt_custom_event(): EVENT_STA_IP ath1: d0:4f:7e:39:4f:28 / 192.168.15.226
Mar 13 14:32:35 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") hostapd: ath4: STA 02:9f:c2:25:6a:77 DRIVER: Sead AUTH addr=d0:4f:7e:39:4f:28 status_code=0
Mar 13 14:32:35 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") syslog: wevent.ubnt_custom_event(): EVENT_STA_JOIN ath4: d0:4f:7e:39:4f:28 / 10
Mar 13 14:32:35 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") kernel: [2392055.140000] wmi_unified_event_rx : no registered event handler : event id 0x901b
Mar 13 14:32:35 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") hostapd: ath4: STA d0:4f:7e:39:4f:28 IEEE 802.11: associated
Mar 13 14:32:35 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") hostapd: ath1: STA d0:4f:7e:39:4f:28 IEEE 802.11: disassociated
Mar 13 14:32:35 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") syslog: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath1: d0:4f:7e:39:4f:28 / 4
Mar 13 14:32:35 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") hostapd: ath4: STA d0:4f:7e:39:4f:28 WPA: pairwise key handshake completed (RSN)
Mar 13 14:32:35 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") syslog: wevent.ubnt_custom_event(): EVENT_STA_IP ath4: d0:4f:7e:39:4f:28 / 192.168.15.226
Mar 13 14:32:35 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") kernel: [2392055.420000] [wifi1] FWLOG: [33534392] RATE: ChainMask 3, phymode 1044489, ni_flags 0x02233006, vht_mcs_set 0xfffa, ht_mcs_set 0xffff, legacy_rate_set 0x1ffb1c3
Mar 13 14:32:35 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") kernel: [2392055.420000] [wifi1] FWLOG: [33534403] WAL_DBGID_SECURITY_ALLOW_DATA ( 0x4369ec )
Mar 13 14:32:35 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") kernel: [2392055.420000] [wifi1] FWLOG: [33534424] RATE: ChainMask 3, phymode 1044490, ni_flags 0x02233006, vht_mcs_set 0xfffa, ht_mcs_set 0xffff, legacy_rate_set 0x80801c1d
Mar 13 14:32:35 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") stamgr: kick-sta-on d0:4f:7e:39:4f:28 ath1 (reason:On other VAP)
Mar 13 14:32:35 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") kernel: [2392055.490000]  ieee80211_ioctl_kickmac[14812]
Mar 13 14:32:45 192.168.15.8 ("U7LT,f09fc2236a77,v3.9.19.8123") hostapd: ath4: STA d0:4f:7e:39:4f:28 RADIUS: starting accounting session 5A873B80-0000085D

 

Established Member
Posts: 1,762
Registered: ‎01-30-2016
Kudos: 818
Solutions: 217

Re: Continued problems with iPads and only iPads

I have had dozends Ipad on the network and fortunately never had an issue.

 

On your SSID try to set the DTIM value to 3 or greater.

I'm eager to hear if it helps.

Please give kudo's to the people who have helped you and mark your thread as solved when you receive a solution to your issue.
For a deeper understanding on how WiFi works.
Certified UEWA, ACSP, ACTC
New Member
Posts: 24
Registered: ‎10-18-2017
Kudos: 1
Solutions: 1

Re: Continued problems with iPads and only iPads

I have it set to 3 already.

Highlighted
Established Member
Posts: 1,762
Registered: ‎01-30-2016
Kudos: 818
Solutions: 217

Re: Continued problems with iPads and only iPads

And have you tried much larger values? like 150? Somewhere I stumbled over that number someone said that fixed an issue with Apple devices.

Please give kudo's to the people who have helped you and mark your thread as solved when you receive a solution to your issue.
For a deeper understanding on how WiFi works.
Certified UEWA, ACSP, ACTC
New Member
Posts: 24
Registered: ‎10-18-2017
Kudos: 1
Solutions: 1

Re: Continued problems with iPads and only iPads

I have only had it set to 3.  I can try 150 and see what happens.

 

New Member
Posts: 24
Registered: ‎10-18-2017
Kudos: 1
Solutions: 1

Re: Continued problems with iPads and only iPads

Changed it to 150.

 

About 5 minutes later my son asked if I was doing something to the WiFi.  His iPhone showed a connection, had an IP but was not able to send or receive any traffic.  Slightly different the what the iPad's do when set to 3.

 

I had to turn off wifi on his phone an turn it back on again.

 

Will leave it set to 150 for awhile and see if any other issues crop up.

 

New Member
Posts: 24
Registered: ‎10-18-2017
Kudos: 1
Solutions: 1

Re: Continued problems with iPads and only iPads

That seemed to just make it worse.

 

Now the iPhones are having lots of problems.

 

Going to revert back to 3.

 

Established Member
Posts: 1,762
Registered: ‎01-30-2016
Kudos: 818
Solutions: 217

Re: Continued problems with iPads and only iPads

Thanks for the feedback...

that’s really odd this recurring Apple issues. 

Please give kudo's to the people who have helped you and mark your thread as solved when you receive a solution to your issue.
For a deeper understanding on how WiFi works.
Certified UEWA, ACSP, ACTC
SuperUser
Posts: 8,233
Registered: ‎01-10-2012
Kudos: 4753
Solutions: 371

Re: Continued problems with iPads and only iPads

Since you already had DITM set to 3, have you played with any other advanced settings?  Min RSSI?  Fast Roaming?  Balancing?


If so, start turning them OFF.  When the problem goes away, you will find out what was causing it.  

 

Other than DITM (which the default of 1 is dumb since it negatively affects iOS devices if other than 3), and especially at home, people shouldn't need to be turning on advanced features but I find sites with everything turned on and the reason is often "well it's there and they are advanced and I want to be advanced"....   sigh...

When you receive a solution to your question/issue, don't forget to mark your thread as solved and to give kudo's to the people who have helped you out!

Having wifi problems? Take a look here first: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
New Member
Posts: 24
Registered: ‎10-18-2017
Kudos: 1
Solutions: 1

Re: Continued problems with iPads and only iPads

All other wireless settings are default. 

Reply