Jeremy Kusnetz wrote:
> Freeradius is crashing on me.  I've resorted to running it with radwatch.
> 
> We've just gone operational with freeradius when 0.5 came out.  I've been
> running 0.4 or some CSV snapshot since then in development, but weren't
> getting nearly the number of requests that we are getting now, so I don't
> know if this was a problem in 0.4 or if it was introduced in 0.5
> 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???  Reguardless freeradius shouldn't crash
> from this.



> 
> 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
> Tue Mar 19 19:47:02 2002 : Error: CHILD: exit on signal (11)

Did you just copy over radiusd or did you do a make install?
I got sig 11's because I just copied the new radiusd over the 0.4 one. 
Bad idea.  After I did a 'make install', it overwrote the libs in 
/usr/local/lib and the world was good.

I'm getting a lot of those UKNOWN client errors with bogus IP's.  I have 
an access list blocking access to the radius daemon from anywhere but 
the RASs.  What's going on there? Alan?

Cheers,

Mike

-- 

Mike Cathey - http://www.mikecathey.com/
Network Administrator
RTC Internet - http://www.catt.com/


- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to