NOTE: You may want to turn off full MAC randomization

Ammako I may be wrong but I don't think if it was secure Graphene would have an option to only allow LTE for reducing attack surface because. Historically it was used to attack a lot of devices with NSO software etc.

missing-root back in the day, anti cheat companies used to serve bans to hackers and cheaters in certain video games based of MAC address. Was referred to as a Hardware ban.

Sucked to see that as a pre teenager, knowing u could never play that game ever again.

CuriousFox In Settings > Network and Internet > Internet > Saved networks > click on the Wi-Fi network you want to change > Privacy > select "Use per-network randomized MAC".

Ammako Cellular networks are neither secure nor private. There is abundant scientific literature on the topic.

ToffoliGate Thank you! That did the trick!!

missing-root This might have solved the weirdest WiFi issue I was having. Even with Cisco hardware (admittedly old). Why would the WiFi controller store all the MAC addresses for old sessions? Never would have guessed.

Carpool7341 Cisco hardware

Can you feel the pain already?

Jokes aside, hardware, especially when it's a little older, doesn't know the concept of MAC randomization. Some (most) DHCP implementations use MAC addresses to recognize devices, so that they can reserve an IP per device. This of course leads to DHCP pool flooding/DHCP starvation where the whole address pool gets eaten up by "dead" leases. Especially with longer lease times, this can lead to constant issues.

DeletedUser87

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)

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.