AT-WR4500 Series - IEEE 802.11abgh Outdoor Wireless Routers
137
RouterOS v3 Configuration and User Guide
instances may be send by RADIUS server to specify additional URLs which are choosen in round
robin fashion.
•
Mikrotik-Advertise-Interval
- Time interval between two adjacent advertisements. Multiple
attribute instances may be send by RADIUS server to specify additional intervals. All interval values
are threated as a list and are taken one-by-one for each successful advertisement. If end of list is
reached, the last value is continued to be used.
•
WISPr-Redirection-URL
- URL, which the clients will be redirected to after successfull login
•
WISPr-Bandwidth-Min-Up
- minimal datarate (CIR) provided for the client upload
•
WISPr-Bandwidth-Min-Down
- minimal datarate (CIR) provided for the client download
•
WISPr-Bandwidth-Max-Up
- maxmal datarate (MIR) provided for the client upload
•
WISPr-Bandwidth-Max-Down
- maxmal datarate (MIR) provided for the client download
•
WISPr-Session-Terminate-Time
- time, when the user should be disconnected; in "YYYY-MM-
DDThh:mm:ssTZD" form, where Y - year; M - month; D - day; T - separator symbol (must be
written between date and time); h - hour (in 24 hour format); m - minute; s - second; TZD - time
zone in one of these forms: "+hh:mm", "+hhmm", "-hh:mm", "-hhmm"
The received attributes override the default ones (set in the default profile), but if an attribute is not
received from RADIUS server, the default one is to be used.
Rate-Limit takes precedence over all other ways to specify data rate for the client. Ascend data rate
attributes are considered second; and WISPr attributes takes the last precedence.
Here are some Rate-Limit examples:
•
128k
- rx-rate=128000, tx-rate=128000 (no bursts)
•
64k/128M
- rx-rate=64000, tx-rate=128000000
•
64k 256k
- rx/tx-rate=64000, rx/tx-burst-rate=256000, rx/tx-burst-threshold=64000, rx/tx-burst-
time=1s
•
64k/64k 256k/256k 128k/128k 10/10
- rx/tx-rate=64000, rx/tx-burst-rate=256000, rx/tx-burst-
threshold=128000, rx/tx-burst-time=10s
Accounting-Request
The accounting request carries the same attributes as Access Request, plus these ones:
•
Acct-Status-Type
- Start, Stop, or Interim-Update
•
Acct-Authentic
- either authenticated by the RADIUS or Local authority (PPPs only)
•
Class
- RADIUS server cookie, as received in Access-Accept
•
Acct-Delay-Time
- how long does the router try to send this Accounting-Request packet
Stop and Interim-Update Accounting-Request
Additionally to the accounting start request, the following messages will contain the following attributes:
•
Acct-Session-Time
- connection uptime in seconds
•
Acct-Input-Octets
- bytes received from the client
•
Acct-Input-Gigawords
- 4G (2^32) bytes received from the client (bits 32..63, when bits 0..31 are
delivered in
Acct-Input-Octets
)
•
Acct-Input-Packets
- nubmer of packets received from the client
•
Acct-Output-Octets
- bytes sent to the client
•
Acct-Output-Gigawords
- 4G (2^32) bytes sent to the client (bits 32..63, when bits 0..31 are
delivered in
Acct-Output-Octets
)
•
Acct-Output-Packets
- number of packets sent to the client
Stop Accounting-Request
These packets will, additionally to the Interim Update packets, have:
•
Acct-Terminate-Cause
- session termination cause (see RFC2866 ch. 5.10)