雷竞技网站

嗨

I upgraded my main mikrotik v2.9.50 to v3.2. It runs userman with about 800 pppoe clients.

I also had a pppoe server on the same machine that is running userman by using the router address as 127.0.0.1 and the radius setting in Mikrotik to 127.0.0.1. I also run a hotspot of this Mikrotik.

This worked fine on 2.9.50 but not on 3.2. It just don't want to authenticate the local pppoe servers' users. The hotspot does the same. Is this a bug in v3.2? I also tried other interfaces' ip but no luck. Can it be fixed and is there a temperory workaround? I am allowing the users to authenticate from the local secrets but I loose all the logs an usage tracking.

Thanks for any help.

Hi,

I'm also having some dificulties to upgrade the user database from 2.9.49 to 3.2. The customer password is not recovered properly and on the user database the time left column appears as something like "1965w:4d:6h:57m:17s" when it is 0s on the previous version.

Are there any intermediate steps between 2.9.49 and 3.2 for the usermanager?

Thanks to Segejs my problem is solved.

I had a masquerade rule that didn't have a specific out interface which prevented userman to connect to the local host.