Setup guide
• your uptime limit is reached - self-explanatory
• your traffic limit is reached - either limit-bytes-in or limit-bytes-out limit is reached
• no more sessions are allowed for user - the shared-users limit for the user's profile is reached.
Solution: wait until someone with this username logs out, use different login name or extend the
shared-users limit
RADIUS client non-fatal errors:
• invalid username or password - RADIUS server has rejected the username and password sent
to it without specifying a reason. Cause: either wrong username and/or password, or other error.
Solution: should be clarified in RADIUS server's log files
• <error_message_sent_by_radius_server> - this may be any message (any text string) sent
back by RADIUS server. Consult with your RADIUS server's documentation for further
information
RADIUS client fatal errors:
• RADIUS server is not responding - self-explanatory. Solution: check whether the RADIUS
server is running and is reachable from the HotSpot router
• invalid response from RADIUS server - the RADIUS server has sent incorrect response
(neither accept nor reject). Solution: make sure the RADIUS server sends only accept or reject
responses to authentication requests
HotSpot Step-by-Step User Guide for dhcp-pool Method
Description
Let us consider following example HotSpot setup:
There will be 2 HotSpot IP address ranges used for clients on prism1 interface. You are free to
choose the address ranges, just make sure you use masquerading for not routed ones. In this
example, we are using:
• temporary addresses which must be masqueraded:
• network: 192.168.0.0/24
• gateway: 192.168.0.1
• pool: 192.168.0.2-192.168.0.254
• real addresses which require routing:
• network: 10.5.50.0/24
• gateway: 10.5.50.1
• pool: 10.5.50.2-10.5.50.254
For HotSpot client accounting, HotSpot will add dynamic firewall rules in firewall HotSpot chain.
This chain has to be created manually. And all network packets (to/from HotSpot clients) have to
pass this chain.
Example
1. The ether1 interface is configured with IP address 10.5.6.5/24 and the default route pointing to
the 10.5.6.1 gateway.
2. The prism1 interface is configured for AP mode and is able register IEEE 802.11b wireless
clients. See the Prism Interface Manual for more details.
3. ARP should be set to reply-only mode on the prism1 interface, so no dynamic entries are