radiusd -X

[Alan DeKok]

kachin Agarwal wrote:
> I have done some experiments bcoz my auth-rate is low. i ve included
> timestamps in the freeradius code

  Use radiusd -Xx.  It will print out time stamps for you.  There is no
need to change the code.

> and in some modules. and i found out -
> 
>  Finished Request 0  : Tue, 15 Dec 2009 07:08:35  0.788477
> 
>  Going to the next Request  : Tue, 15 Dec 2009 07:08:35  0.788649
> 
>  Waking up in 4.9 seconds : Tue, 15 Dec 2009 07:08:35  0.788866
> 
>  rad_recv: Access-Request packet from host 127.0.0.1 port 10004,
> id=9,    length=306   :    Tue, 15 Dec 2009 07:08:35  0.857346
> 
> 
> As u can see from the above timestamp..  when it reaches the finished
> request 0 the timestamp in milli sec is 788.4ms.so till "waking up in
> 4.9 sec" it hardly takes 0.4ms
> But after this "Waking up in 4.9 sec" till the next request "rad_recv"
> it takes about 70ms.
> 0.857346 - 0.788866 = ~70 ms
> What does it do for such a long time till the next request comes in??

  Nothing.

  What does a web server do when no one asks for a web page?

  What does an email server do when no one is sending email?

  I think the issue here is larger than RADIUS.  You are trying to
understand the RADIUS server even though you aren't clear how networks
work.  First, understand networks.  After that, do in-depth
investigations of RADIUS servers.

  Alan DeKok.