Just noticed its available as of yesterday/today:
Not sure what Mandatory DHCP is yet though lol
I'm going to guess mandatory DHCP means that packets coming from clients for which no DHCP lease is known are dropped. I often use static IP addresses on hotel Wi-Fi with exhausted DHCP ranges (common problem). This would stop me from doing that...
Found it 😃
Upgraded my lab just now, the option only shows up when you upgrade to 26.1
My assumption is that it is equivalent to the Cisco WLC option (if your familiar) called DHCP Required, which I personally think is great. Another layer of security (so to speak).
"won't be able to associate" -> interesting
Since DHCP takes place after association I'm not sure if that's even possible.
Aruba has this setting. You can associate, but if you have a static it won't pass your traffic. It's sorta like what Dynamic ARP Inspection and IP Source Guard do on the wired side.
So with this enabled, if a client on this VLAN had a static IP set it would not allow them network access?
Thanks, not sure if I have any static clients out there................there shouldn't be but you never know.
@Bossnine wrote:So with this enabled, if a client on this VLAN had a static IP set it would not allow them network access?
Don't think you should generalize that. I think it's specifically for clients that are wirelessly connected.
Sorry if I didn't make that clear as well, it was implied since we were discussing wifi.
@Bossnine wrote:Sorry if I didn't make that clear as well, it was implied since we were discussing wifi.
Okay, just wanted to make sure 🤓.
We tried this but I hadn't noticed the known issue of sporadic packet loss etc. for L3 roaming, took down half a site so rolled back! A second less busy site seems okay though...
Is anyone having issues with clients getting DHCP on 26.1?
Most of our APs seem to be working fine but several of our MR72s are having issues right now. Rebooting them seems to help for a while.
I had half our wifi phones drop offline the morning after the upgrade. Rolled back and figured I would wait for .2 before taking another look. Never investigated the issue but DHCP could have been one of the causes.
We've tried 26.1 through 26.4 and none are usable with Apple and Cisco mobiles in particular as they simply drop off the network far too often and don't reconnect. I'm guessing this is due to the known L3 roaming issue.
FYI, I received this message on a ticket of mine with Apple for wireless issues with iPads.
Hi Nathan,
Apologies for the lack of updates on this. The issue we identified in this case that can cause intermittent failures to connect to a PSK Wi-Fi network has been resolved in the iOS 13 beta.
If you have an opportunity to test, please let us know if you see improvements.
Yes, I also saw that but as the Cisco WiFi phones also drop at the same time (and don't reconnect until AP reboot) I think something bigger is at large.
We will try each new release as it comes due to needing the 26.x improvements but it is a bit of a chore...