Page 1 of 1

unrealircd and routers...

Posted: Fri Aug 19, 2005 8:30 pm
by WARP Radio
first off, I apologize if this is posted elsewhere.. I have looked, but didn't see an entry for this issue...

for starters:
I have a fully-working version of Unrealircd 3.2.3 installed and working..
Unrealircd is installed on a server in a datacenter under FreeBSD.
I have fully configured it and there are no problems with it- its stable and reliable :-)

The problem recently is that users- which use routers seem to have a problem staying connected.. they keep timing out. I remember this problem on efnet some years ago, as well.. but the interesting thing is one of my admins, who uses a router, is on my chat network and on efnet.. he "times out" on my network but remains connected on efnet... He has created a script which automatically sends a message once every minute to a non-used channnel (#junk) which seems to keep him and another admin connected.. I cannot figure this one out as I am on a switch and I remain connected- no matter what..

anyone else out there notice this problem and what I can do to address and correct it?

oh, and one other small thing.. is there a way to perminently add a gline to the server? I tried a "deny block" but it complained for a "type" so I just "remmed it out" for now.. its not a real biggie as long as the server remains running.. there are just times when I need to "cycle" the processes on the box and then I lose all the glines!

thanks in advance!

-DjZ-
:) :)

Posted: Fri Aug 19, 2005 9:03 pm
by Stealth
It sounds like your pingfreq is too high in the class block.

To add a permanent gline, use 0 as the time. To have the gline remain through server restarts, use your services AKill function.

Posted: Fri Aug 19, 2005 9:17 pm
by WARP Radio
hi there! and thanks for responding!

Actually, I have tried to set the pingfreq to a lower value and a higher value (currently set to 2 minutes)

class
clients {
pingfreq 120;
maxclients 10000;
sendq 100000;
recvq 8000;
};

again thanks for the reply :-)

-DjZ-
:) :)

Posted: Fri Aug 19, 2005 9:24 pm
by Stealth
You should try setting it to 60 or 90.

Also, everyone connected to the internet through a high-speed connection will eventually reach a router before they get to the internet, unless they are directly connected to their modem. Some of the cheaper routers may not be able to hold a connection as well as some of the more expensive ones. That is why messaging a channel every X seconds solves this problem, it tells the router the connection is still active.

Posted: Fri Aug 19, 2005 9:39 pm
by WARP Radio
Some of the cheaper routers may not be able to hold a connection as well as some of the more expensive ones.
I agree with you... but you try telling your chatters "its YOUR cheap router!" LOL

dosen't seem to effect those who are directly-connected to their modems.. or myself which is going through a switch

I'll set the pingfreq back to 60- though isn't that a bit excessive?

-DjZ-
:) :)

Posted: Fri Aug 19, 2005 9:44 pm
by Stealth
I think usually about 90 is good. 60 can be excessive, but you don't need to go in 30 second incriments, just lower it until the ping timeouts stop. If it goes too low, you will get sudden masses of users timing out, so don't go too low.

The pingfreq needs to be set based on your connection. If you have plenty of bandwidth, it can be a low number, but if you have limited bandwidth, it can be a higher number. I ran Unreal on dialup with ~7 users, and IIRC the pingfreq was 90.

Posted: Fri Aug 19, 2005 10:29 pm
by WARP Radio
"10-4" chief!

I'll give it a try I set to 80 that should be low enough to "keep things in check" but not "flood the server with pings"

I'll let you know if it helps...

again, thanks for the input!

-DjZ-
:) :)

Posted: Sun Aug 21, 2005 7:09 am
by Suchiara
Well I had the same problem (our lan has 6 segments, each separated with a pc-router). This is what solved my problem:

for mirc users we suggested to add

Code: Select all

on 1:CONNECT: { .timer 0 30 /.RAW PONG : $+ $server }
into 'remote'

increased pingfreq to 300.

Now everything seems to be stable.. I dunno why, but when I set pingfreq to 90, 120 or 180, the problem comes back again :roll: