Overview #
iOS devices (iPhone, iPad) optimize network connectivity by attempting to reuse previously assigned IP addresses when reconnecting to Wi-Fi networks. While this behavior improves connection speed and battery efficiency, it can interfere with the correct detection and display of Captive Portals, especially on guest networks without strict DHCP enforcement.
Cisco Wireless LAN Controllers (WLC) offer a setting called “DHCP Addr. Required” that can significantly improve the captive portal experience for iOS devices.
Problem Description #
Without “DHCP Addr. Required” enabled:
- iOS devices attempt to use a cached IP address from a previous connection.
- They may skip the DHCP process unless forced to revalidate.
- If the old IP address is invalid or mismatched with the current network, connectivity issues can occur.
- Captive Portal detection (via Captive Network Assistant) may fail or be delayed.
Result: Users experience difficulties accessing the network or do not see the Captive Portal login page promptly.
Solution: Enforce DHCP Address Assignment #
By enabling “DHCP Addr. Required” on the WLC SSID:
- The controller blocks client traffic until a full DHCP handshake is completed.
- Devices must request and obtain a new valid IP address before any network access is allowed.
- iOS devices are forced to perform a fresh DHCP discovery immediately upon connecting.
- This ensures correct network parameters (IP, Gateway, DNS) and triggers proper Captive Portal detection.
Result: iPhones and iPads reliably open the Captive Portal login window (Captive Network Assistant) as expected.
Conclusion #
Enabling “DHCP Addr. Required” on WLC guest SSIDs is crucial for ensuring a smooth and reliable captive portal experience, particularly for iOS devices. It prevents old IP address reuse issues, accelerates proper network access, and enhances overall user satisfaction on public or enterprise guest Wi-Fi networks.