Allied Telesis AT-WR4500 - Manual (Page 239)

AT-WR4500 Series - IEEE 802.11abgh Outdoor Wireless Routers 239
RouterOS v3 Configuration and User Guide
radiusu - show the attribute identified with in unsigned integer form (in case RADIUS
authentication was used; "0" otherwise)
radius- - show the attribute identified with and vendor ID in text
string form (in case RADIUS authentication was used; "" otherwise)
radius-u - show the attribute identified with and vendor ID in
unsigned integer form (in case RADIUS authentication was used; "0" otherwise)
Working with variables
$(if ) statements can be used in theses pages. Following content will be included, if
value of will not be an empty string. It is an equivalent to $(if != "") It
is possible to compare on equivalence as well: $(if == ) These
statements have effect until $(elif ), $(else) or $(endif). In general case it looks
like this:
some content, which will always be displayed
$(if username == john)
Hey, your username is john
$(elif username == dizzy)
Hello, Dizzy! How are you? Your administrator.
$(elif ip == 10.1.2.3)
You are sitting at that crappy computer, which is damn slow...
$(elif mac == 00:01:02:03:04:05)
This is an ethernet card, which was stolen few months ago...
$(else)
I don't know who you are, so lets live in peace.
$(endif)
other content, which will always be displayed
Only one of those expressions will be shown. Which one - depends on values of those variables for each
client.
Customizing Error Messages
All error messages are stored in the errors.txt file within the respective HotSpot servlet directory. You
can change and translate all these messages to your native language. To do so, edit the errors.txt file.
You can also use variables in the messages. All instructions are given in that file.
Multiple Versions of HotSpot Pages
Multiple hotspot page sets for the same hotspot server are supported. They can be chosen by user (to
select language) or automatically by JavaScript (to select PDA/regular version of HTML pages).
To utilize this feature, create subdirectories in HotSpot HTML directory, and place those HTML files,
which are different, in that subdirectory. For example, to translate everything in Latvian, subdirectory "lv"
can be created with login.html, logout.html, status.html, alogin.html, radvert.html and errors.txt files,
which are translated into Latvian. If the requested HTML page can not be found in the requested
subdirectory, the corresponding HTML file from the main directory will be used. Then main login.html file
would contain link to "/lv/login?dst=$(link-orig-esc)", which then displays Latvian version of login page: href="/lv/login?dst=$(link-orig-esc)">Latviski
. And Latvian version would
contain link to English version: English
Another way of referencing directories is to specify 'target' variable:
Latviski
English
After preferred directory has been selected (for example, "lv"), all links to local HotSpot pages will
contain that path (for example, $(link-status) = "http://hotspot.mt.lv/lv/status").
So, if all hotspot pages reference links using "$(link-xxx)" variables, then no more changes are to be made
- each client will stay within the selected directory all the time.