What's new

iPhone Constantly Disassociating/Associating from WiFi

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

sbsnb

Very Senior Member
I'm trying to figure out how to stop my daughter's iPhone from spamming my log file. If anyone knows how to stop this silly behavior in iPhones I would really appreciate it.

This is just one 20-minute slice while everyone is asleep and the phone is less than 20 feet away from the router. It's generating 16 KB per hour worth of log entries.

Code:
Jun 27 04:02:41 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:02:41 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:02:43 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.1.5 90:A2:5B:XX:XX:XX
Jun 27 04:02:43 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.1.5 90:A2:5B:XX:XX:XX iPhone11
Jun 27 04:03:03 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 90:A2:5B:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 27 04:07:16 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:07:16 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:07:16 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.1.5 90:A2:5B:XX:XX:XX
Jun 27 04:07:16 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.1.5 90:A2:5B:XX:XX:XX iPhone11
Jun 27 04:07:25 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 90:A2:5B:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 27 04:07:49 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:07:49 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:07:49 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.1.5 90:A2:5B:XX:XX:XX
Jun 27 04:07:49 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.1.5 90:A2:5B:XX:XX:XX iPhone11
Jun 27 04:07:58 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 90:A2:5B:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 27 04:08:23 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:08:23 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:08:23 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.1.5 90:A2:5B:XX:XX:XX
Jun 27 04:08:23 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.1.5 90:A2:5B:XX:XX:XX iPhone11
Jun 27 04:08:43 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 90:A2:5B:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 27 04:09:48 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:09:48 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:09:48 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.1.5 90:A2:5B:XX:XX:XX
Jun 27 04:09:48 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.1.5 90:A2:5B:XX:XX:XX iPhone11
Jun 27 04:10:04 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 90:A2:5B:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 27 04:10:11 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:10:11 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:10:12 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.1.5 90:A2:5B:XX:XX:XX
Jun 27 04:10:12 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.1.5 90:A2:5B:XX:XX:XX iPhone11
Jun 27 04:10:20 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 90:A2:5B:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 27 04:10:54 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:10:54 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:10:54 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.1.5 90:A2:5B:XX:XX:XX
Jun 27 04:10:54 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.1.5 90:A2:5B:XX:XX:XX iPhone11
Jun 27 04:11:02 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 90:A2:5B:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 27 04:13:15 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:13:15 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:13:15 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.1.5 90:A2:5B:XX:XX:XX
Jun 27 04:13:15 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.1.5 90:A2:5B:XX:XX:XX iPhone11
Jun 27 04:13:25 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 90:A2:5B:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 27 04:13:29 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:13:29 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:13:30 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.1.5 90:A2:5B:XX:XX:XX
Jun 27 04:13:30 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.1.5 90:A2:5B:XX:XX:XX iPhone11
Jun 27 04:13:38 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 90:A2:5B:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 27 04:13:55 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:13:55 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:13:56 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.1.5 90:A2:5B:XX:XX:XX
Jun 27 04:13:56 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.1.5 90:A2:5B:XX:XX:XX iPhone11
Jun 27 04:14:04 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 90:A2:5B:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 27 04:17:38 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:17:38 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:17:38 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.1.5 90:A2:5B:XX:XX:XX
Jun 27 04:17:38 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.1.5 90:A2:5B:XX:XX:XX iPhone11
Jun 27 04:17:54 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 90:A2:5B:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 27 04:19:26 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:19:26 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 90:A2:5B:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 27 04:19:26 dnsmasq-dhcp[393]: DHCPREQUEST(br0) 192.168.1.5 90:A2:5B:XX:XX:XX
Jun 27 04:19:26 dnsmasq-dhcp[393]: DHCPACK(br0) 192.168.1.5 90:A2:5B:XX:XX:XX iPhone11
Jun 27 04:19:35 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 90:A2:5B:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
 
Last edited:
Can you describe your environment?

Router model
Firmware version
Any other access points/AiMesh nodes?
Etc...


Sent from my iPhone using Tapatalk
 
Single RT-AC88U running Merlin 384.17.0. All known devices are set to static DHCP assignment via /jffs/conf/dnsmasq.conf.add.

Code:
dhcp-host=90:A2:5B:XX:XX:XX,iPhone11,192.168.1.5,12h
 
Roam Assist settings?
Smart Connect settings?

Those 2 things can tell a client to disassociate unnecessarily


Sent from my iPhone using Tapatalk
 
Apple devices have always been prone to doing this going all the way back to the iPhone 4. Look at the settings on the iPhone, this is not a router issue.
 
Apple devices have always been prone to doing this going all the way back to the iPhone 4. Look at the settings on the iPhone, this is not a router issue.

There are no settings on an iPhone RE Wifi to play with

So have to live with this behaviour (assuming no router settings will affect it)


Sent from my iPhone using Tapatalk
 
Roam Assist settings?
Smart Connect settings?

Those 2 things can tell a client to disassociate unnecessarily
Both are disabled.

fe4nfsh.png


Ihd8tPU.png


Apple devices have always been prone to doing this going all the way back to the iPhone 4. Look at the settings on the iPhone, this is not a router issue.
I suspect the iPhone as they have always been poorly behaved devices in more ways than one, but I don't know what settings in the iPhone can be manipulated to prevent this (I suspect it cannot be stopped short of banning the device from the network).
 
There are no settings on an iPhone RE Wifi to play with

So have to live with this behaviour (assuming no router settings will affect it)
Thanks everybody.

I think the Apple user is going to have to live with being banned from the network. I'm not ready to give up on log files that span more than 24 hours just to accommodate misbehaving devices.

For now I can ban specific devices, but I'd rather a global ban of Apple OUIs. The list of Apple OUIs is far longer than the wireless MAC filter will allow, and I don't think you can use ranges or wildcards. There has to be a way.

Off to research and experiment.
 
I suspect the iPhone as they have always been poorly behaved devices in more ways than one, but I don't know what settings in the iPhone can be manipulated to prevent this (I suspect it cannot be stopped short of banning the device from the network).
I suspect it's waking up from standby to check for updates/notifications and then going back to sleep. It doesn't always do it but coincidentally my wife's iPad did it yesterday. And I have a completely different router and firmware to you (and it was the same with my old N66U).
Code:
Jun 26 20:55:12 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 20:55:19 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 21:00:33 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 21:00:36 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 21:00:51 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 21:05:33 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 21:05:37 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 21:05:52 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 21:10:33 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 21:10:38 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 21:11:08 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 21:15:53 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 21:15:54 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 21:16:24 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 21:20:54 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 21:20:55 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 21:21:10 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 21:25:56 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 21:25:56 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 21:26:26 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 21:31:17 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 21:31:28 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 21:31:43 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 21:36:18 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 21:36:29 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 21:36:44 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 21:41:38 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 21:41:45 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 21:42:15 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 21:47:01 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 21:47:01 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 21:47:31 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 21:52:01 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 21:52:02 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 21:56:56 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 21:57:04 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 21:57:34 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 22:02:18 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 22:02:20 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 22:02:35 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 22:07:18 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 22:07:21 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 22:12:02 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 22:12:07 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 22:12:37 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 22:17:23 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 22:17:23 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 22:17:42 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 22:17:53 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 22:22:42 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 22:22:54 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 22:23:10 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 22:27:42 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 22:32:39 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 22:32:42 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 22:33:12 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 22:38:00 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 22:43:01 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 22:43:14 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 26 22:43:29 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has disconnected.
Jun 26 22:47:42 dnsmasq-dhcp[336]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
Jun 26 22:47:45 wireless: eth2 4C:B1:99:A1:60:C0 Anns-iPad.home.lan (192.168.1.211) has connected.
Jun 27 10:49:58 dnsmasq-dhcp[28970]: DHCPACK(br0) 192.168.1.211 4c:b1:99:a1:60:c0 Anns-iPad
At 22:50 I got fed up with the messages, went and unlocked the iPad to wake it up and then put it back in standby. The messages stopped.
 
I suspect it's waking up from standby to check for updates/notifications and then going back to sleep. It doesn't always do it but coincidentally my wife's iPad did it yesterday. And I have a completely different router and firmware to you (and it was the same with my old N66U).

At 22:50 I got fed up with the messages, went and unlocked the iPad to wake it up and then put it back in standby. The messages stopped.
Ideally we could tell dnsmasq to rate limit a device to x DHCP requests per time period. That way I don't have to ban them outright.
 
That wouldn't stop the WLCEVENTD messages.
Are iPhones so badly behaved that they'll DOS the router even when they can't successfully obtain an IP address from an SSID they "know" requires a DHCP assignment? Unfortunately, I don't think there's a way to prevent that short of flushing the iPhone "accidentally." ;)

My faith in humanity rests on the assumption that network programmers know better than to program infinite loops in network retry code. Can you imagine a device that did this to a server that wasn't answering a SYN?
 
Are iPhones so badly behaved that they'll DOS the router even when they can't successfully obtain an IP address from an SSID they "know" requires a DHCP assignment?
There are plenty on posts in these forums complaining about exactly that behaviour (not necessarily from iPhones).
 
There are plenty on posts in these forums complaining about exactly that behaviour (not necessarily from iPhones).
I suspect this is because RFC 2131 (Dynamic Host Configuration Protocol) allows for this behavior. It does not specifically prohibit infinite retries, stating only:
Code:
If the client receives neither a DHCPACK or a DHCPNAK message after employing the
retransmission algorithm, the client reverts to INIT state and restarts the initialization process.
 
In the household i had the same with massive flooding in the syslog, try to play/disable, location service>system services, Low Data mode for cellular. Low Power Mode to save battery life. When i disabled these settings on the i phones, the constant logging is gone. You need approval from the person who holds it though, that can be tricky :mad::)
 
Don’t know if this is helpful but I did a factory reset and wiped the JFFS partition on my ax88u. I wasn’t trying to fix the WiFi disconnects with my iPhones, it had just been awhile and I felt it was time to do a reset. Since then I haven’t noticed any issues with the iDevices in my house. What I would typically see is my phone would show the WiFi status indicator like it was connected but syslog on router showed disassociated. I’d have to disconnect/reconnect on my phone to reestablish connectivity.

for the advanced options on WiFi I’ve pretty much left the defaults except I’ve disabled universal beam forming on both bands.

Some other troubleshooting I’ve seen recommended, but haven’t tried yet are disabling mimo, disabling wmm apsd, disabling protected management frames and disabling airtime fairness.
 
If the iPhones and iPads are working correctly I see no reason worry about it. Change your log settings to a higher level so you don't see it.
I want the WLCEVENTD messages for properly functioning devices, but I don't want devices that are going to trigger them every 60 seconds 24 hours a day. Those devices are getting booted from the WAN. For now I'm just adding

dhcp-host=90:A2:5B:*:*:*,ignore
dhcp-host=90:81:2A:*:*:*,ignore

to /jffs/configs/dnsmasq.conf.add. This handles all the known Apple devices I've seen on my WAN so far. I'm hoping the lack of internet access will cause Apple device users to delete my SSID from their devices and prevent this behavior in the future.

If that doesn't work I'll explore assigning them addresses with static routes that prevent them from accessing WAN or LAN.
 
I want the WLCEVENTD messages for properly functioning devices, but I don't want devices that are going to trigger them every 60 seconds 24 hours a day. Those devices are getting booted from the WAN. For now I'm just adding

dhcp-host=90:A2:5B:*:*:*,ignore
dhcp-host=90:81:2A:*:*:*,ignore

to /jffs/configs/dnsmasq.conf.add. This handles all the known Apple devices I've seen on my WAN so far. I'm hoping the lack of internet access will cause Apple device users to delete my SSID from their devices and prevent this behavior in the future.

If that doesn't work I'll explore assigning them addresses with static routes that prevent them from accessing WAN or LAN.

This is a bizarre statement. Surely only users of Apple devices that you have given your Wi-fi key to are causing this issue?


Sent from my iPhone using Tapatalk
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top