Hi, Am Fr, den 14.05.2004 um 3:46 Uhr -0400 schrieb Alan DeKok: > Stephan Jaeger <[EMAIL PROTECTED]> wrote: > > and the proxy says: > > > > Fri May 14 09:23:53 2004 : Info: Ready to process requests. > > Fri May 14 09:24:05 2004 : Proxy: No outstanding request was found for > > proxy reply from home server 127.0.0.1:xxxx - ID 1 > > Fri May 14 09:24:05 2004 : Error: Assertion failed in request_list.c, > > line 533 > > Please run the server in debugging mode. As I said, the *idea* of > the code should solve the problem, but it hasn't been heavily tested. > > I can't reliably reproduce this problem in my setup, so it's > difficult for me to stress test the code. There isn't much more to see, at least not for me. Here is the output only for the second incoming request after that he bails out:
[...] Waking up in 3 seconds... rad_recv: Access-Request packet from host 127.0.0.1:34249, id=164, length=64 User-Name = "test" User-Password = "xxx" NAS-IP-Address = 255.255.255.255 NAS-Port = 0 Called-Station-Id = "00" Processing the authorize section of radiusd.conf modcall: entering group authorize for request 1 users: Matched DEFAULT at 3 modcall[authorize]: module "files" returns ok for request 1 rlm_realm: No '@' in User-Name = "test", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 1 modcall: group authorize returns ok for request 1 Sending Access-Request of id 2 to 127.0.0.1:xxxx User-Name = "test" User-Password = "xxx" NAS-IP-Address = 255.255.255.255 NAS-Port = 0 Called-Station-Id = "00" Proxy-State = 0x313634 Assertion failed in request_list.c, line 533 Aborted Let me know if you need the whole debug output. Regards Stephan Jaeger - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html