Community discussions

MikroTik App
 
usmany
Member Candidate
Member Candidate
Topic Author
Posts: 144
Joined: Sun Dec 20, 2009 3:20 pm
Location: Nigeria
Contact:

Mikrotik Login Page

Wed Oct 06, 2010 5:24 pm

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
 
fewi
Forum Guru
Forum Guru
Posts: 7717
Joined: Tue Aug 11, 2009 3:19 am

Re: Mikrotik Login Page

Wed Oct 06, 2010 5:26 pm

Run the Hotspot wizard and make a Hotspot?
 
usmany
Member Candidate
Member Candidate
Topic Author
Posts: 144
Joined: Sun Dec 20, 2009 3:20 pm
Location: Nigeria
Contact:

Re: Mikrotik Login Page

Wed Oct 06, 2010 5:30 pm

Run the Hotspot wizard and make a Hotspot?
I done that, but i still can not get the login page appear when customer open up browser to surf.
 
fewi
Forum Guru
Forum Guru
Posts: 7717
Joined: Tue Aug 11, 2009 3:19 am

Re: Mikrotik Login Page

Wed Oct 06, 2010 5:44 pm

Post a network diagram of your topology including all relevant devices, their interfaces, links, and IP addresses.
Also post the output of "/ip route print", "/ip address print", "/ip hotspot export" and "/ip firewall export".
 
jober
Long time Member
Long time Member
Posts: 690
Joined: Fri May 28, 2004 12:16 pm
Location: Louisiana,USA

Re: Mikrotik Login Page

Wed Oct 06, 2010 10:55 pm

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.
 
usmany
Member Candidate
Member Candidate
Topic Author
Posts: 144
Joined: Sun Dec 20, 2009 3:20 pm
Location: Nigeria
Contact:

Re: Mikrotik Login Page

Thu Oct 07, 2010 3:00 pm

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.
I dont get your point?

I have rb750g, i set all necessary setting hopefully right! but i can not get login page to browser. I can only get the login in page when you type in the rb750g ip address or http://hotspot.com

Here is the html login page if there is something i need to correct:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>internet hotspot > Computer Centre-Futy login</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta http-eqiuv="refresh" content="0; url=http://http://hotspot.com/login">
<meta http-equiv="pragma" content="no-cache" />
<meta http-equiv="expires" content="-1" />
<style type="text/css">
body {color: #737373; font-size: 10px; font-family: verdana;}

textarea,input,select {
background-color: #FDFBFB;
border: 1px solid #BBBBBB;
padding: 2px;
margin: 1px;
font-size: 14px;
color: #808080;
 
fewi
Forum Guru
Forum Guru
Posts: 7717
Joined: Tue Aug 11, 2009 3:19 am

Re: Mikrotik Login Page

Thu Oct 07, 2010 4:00 pm

If that is your login.html then it makes no sense, whatsoever

It attempts to redirect back to the Hotspot servlet that just loaded it, but with the protocol twice in the URL, which would confuse any browser:
<meta http-eqiuv="refresh" content="0; url=http://http://hotspot.com/login">
What is the purpose of a that HTML and what are you trying to achieve? What you are doing cannot possibly ever work for any purpose.
 
reverged
Member Candidate
Member Candidate
Posts: 270
Joined: Thu Nov 12, 2009 8:30 am

Re: Mikrotik Login Page

Fri Oct 08, 2010 10:18 am

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:
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 
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.
 
usmany
Member Candidate
Member Candidate
Topic Author
Posts: 144
Joined: Sun Dec 20, 2009 3:20 pm
Location: Nigeria
Contact:

Re: Mikrotik Login Page

Fri Oct 08, 2010 10:31 am

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:
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 
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.
Thank you so much, I will try it.

Who is online

Users browsing this forum: No registered users and 18 guests