Форум о ботах Eggdrop/Windrop

[indjov]

Здравствуйте,
У меня есть tcl, который проверяет идентификатор пользователя при входе в канал.
Этот tcl я использую прокси-защиту.
Но я думаю, что это сценарий ставит запрет маску *!*@*, И поставить этот запрет после того как кто-то падает с сетевого сервера и обратно онлайн

Код: Выделить всё

bind join - "*" badident

proc badident {nick host hand chan} {
 if {[matchattr $hand X]} {
  putlog "14Защитен потребител:15 $nick ($host)"
  return 0
}
   if {![isbotnick $nick] && [botisop $chan]} {
    if {[regexp {^~[a-z]{1}[0-9]{2,5}$} [lindex [split $host @] 0]]} {
      newchanban $chan *!*@[lindex [split $host @] 1] $::botnick "proxyta sa zabraneni" 120
      }
   }
}


[tvrsh]

I dont understand you. What do you want?

[indjov]

After the split of one of the servers, and when he is back online, my bot decided to put a ban on this mask *! * @ *.
I looked all your tcl`s seemingly everything is fine
bother me only one tcl.

I think this tcl above in the post which I have given, failed to make a proper inspection and puts ban *! * @ *, But I'm not sure that so

[tvrsh]

This isnt my tcl. Maybe this ban was set by sentinel.tcl or allprotection.tcl because they decide this is mass join flood? The reason of *!*@* ban is "proxyta sa zabraneni"?

[indjov]

No,
Do not use these tcl , this tcl wrote separately and only for protection proxies check the ID of the client and if it has numbers ~ and accepts proxy.
The verification code here is correct, but when there is a split and returns the server, and this mass input, and bot ban put on this mask.
Interestingly, after the ban, bot not kick for any reasons

[tvrsh]

Your tcl didnt match mass join, it only check users ident, so *!*@* was set by another script. Check you flood-join and ban-type from eggdrop.conf

# flood-join 5:60
# Set here how many joins in how many seconds from one host constitutes
# a flood. Setting this to 0 or 0:0 disables join flood protection for
# the channel.

Try to disable it.