UnrealIRCd Forums

for some unknown reason, the irc server started to ignore configured ping frequencies and now only does 1 ping every 10 minutes on all classes (i have it set up various per class in .conf) i tried /restart but didn't help. all other server's functions work normally. what is wrong?

I'm no expert, but doesnt the IRCd not ping an active client? Maybe it just does more rarely? Maybe I'm completely wrong?

first, i've been told about this from mirc users(obviously, not hiding ping-pong events shows this quite fast), then i tried to test by telnet and after the first connect pong response, next ping comes after 10 minutes and if i don't respond, the ping timeout comes after another 10 minutes.

Could you paste the output of /stats Y please?

here it is

22:25:44 -!- Y servers 90 100 10 1000000 8000
22:25:44 -!- Y restricted 60 0 20 50000 5000
22:25:44 -!- Y web 600 0 1000 30000 4000
22:25:44 -!- Y opers 90 0 10 300000 10000
22:25:44 -!- Y adv_users 90 0 1000 150000 9000
22:25:44 -!- Y users 90 0 1000 100000 8000
22:25:44 -!- Y default 120 0 100 3000000 8000
22:25:44 -!- Y End of /STATS report

Ok, I think the problem is that all users get in the "web" class instead of the correct one (users?).
Check your allow blocks.

allow {
ip *@*;
hostname *@*;
class users;
maxperip 18;
};

allow {
hostname *@localhost;
ip *@127.0.0.1;
class web;
maxperip 1000;
options {
noident;
};
};

this seems to be ok in config file, i had also idea about increasing ping frequency for web users but the time is still around 10 minutes(and no class has it set to this time)

Are those your only allow blocks?

yes, only these 2 (there are some others but they are commented out and have never been used)

Hmm strange.... Paste the output of "/stats allow" too, just to be sure...

11:18:47 -!- I *@127.0.0.1 * *@localhost 1000 web my.irc.server 6667
11:18:47 -!- I *@* * *@* 18 users my.irc.server 6667
11:18:47 -!- I End of /STATS report

anyway, i deleted and re-installed the whole ircd and now it seems the pings are ok...as mysteriously the problem appeared, so same way it is gone...