Need Help with setting up mikrotik and radius manager!

Hi All,

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?

Any help on this would be greatly appreciated.

Which service you want to bind with Radius server..???

I mean, HOTSPOT, PPPoE.

/ip hotspot profile use-radius=yes
/radius service=hotspot address= secret=123456

in your radius you have to add the Router IP, where the HOTSPOT is configured.

I dropped a line to their support line.
I referanced this thread to see if they will contact you ore post here to help.

If I hear from them, I will see if they will let me play with a copy to help out..

I will post if I hear from them…

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.

Greetings!

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.

WIth RadiusManager, you have to change your radius secret code in three places:

  • clients.conf, for the NAS in question (possibly 0.0.0.0/0);
  • under NAS config in the ACP (Administrator Control Panel); and
  • on the MT

Finally, you must stop & restart radiusd for the changes to take effect.

–Dan <><

Thanks for the reply, but I was instructed by DMAsoftlabs not to change the clients.conf file.

They said there is only two places that need to be changed:

ACP on radiusmanager NAS and MT itself.

I asked if I should add the shared secret into the clients.conf file, and they said it is not necessary. I will however try what you sugested!