Are there any plans to support the user manager as a RADIUS peer, authenticating against a remote RADIUS server, but auth and acct on a local basis?
We’re running a RADIUS server (with database backend) already, but would love to set up our hot spots to allow logins against that server instead of an internal list of users.
It would allow local control of logged-in users, but could keep the database off all users offsite.
Why don’t you only use RADIUS then? What is it you are trying to acomplish?
I would choose only the one or the other, IMHO
As a RADIUS peer, the User Manager would be able to manage the sessions directly, on only one box. Right now, I’ve got two user entries for hotspot users - one on the MT box, and one on our RADIUS server.
Even when they’re synced (which is not always - lots of concurrent login issues), it’s difficult to manage where a user is logged in, and how to manage them.
If the User Manager could simply peer off of the RADIUS server for authentication (and to be the single place for session management), we’d be set. Check out Craig Sickles post in this forum.
I see what you mean. It makes sense to me. Perhaps Mikrotik should considder making it possible to have the database on a remote server. That way you should be able to tap into it using RADIUS and UM.
Just my thoughts…
This is EXACTLY waht I have been asking for…
(Or trying to figure out)
The only thing, I was hoping that both Peers could be UserManager…
Or the ability to create a list of radius servers.. IE:
local (usermanager) = server1 (or 1st server in the radius list)
remote1 = 2nd on list = remote radius IE UserManager or Free Radius..
remote2 …
This would ROCK.