Jeremy Kusnetz <[EMAIL PROTECTED]> wrote: > I'm using SQL and simultanious logins. It's happening when I get a request > from a bogus IP address. I'm not sure why I'm getting requests from these > IP address, maybe it's an attack???
It's a problem, whatever it is. > Reguardless freeradius shouldn't crash from this. I agree. > It looks like it might be related to checkrad. > > These are the errors I get in the logs before it crashes: > > Tue Mar 19 19:47:02 2002 : Error: Check-TS: timeout waiting for checkrad > Tue Mar 19 19:47:02 2002 : Error: Trying to look up name of unknown client > 40.69.22.64. > Tue Mar 19 19:47:02 2002 : Error: Accounting-Request packet sent to a > non-accounting port from client UNKNOWN-CLIENT:0 - > ID 10 : IGNORED That's one weird client. > Tue Mar 19 19:47:02 2002 : Error: CHILD: exit on signal (11) Hmm... that message isn't (or shouldn't be) related to the previous 'unknown client'. The main server thread sends the 'unknown client:ignored' message, and drops the bad packet on the floor. Either way, it shouldn't crash. If you can use gdb or get a core dump, then it should be possible to track down *where* it core dumps, then that will help a lot in figuring out why. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
