This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.


For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.

sentinel register bot join part flood why ?

Old posts that have not been replied to for several years.
Locked
V
Volume
Halfop
Posts: 84
Joined: Fri May 23, 2003 5:08 am

sentinel register bot join part flood why ?

Post by Volume »

hello,
gives a funktion who sentinel ignore bots join/part op deop and kick flood ?
i would sentinel to be allowed all what bots doing and dont information me and on the partyline.

By restart all bots:
  • [21:28:21] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot2 on #channel!
    [21:28:21] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot3 on #channel!
    [21:28:21] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot4 on #channel!
    [21:28:21] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot5 on #channel!
    [21:28:21] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot6 on #channel!
    [21:28:21] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot7 on #channel!
    [21:28:21] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot8 on #channel!
    [21:28:21] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot9 on #channel!
    [21:28:21] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot10 on #channel!
    [21:28:21] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot11 on #channel!
    [21:28:21] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot12 on #channel!
    [21:28:21] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot13 on #channel!
    [21:28:21] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot14 on #channel!
    [21:28:22] <bot1> [21:12] sentinel: JOIN-PART flood detected by bot15 on #channel!
User avatar
slennox
Owner
Posts: 593
Joined: Sat Sep 22, 2001 8:00 pm
Contact:

Post by slennox »

sentinel.tcl won't ignore a flood except from users that are opped. The logic is that if sentinel ignored floods from hosts that simply matched recognised users, a flooder who spoofed the hosts of those users could freely flood the channel. I don't know how likely this scenario is today, but the decision was made at some point to make sure this didn't become a hole that could be exploited.

An option could be added to change this behaviour, but I'm not active enough on the script's development to add it at present.
Locked