Hi, I am attempting to use the new captive network DHCP advertisement in option 114 as described here: https://developer.apple.com/news/?id=q78sq5rv
I configured my network's dhcp server (dnsmasq) like the following:
(wifi.mysite.com does resolve and have a valid https cert within my network, and the API response is valid per the spec)
When I associated an iOS 14 device (iPhone) to the network, it successfully was assigned a DHCP address and included the new option 114. However, it seems that it does not attempt to query the captive portal API specified in option 114 (no dns or https request for is seen wifi.mysite.com in a packet capture at my AP). Instead, the iPhone does an HTTP GET of http://captive.apple.com/hotspot-detect.html. Seems like it is behaving just like an iOS 13 or below device with respect to captive networks, even though the new dhcp option is present.
Some additional info: my network is ipv4 only, and I've already tried forgetting the SSID on the iPhone, DHCP release/renew, rebooting the iPhone.
I configured my network's dhcp server (dnsmasq) like the following:
Code Block dhcp-option-force=114,https://wifi.mysite.com/v1/captive
(wifi.mysite.com does resolve and have a valid https cert within my network, and the API response is valid per the spec)
When I associated an iOS 14 device (iPhone) to the network, it successfully was assigned a DHCP address and included the new option 114. However, it seems that it does not attempt to query the captive portal API specified in option 114 (no dns or https request for is seen wifi.mysite.com in a packet capture at my AP). Instead, the iPhone does an HTTP GET of http://captive.apple.com/hotspot-detect.html. Seems like it is behaving just like an iOS 13 or below device with respect to captive networks, even though the new dhcp option is present.
Some additional info: my network is ipv4 only, and I've already tried forgetting the SSID on the iPhone, DHCP release/renew, rebooting the iPhone.
I'm also experiencing the same issue described in previous POSTs. Is Apple ever going to fix this (or is even aware)?
This feature is very important to get rid of HSTS redirection among other details that in legacy captive portal aren't optimal.
I find it strange releasing this feature this way as it defeats the purpose if on first join the portal ain't triggered.
This feature is very important to get rid of HSTS redirection among other details that in legacy captive portal aren't optimal.
I find it strange releasing this feature this way as it defeats the purpose if on first join the portal ain't triggered.
