I have just had DMAsoftlab.com finish setup of Radius Manager, now I need mikrotik to authenticate clients, but don’t know how to tell mikrotik to use radius manager as authintication device.
I presume that under radius I add a radius server
ppp type
with ip address pointing to the radius manager pc’s ip address
and a shared secret that matches with radius manager.
If I am correct, then why does radius manager not authenticate?
NAS has been setup on the radius manager box. and my setup above matches that of the radius box, is there anywhere else eg under ppp shared secret etc etc…that needs to be changed from using usermanager to radius manager?
Hi Support contacted me with a solution, but NASes created using Radius Manager do not work, only the original testing123 NAS is working.
I would like to use this for both Hotspot Authentication as well as PPPOE, but currently my aim is to get PPPOE working as this is what 99% of our clients use to connect.
We only use hotspot for our clients that connect for short periods.
Did you set up the new hotspot as a radius client? If not, that is probably the challenge. FreeRADIUS uses the file clients.conf to verify radius client authorization. I use radtest to insure the RADIUS server is sending the correct parameters to my clients. From a shell on the RADIUS server:
radtest user password 127.0.0.1 0 radiussecret
Change user, password, hotspot IP ( I use 127.0.0.1 first to check the user/password), and radiussecret to valid values for your system.
radtest works, (also not using hotspot at this stage)
I can actually log in when using testing123 sharedsecret, but any NAS created in radiusmanager does not work, only the default testing123 one.
It takes a while after setting up the shared secret in radiusmanager for users to be able to authenticate, but after those few minutes pass logins are accepted no problem again only with the default testing123 NAS.
I am curruntly communicating with Support at DMAsoftlabs, but email back and forth takes time.