Recently I installed multiple MT493AH units at multiple locations. All locations are just about the same configuration, 100-200 foot tower with 493 at bottom of tower and Ubiquiti APs at the top of the tower with directional antennas.
The 493s are all configured as hotspots with Radius authentication. I do not have idle timeout, session timeout or keepalive enable for the default user on the hotspot. The server has idle timeout, and keepalive enabled on the default server. Radius attributes that are configured in Radius are WISPr bandwidth up/down.
I have also reconfigured the login page so those that are not authenticated will receive a notice of our services and their MAC address and IP address.
We have multiple clients on each tower that will ocassionally received the login page. Sometimes this happens when they first connect, sometimes it happens during a session. Typically when we look at the Host tab in WinBox they have a D beside their MAC meaning they are not authenticated. Normally we can clear their entry and they start working but sometime the only thing that will get them working is to have them shut down all their equipment and/or repair their network connection. This is happening with different brands of CPEs on the customer end.
I have spent the last 3 weeks working on this, searching the forums, changing settings and still no solution.
Anyone with an insight to the solution to the problem please let me know what to do next. I am almost to the point that I am going to have to turn off the Hotspot and just allow everyone in the system which I don’t want to do.
The below example has 4 ubiquiti PS2-EXT APs mounted at 190 feet with the 493 in the comm building at the bottom of the tower. Each AP is connected to individual ports on tthe 493, ports 2, 3, 4, 5. Those 4 ports are then placed in a bridge called HS-Bridge. The hotspot is assigned to the HS-Bridge.
If the below is not enought let me know what you need.. I am new to MT’s but not new to IPs
I don’t see that in the docs. If you use the “/ip hotspot setup” and don’t change it, it will use the ip of the interface you selected. All mine have the ip of the interface there, and all work normally.
ADD: Just to be sure, you are seeing the mac addresses of the clients and not the APs in the host list, correct?
Page 12 of the Hotspot.pdf under Notes states: “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.”
I am trying to find differences between your system and mine, since mine is working and your isn’t. I will presume that works, but I haven’t seen it. All setups I have done set that value.
Did you check your “/ip hotspot host” to insure the mac addresses there are in fact your clients and not the mac addresses of the APs?
That is odd. Is there anything in the log that indicates why they are being logged out? Obviously that is what is happening, don’t you think? I would look at the RADIUS server log too. Radacct table actually. It should have a reason why each client session was terminated.
