https://datatracker.ietf.org/doc/html/rfc2131 " If the client receives a DHCPNAK message, it cannot reuse its remembered network address. It must instead request a new address by restarting the configuration process " This is not what iOS is doing, it keeps on asking for the previous obtained ip address event after receiving multiple DHCPNAK from the dhcp server.

Hello, Thank you for your suggestion, but i thought i could find here a developper that could explain the behaviour based on the actual production code, the Support Community won't be of any help. Regards

Hello, Happy to see that i am not the only one to have noticed the behavior. On our side, here is the context : 2 universities offering same ssid "eduroam" next to each other So a student from University A associate successfully to the ssid eduroam, and if he walks towards University B he will authenticate successfully using the ssid eduroam of University B, but after successfull authentication logs show that the device failed to get a new ip address as it asks continuouly (till the end of the dhcp lease ?) its previous obtained ip address to the dhcp server behind the ssid eduroam of University B, the client can be stuck for a very long time (minutes, hours), at some point the client decide to make a dhcp discover and get a valid ip address. All clients seen are iPhone/iPad. It is devastating for all our Apple clients. Regards