Can you feel the pain already?
I really do, lol. It wasn't IP exhaustion, the DHCP server is a pfsense router and it definitely had plenty available. There are multiple access points with roaming between them and the controller would just crash sometimes.
We'll see if the issue is solved, it's only been a couple of days...
Carpool7341 ah, didn't know it was roaming related. 802.11r relies on MAC address tables afaik, so it would be my conclusion that they become unresponsive when they're flooded with MAC addresses. (I can also just assume they're stored way longer than DHCP leases). At least it's solved.
I was just mentioning DHCP starvation because that is what I "did" to our company network when I hadn't noticed that my GOS phone was on "per connection" randomization. And our address pool is around 400 IPs for around 250 people (please don't ask who set it up like this lol)
Carpool7341
Nevermind, that didn't solve it. Guess it's just time to replace the hardware...
Back to the original post. Forgive my lack of knowledge on the matter. Would having your DHCP lease time set to one day not eliminate the issue? Supposing your home router does not see the same "device" in 24 hrs, would it not recycle the IP address?
I won't connect to public WiFi because it's not that secure.
If my router remembers every mac ever connected to it, I'd buy a more secure router instead.
The only reason I might use static MAC is my enterprise network needs it.