I am experiencing problems with userman on ROS V3.10.
I can setup userman and it will work if only one interface has an IP address, as soon as a second interface is assigned an IP address it no longer sees the router in userman.
Log error is user xxxxxxxxx authentication failed radius time out.
ping the radius ip that is setup with 100% replies
If I remove the ip on the second interface all works again.
This was never the case on 2.9.x versions, and this is the first time I have experienced this.
The routerboard is 433 with 3 wlan and 3ethernet.
Plain and simple ppp server with userman as radius.
If you would like output from router to see the setup I can upload it if you like.
Using an external radius like radius manager with ip addresses on multiple interfaces works, but I only have a demo licence for radius manager, and don't see the need to spend $99 if I can get userman to work.
Any thoughts would be greatly appreciated.
Thanks in advance
Scratch the above-->Managed a workaround
This is what I did
Setup radius manager as in wiki, then added another router under /tools/user-manager/router and under /radius
Don't know why that solved the issue, but thought if it can't see radius on that interface, let me try add it as a server on the second interface ip, and it worked, the others that followed did not require the additional radius setup, so for all my 6 interfaces there is only two that are setup and it is now working on all the interfaces now.
But hey it's working so can't complain. I would suggest that Mikrotik look into this, it's kinda annoying when somthing that used to work flawlessly now has problems