• radius<id> - send the attribute identified with <id> in text string form to the RADIUS server
(in case RADIUS authentication is used; lost otherwise)
• radius<id>u - send the attribute identified with <id> in unsigned form to the RADIUS server
(in case RADIUS authentication is used; lost otherwise)
• radius<id>-<vnd-id> - send the attribute identified with <id> and vendor ID <vnd-id> in text
string form to the RADIUS server (in case RADIUS authentication is used; lost otherwise)
• radius<id>-<vnd-id>u - send the attribute identified with <id> and vendor ID <vnd-id> in
unsigned form to the RADIUS server (in case RADIUS authentication is used; lost otherwise)
• md5.js - JavaScript for MD5 password hashing. Used together with http-chap login method
• alogin.html - page shown after client has logged in. It pops-up status page and redirects
browser to originally requested page (before he/she was redirected to the HotSpot login page)
• status.html - status page, shows statistics for the client
• logout.html - logout page, shown after user is logged out. Shows final statistics about the
finished session. This page may take the folllowing additional parameters:
• erase-cookie - whether to erase cookies from the HotSpot server on logout (makes impossible
to log in with cookie next time from the same browser, might be useful in multiuser
environments)
• error.html - error page, shown on fatal errors only
• rlogin.html - page, which redirects client from some other URL to the login page, if
authorization of the client is required to access that URL
• rstatus.html - similarly to rlogin.html, only in case if the client is already logged in and the
original URL is not known
• flogin.html - shown instead of login.html, if some error has happened (invalid username or
password, for example)
• fstatus.html - shown instead of redirect, if status page is requested, but client is not logged in
• flogout.html - shown instead of redirect, if logout page is requested, but client is not logged in
Some other pages are available as well, if more control is needed:
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,
Page 520 of 695
Copyright 1999-2007, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.
Other trademarks and registred trademarks mentioned herein are properties of their respective owners.
To Next Page
Loading...
General