mirc flood

[clever]

mirc's flood protection works by sending a ping to the server and waiting for an answer before sending a few more lines and another ping

the irc server normaly delays all msgs including the ping while your flooding causing a small buffer to fill up and once its filled you will flood out

ctrlproxy answers the ping asap causing mirc to think theres no flood protection in effect and it dumps everything to ctrlproxy at once

then ctrlproxy seems to just dump it all at once to the network causing me to flood out
and mirc sends enough to flood out just by connecting to the ctrlproxy even with all scripts shut off(proble a flood of /topic/names cmds)

[confusim (confusim)]

I don't know why, but I've never got "excess flood" while using mirc+nnscript with ctrlproxy. I agree that ctrlproxy should act like a normal ircserver.. You could test some other client, xchat for example.

[anonymous (anonymous-bugs)]

i was sharing that nick between both mirc and irssi at the time and only way to get it to connect is to get irssi AND mirc off the nick and reconnect just ctrlproxy then carefully put the clients back and punch the pc randomly when it floods out repeadedly

[Jelmer Vernooij (jelmer)]

I think this bug will have to be fixed by keeping a queue of client requests and handling them / sending them to the server in order.

[Jelmer Vernooij (jelmer)]

This is a somewhat more radical change than I feel comfortable with at the moment. Delaying until 3.0.3.

[clever (clever-nbnet)]

another way to fix the problem is to accept the mirc lines at full speed without care for flooding
and have ctrlproxy do its own global(all client) flood protection
so it has a single queue for the whole network with flood protection
but that may also be more work