[1.1.0.39] Problems with WiFi captive portal [answered]
asked 2014-10-30 11:38:48 +0300
I can no longer connect to the London Underground WiFi network.
In 1.0 firmwares the process would be:
- (Auto)connect to the access point (wifi indicator on home screen shows a star or an exclamation mark)
- Open browser and go to an http page
- Captive portal DNS-redirects to a login page, or hopefully remembers your MAC address and lets you straight in (via an ad)
- Jolla somehow notices between 0 and 10 seconds later that it's been granted full internet access and shows "(wifi) Connected" banner and normal indicator on homescreen
- Browse away
Now in 1.1 firmwares, in the third step, the browser will not be able/allowed to look up the DNS for a host and thus get redirected to the captive portal login page.
Browser shows its "cannot look up host" error page. Using Android Firefox still doesn't work, as Firefox says it's offline. Even performing a ping from the terminal won't look up an address.
Another question on here (and recent activity under the wifi tag) suggests that the browser is/was whitelisted to be able to work in half-connected mode, but this no longer seems to be the case.
It seems that the system is reporting that it's not connected (and won't forward DNS queries), so all apps will either not bother doing any networking, or try and fail, thus there is no way to satisfy the captive portal to continue to full internet access (which the Jolla would then presumably be happier with).
To follow up, I used another captive portal yesterday, and it worked as per 1.0 firmwares - I could use the browser to login. But the Underground Wifi still doesn't work. Sailors or others - anything I can run/check to see why it's got in a state where it won't look up any hosts?
vitaminj ( 2014-11-07 00:26:46 +0300 )edit