local users - excess flood

garethnelsonuk · none Joined: 03 Oct 2004 Posts: 16

i've recently been experiencing some trouble on my network with users (and specifically eggdrop bots) getting kicked off with an excess flood error

my IRCD is hybrid 7.0.3 and i'm running anope for services (though i get the same error with services delinked)

mainly it's eggdrops and users logged in from the same LAN as one of the servers, or even people with shell accounts on the server connecting to localhost

any ideas what could be causing this?

(if anyone needs to see my ircd.conf just ask)

katsklaw · Guru Joined: 28 Jun 2004 Posts: 1114

excess flood quits are from the user exceeding his/her sendQ, which is a setting in your ircd.conf file. The quit has nothing to do with Services.

Common reasons for excess flood quits are playing extremely large ASCII pop-ups without using some sort of delay between lines, mass amounts of spam or other large amounts of data being sent to a channel or user at a high rate of speed. If you find that legit users can flood themselves off easily you should increase the sendQ because it's set too low, but becareful to not set this too high.

If you only have a few users/bots that quit from excess flood then they are likely doing something to cause it.

garethnelsonuk · none Joined: 03 Oct 2004 Posts: 16

My eggdrops have only recently started getting kicked off, i did increase the SendQ but no luck.

I've been thinking - is it possible that since all the bots are running on the same machine as the IRCD that the IRCD sees them all as clones and therefore it's the combined data being dumped by all the bots and local users?

aquanight · Lurker Joined: 14 Jun 2004 Posts: 118 Location: Boise, ID

Excess flood can be recvq as well. Remember: sendq is data the ircd sends to the client, recvq is data from client to server. RecvQs are typically smaller (enough to hold maybe 10 full length (512 bytes) messages)). So if your bot is sending a lot of data and gets disconnected for "Excess flood" then 1) make it try to control it's own sending (eg, queue it's messages to be on par with the fakelag (or whatever flood control system your ircd uses. hybrid probably uses fakelag (which is defined in RFC1459 I believe)) system) or 2) up the recvq if it's really low (for example 2KB is probably too small.)