Hi Simon,
Thank you for your quick answer. I'm sorry to be a little bit out of topic. Do you know what I should do with these requests? Should I declare such virtual users into freeradius users file? What kind of data do I have to provide? I do understand that it should happen once at MAX boot time, but why does it happen all the time? Sometimes it stops and I can establish a route to an other network, but during such requests, I cannot establish a route. The MAX "doen't see" packets for the wan network. Should I do a dump of configuration and then a "reset to factory" and finally restore the config? Thank you Christophe Marbacher ----- Previous message Simon: "My understand of this is its the max trying to get its config from Radius. Its quite normal, but you should only see it once the NAS has booted or you do a config reload." > > Hello, > > I get strange things from my MAX1800. Using freeradius daemon with > > radiusd -f -s -x -y > > I get the following messages: > > ---------------------------------------------------------------------------- > ----------------------------------------- > Sending Access-Reject of id 52 to 10.0.250.250:1025 > rad_recv: Access-Request packet from host 10.0.250.250:1025, id=53, > length=84 > User-Name = "permconn-cheseaux-1" > Password = "\306=\243\275Q\372\245\367QT\3153\302\377\252\244" > NAS-IP-Address = 10.0.250.250 > NAS-Port = 0 > NAS-Port-Type = Virtual > Service-Type = Outbound-User > Sending Access-Reject of id 53 to 10.0.250.250:1025 > rad_recv: Access-Request packet from host 10.0.250.250:1025, id=54, > length=81 > User-Name = "dovbs-cheseaux-1" > Password = "#-\033n\275\362\254\376\216\021\275\232of+$" > NAS-IP-Address = 10.0.250.250 > NAS-Port = 0 > NAS-Port-Type = Virtual > Service-Type = Outbound-User > Sending Access-Reject of id 54 to 10.0.250.250:1025 ---- CUT ------
Marbacher Christophe.vcf
Description: Binary data
