Guys,
How can i make the login page appear when a customer try to surf the net? I want all connections to the network to display the mikrotik login page on customers system.
Thank You
I done that, but i still can not get the login page appear when customer open up browser to surf.Run the Hotspot wizard and make a Hotspot?
I dont get your point?same problem here
I get the same old default hotspot login screen and I can figure out how to get the um user login page to come up.
internet router is rb600-----switch-----ether1/rb750g/UM ether5-----ether1rb600 with hotspot on wlan1
inet router is 4.11
UM is 5.0rc1 using user-manager-5.0rc1-mipsbe.npk
hotspot is 4.11
It would be nice to have some clear documentation on v5 and v4. It's hard to figure out what you need to do when you get pointed to v3 docs that don't apply to v4 or v5. There should be 3 different areas for v3, v4 and v5.
<meta http-eqiuv="refresh" content="0; url=http://http://hotspot.com/login">
Serving Servlet Pages
The HotSpot servlet recognizes 5 different request types:
1. request for a remote host
* if user is logged in, the requested page is served
* if user is not logged in, but the destination host is allowed by walled garden, then the request is also served
* if user is not logged in, and the destination host is disallowed by walled garden, rlogin.html is displayed; if rlogin.html is not found, redirect.html is used to redirect to the login page
2. request for "/" on the HotSpot host
* if user is logged in, rstatus.html is displayed; if rstatus.html is not found, redirect.html is used to redirect to the status page
* if user is not logged in, rlogin.html is displayed; if rlogin.html is not found, redirect.html is used to redirect to the login page
3. request for "/login" page
* if user has successfully logged in (or is already logged in), alogin.html is displayed; if alogin.html is not found, redirect.html is used to redirect to the originally requested page or the status page (in case, original destination page was not given)
* if user is not logged in (username was not supplied, no error message appeared), login.html is showed
* if login procedure has failed (error message is supplied), flogin.html is displayed; if flogin.html is not found, login.html is used
* in case of fatal errors, error.html is showed
4. request for "/status" page
* if user is logged in, status.html is displayed
* if user is not logged in, fstatus.html is displayed; if fstatus.html is not found, redirect.html is used to redirect to the login page
5. request for '/logout' page
* if user is logged in, logout.html is displayed
* if user is not logged in, flogout.html is displayed; if flogout.html is not found, redirect.html is used to redirect to the login page
Thank you so much, I will try it.I found this page to be very helpful in setting up such a hotspot:
http://www.mikrotik.com/testdocs/ros/2.9/ip/hotspot.php
It says v2.9 but the concepts are the same and this section is very important:
So, you need rlogin.html or redirect.html page to redirect to the actual login page. I use a refresh in the html header to redirect to an external page, but it can redirect to any page assuming it is in the walled garden.Code: Select allServing Servlet Pages The HotSpot servlet recognizes 5 different request types: 1. request for a remote host * if user is logged in, the requested page is served * if user is not logged in, but the destination host is allowed by walled garden, then the request is also served * if user is not logged in, and the destination host is disallowed by walled garden, rlogin.html is displayed; if rlogin.html is not found, redirect.html is used to redirect to the login page 2. request for "/" on the HotSpot host * if user is logged in, rstatus.html is displayed; if rstatus.html is not found, redirect.html is used to redirect to the status page * if user is not logged in, rlogin.html is displayed; if rlogin.html is not found, redirect.html is used to redirect to the login page 3. request for "/login" page * if user has successfully logged in (or is already logged in), alogin.html is displayed; if alogin.html is not found, redirect.html is used to redirect to the originally requested page or the status page (in case, original destination page was not given) * if user is not logged in (username was not supplied, no error message appeared), login.html is showed * if login procedure has failed (error message is supplied), flogin.html is displayed; if flogin.html is not found, login.html is used * in case of fatal errors, error.html is showed 4. request for "/status" page * if user is logged in, status.html is displayed * if user is not logged in, fstatus.html is displayed; if fstatus.html is not found, redirect.html is used to redirect to the login page 5. request for '/logout' page * if user is logged in, logout.html is displayed * if user is not logged in, flogout.html is displayed; if flogout.html is not found, redirect.html is used to redirect to the login page