> I hate that they don't even go through DHCP most of the time and just assume that last known IP is still available, all to "help it connect quicker".
Oh, I forgot all about that.
I worked at a K-12 that deployed Apple devices awhile back, and this behavior was a nightmare for network management. Especially for travelling teachers who would take their device to several different buildings throughout the day (and, therefore, different IP subnets with the same WiFi name).
The worst part was that some of the devices would just... never emit a DHCPREQUEST. They'd either ignore the fact that there was an address collision confusing everyone else's ARP tables, or connect to the network but stick with an IP that had no route to a gateway. As I recall -- it's been awhile -- even setting the lease duration to something very low didn't seem to help. Indeed, I think that made it worse.
It was bad enough at one point that we had those devices with the worst behavior set up with reserved IPs and a hidden WiFi network that was a district-wide VLAN with a single subnet.
Oh, I forgot all about that.
I worked at a K-12 that deployed Apple devices awhile back, and this behavior was a nightmare for network management. Especially for travelling teachers who would take their device to several different buildings throughout the day (and, therefore, different IP subnets with the same WiFi name).
The worst part was that some of the devices would just... never emit a DHCPREQUEST. They'd either ignore the fact that there was an address collision confusing everyone else's ARP tables, or connect to the network but stick with an IP that had no route to a gateway. As I recall -- it's been awhile -- even setting the lease duration to something very low didn't seem to help. Indeed, I think that made it worse.
It was bad enough at one point that we had those devices with the worst behavior set up with reserved IPs and a hidden WiFi network that was a district-wide VLAN with a single subnet.