I have a RB951Ui-2HnD, and Hostspot & user-manager is configured on it.
When I am trying to connect to Router with IP address, I cannot login by user manager users (I see “RADIUS server is not responding.” message), But local users of Hotspot works.
Please see the picture. Each time I am trying to connect, I see the message “RADIUS server is not responding.” and a number is added to the timeout field.
Looks OK.
Router cannot talk to itself ? (try tools Ping, Telnet, SSH, …)
I would just try replacing 127.0.0.1 with 192.168.88.1, and also check firewall rules.
Other way to debug is add Radius and Manager to the system → logging.
Just check your firewall for the rule that is blocking (drop) in the input chain.
For the default config it probably is the rule to drop input from every interface (or bridge) that is not in the LAN interface list.
So possibilities are
-) add explicit rule for UDP port 1812 that accepts input, and comes before that drop rule in the firewall
-) add interface or the bridge the interface is port of, to the “LAN” interface list
FW rules for input are limited by SRC IP address(-range), interface, interface list, UDP/TCP protocol, port number , or to any other filter you place in the rule.
The first rule that matches the filter is used.
In my case, at first i added LAN interface masquerade in Firewall/NAT without source network. For hotspot network , source network is add in NAT. Result is "Radius server is not responding.
I tried to add port 1812 in firewall but still not responding.
After adding source address in masquerade of LAN interface, radius server is working perfectly.
Not specifying this “secret” may give it some common value, I don’t know if it does, and what this value would be.
The RADIUS server/client connection and authorisation doesn’t care if this is on the same ROS device or not.
Don’t forget to check firewall filter, if following is needed.
add action=accept chain=input comment="defconf: accept to local loopback (for RADIUS)" dst-address=127.0.0.1
.
Enable system logging topics “radius,packet,debug” and “manager”, to see what happens.
I had this problem before. Beside bpwl’s answer that added the rules to firewall, I was added NAT masquerade to log the traffic but did not specify out-interface. After I set it then it is working fine.