Hello everyone,
We have some hotspots up and running, but we have some problems:
After a user login (with some mobile phones) the redirection to an https page or on Facebook doesn't show up. (on some devices work properly)
The hotspot files are local installed at mikrotik routerboard and the redirection link is inside the file login.html
Any ideas - help?
Thanks in advance.
Re: Hotspot redirection after login
Most modern devices (more commonly mobile devices than laptops) will simply close the hotspot page after initial login is completed.
Unless you can allow the user to get to the Facebook page first (which requires a big list of walled garden entries); then complete the login process after that it will be very difficult to find a way to push users to this page; that also works with all systems.
Unless you can allow the user to get to the Facebook page first (which requires a big list of walled garden entries); then complete the login process after that it will be very difficult to find a way to push users to this page; that also works with all systems.
Re: Hotspot redirection after login
Hi!
I would say, that bummer. Even making sure hotspot listens on both http and https ports would not help you much.
We've abandoned attempts to solve that issue because of the idea behind https.
To present you with a login page, hotspot redirects traffic to its own webserver. Whenever that happens with HTTPS you would get a notification about certificate mismatch which is the way it is supposed to be - client expects to get certificate from www.google.com but gets cert from hotspot.somecompany.com. The only way to resolve that is wildcard * certificate, which would be self-signed and give you, same certificate mismatch error.
I would say, that bummer. Even making sure hotspot listens on both http and https ports would not help you much.
We've abandoned attempts to solve that issue because of the idea behind https.
To present you with a login page, hotspot redirects traffic to its own webserver. Whenever that happens with HTTPS you would get a notification about certificate mismatch which is the way it is supposed to be - client expects to get certificate from www.google.com but gets cert from hotspot.somecompany.com. The only way to resolve that is wildcard * certificate, which would be self-signed and give you, same certificate mismatch error.