Setup guide

enabled
http-cookie-lifetime (time; default: 1d) - validity time of HTTP cookies
allow-unencrypted-passwords (yes | no; default: no) - whether to authenticate user if plain-text
password is received
login-mac-universal (yes | no; default: no) - whether to log in every host of Universal client
instantly in case it has its MAC address listed in HotSpot user list
split-user-domain (yes | no; default: no) - whether to split username from domain name when the
username is given in "user@domain" or in "domain\user" format
Command Description
reset-html - overwrite the existing HotSpot servlet with the original HTML files. It is used if you
have changed the servlet and it is not working after that.
Notes
If dns-name property is not specified, hotspot-address is used instead. If hotspot-address is also
absent, then both are to be detected automatically.
If auth-mac is enabled, then a client is not prompted for username and password if the MAC
address of this computer is in the HotSpot user database (either local or on RADIUS). Nevertheless
this method does not excuse clients from the common login procedure, just from filling out the
registration form (i.e. regardless of whether MAC authorization is applicable for a client, he/she
should open the Login in order to get registered). The only exception is the users of Universal
Client - if login-mac-universal property is enabled, they will not even have to open a web browser
if their MAC addresses are listed in the user database.
The universal-proxy feature automatically creates DST-NAT rules to redirect requests of each
particular user to a proxy server he/she is using (it may be set in his/her settings to use an unknown
to us proxy server) to the local embedded proxy server. This feature may be used in combination
with Universal Client feature to provide Internet access for users regardless of their network
settings.
allow-unencrypted-passwords property makes it possible to authenticate with the browsers not
supporting JavaScript (for example, Internet Explorer 2.0). It is also possible to log in using telnet
connection, just requesting the
/login?user=username&password=password
. An another use of
this property is the possibility of hard-coded authentication information in the servlet's login page
simply creating the appropriate link.
auth-requires-mac property makes it possible to make a 'reverse HotSpot' - to authenticate users
accessing the local network from the Internet.
Example
To enable cookie support:
[admin@Wandy] ip hotspot> set auth-http-cookie=yes
[admin@Wandy] ip hotspot> print
use-ssl: no
hotspot-address: 0.0.0.0
dns-name: ""
status-autorefresh: 1m
universal-proxy: no
parent-proxy: 0.0.0.0:0
auth-requires-mac: yes
auth-mac: no