Tnx for the fast reply.
10 sec timeout between packets is a long time, don't you think?
Or do you mean something else? When I test with NTPradping to
a non-existing ip in my lan it takes about 10 sec to complete 3 attempts,
and printing 'Could not receive a response from server'
so after that it should switch to the next server if it was able to do this.
I hope someone can point me in the right direction to change this.
I can't live with 30 sec, 15 would be more acceptable :-)
On 6/30/07, Alex M <radiussupport at lrcommunications dot net> wrote:
> I dono abou the code (well don't remember) but usually you send 3 packets
> and if server dosnt reply then go to the next server. If server time out
> 10 sec so here you will have 30 sec delay to switch to another server. +
> besides all that sockets is kinda slow when it does not see the server. In
> my VB app with sockets I can end up waiting for 1 min to find out that the
> server is down. Its probably good idea to chek with php manual to see
> is the delay id server does not exist
> -----Original Message-----
> From: YvesDM [mailto:ydmlog at gmail dot com]
> Sent: Saturday, June 30, 2007 10:20 AM
> To: Monowall Support List
> Subject: [m0n0wall] Fallover time between radius1 and radius2
> I've setup a second radius server and during my testing with m0n0wall I
> noticed a very long fallover time between radius1 and radius2.
> When I simulate a down radius1 it takes exactly 32 seconds to perform a
> login through radius2.
> That's quite a long time when you're waiting for it !!! Anyone else
> experiencing this?
> Is there a way to make this fallover time shorter?
> I've been digging a bit into the MW code, but I couldn't really find a
> setting reffering to this.
> btw I'm using MW 1.23
> Many tnx