You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you connect to a wireless WiFi hotspot with a sign-in you have to go to your browser and must accept terms and conditions to gain access to the Internet.
But a WiFi-Box doesn't do this, and therefore can't fully connect to the network, and it can't reach the internet. Currently this makes the box inaccessible without a ethernet cable.
We'll need to research whether we can make the WiFi-box "sign-in" in these kind of networks.
Is this still something to look at? Seems to me this is a wont fix (as eg the chromecast is also unable to connect to such a network.)
If the 'accept' splashpage is known we could do a simple wget from the wifibox... otherwise we would need to forward the accept page to present to the user.
I agree we should not create a solution that will be able to login on such networks.
However the WiFi-Box will get into an unreachable state when this happens because it has successfully connected to a network although there's no way for it to reach the internet. We should implement that when it is not able to sign-in at connect.doodle3d.com it should fallback to accesspoint mode.
When you connect to a wireless WiFi hotspot with a sign-in you have to go to your browser and must accept terms and conditions to gain access to the Internet.
But a WiFi-Box doesn't do this, and therefore can't fully connect to the network, and it can't reach the internet. Currently this makes the box inaccessible without a ethernet cable.
We'll need to research whether we can make the WiFi-box "sign-in" in these kind of networks.
Original issue: Doodle3D/doodle3d-client#279
The text was updated successfully, but these errors were encountered: