Indeed, but it's happening, and now, even with ADSL modem, as you can see in the radiusd -X output below: This occurs if user mistypes password or if the realm server is down: rad_recv: Access-Request packet from host 192.168.1.1 port 1385, id=21, length=60 User-Name = "user@realm.com" User-Password = "password" Processing the authorize section of radiusd.conf modcall: entering group authorize for request 20 rlm_realm: Looking up realm "realm.com" for User-Name = "user@realm.com" rlm_realm: Found realm "realm.com" rlm_realm: Proxying request from user user to realm realm.com rlm_realm: Adding Realm = "realm.com" rlm_realm: Preparing to proxy authentication request to realm "realm.com" rlm_eap: No EAP-Message, not doing EAP modcall: group authorize returns noop for request 20 Sending Access-Request of id 16 to 192.168.1.2 port 1645 User-Name = "user@realm.com" User-Password = "password" NAS-IP-Address = 192.168.1.1 Proxy-State = 0x3231 --- Walking the entire request list --- Waking up in 1 seconds... --- Walking the entire request list --- Waking up in 1 seconds... --- Walking the entire request list --- Waking up in 1 seconds... --- Walking the entire request list --- Waking up in 1 seconds... rad_recv: Access-Request packet from host 192.168.1.1 port 1385, id=21, length=60 Sending duplicate proxied request to home server 192.168.1.2 port 1645 - ID: 16 Assertion failed in listen.c, line 558 Aborted Thanks. "Guilherme Franco" <guilhermefranco at gmail.com> wrote:
I was worried about this, but when I tested with the user authenticating from an ADSL modem, there are no problems.
So, might be just another of ERX's crazy behaviors.
Still... it shouldn't kill the server. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog