Captive portal issues
Posted: Thu Aug 06, 2015 9:54 am
Hi Sprite_tm and others,
I've been using libesphttpd to good effect and had configured the captive portal which had been working really well until I realised how iOS devices behave. The problem I'm having is that the iPhone thinks that because it can't actually connect to the internet then it should disconnect from the AP (which is just plain annoying).
My suspicion is that they're just not going to play nicely, in which case I'd like to keep the DNS server functionality but only have it respond successfully to one address so that users don't need to type in IP addresses. I've been trying this by making it return an NXDOMAIN error for anything other than my domain but the iOS device still won't join the network.
Has anyone else made the captive portal work on iOS devices?
I'm going to keep trying to make it work, but any pointers or advice would be appreciated.
Cheers,
Ben
I've been using libesphttpd to good effect and had configured the captive portal which had been working really well until I realised how iOS devices behave. The problem I'm having is that the iPhone thinks that because it can't actually connect to the internet then it should disconnect from the AP (which is just plain annoying).
My suspicion is that they're just not going to play nicely, in which case I'd like to keep the DNS server functionality but only have it respond successfully to one address so that users don't need to type in IP addresses. I've been trying this by making it return an NXDOMAIN error for anything other than my domain but the iOS device still won't join the network.
Has anyone else made the captive portal work on iOS devices?
I'm going to keep trying to make it work, but any pointers or advice would be appreciated.
Cheers,
Ben