Page 1 of 1

Posted: Thu Jan 20, 2005 2:23 am
by Syzop
I've never experienced such a bug on my (private) network which is entirely SSL.. Users can idle there just fine for hours...

What's your ping frequency? (class::pingfreq)
..because when the same user connects via plain connection (no ssl) he can stay connected for..
Best thing is if you would have the same user connected 2 times _at the same time_, so 1 SSL and 1 non-ssl.. and then see if only ssl dies and the other one keeps going on for like an hour...
Is this what you tried? If not, worth doing so :)

Posted: Thu Jan 20, 2005 5:50 am
by jailmann
Hello

i have kind of the same problem

i have 2 user that use ssl but the dies servel times during the day / night when they just ideling but if the are on non ssl then there no problem

one of the user have tried to be on a non ssl the whole night an he have not been ping timeout yet

Posted: Thu Jan 20, 2005 6:55 am
by jailmann
Hello

i forgot to show what my ping is

class clients
{
pingfreq 30;
maxclients 500;
sendq 100000;
recvq 8000;
};

class servers
{
pingfreq 90;
maxclients 10; /* Max servers we can have linked at a time */
sendq 1000000;
connfreq 50; /* How many seconds between each connection attempt */
};

Posted: Thu Jan 20, 2005 7:37 pm
by Syzop
30 is low for clients, I suggest using something like 90, 120 or 180.
With 30 if there's a temporary network problem, connections might have insufficient time to restore.