Alchera wrote:I prefer *!*user@*.domain myself, simply to be fair.
isnt fair either, because users from i.E. java chat will all be banned from same ISP. dont forget domain.host.com representats a single IP and as long its no bouncer with same vhost it will be only 1 ISP connection.
Only that particular user is banned. It takes into account cyber cafe's which the other method does not! I have bots in channels which are setup by users of cyber cafe's and banning an entire cyber for the error of one user is ludicrous! I also use wildcards when an actual host is shown (cybers only have non RDNS IP's).
I have found that using "nick!*@host.domain" or "nick!*user@*.domain" useless as that is the one thing a banned user will do, change nicks but they rarely change their user name (identd).
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM
Alchera wrote:What I was getting at was this (as an example):
* Enfield sets mode: +b *!*chindians@219.95.230.*
Only that particular user is banned. It takes into account cyber cafe's which the other method does not! I have bots in channels which are setup by users of cyber cafe's and banning an entire cyber for the error of one user is ludicrous! I also use wildcards when an actual host is shown (cybers only have non RDNS IP's).
I have found that using "nick!*@host.domain" or "nick!*user@*.domain" useless as that is the one thing a banned user will do, change nicks but they rarely change their user name (identd).
These types of bans quicky fill up the banlists especially on larger channels, as you know flood bots have a tendency to change their nicks and idents quickly and randomly so I would suggest not to include idents or nick in the banmask, only the domain and/or host.
·awyeah·
==================================
Facebook: jawad@idsia.ch (Jay Dee) PS: Guys, I don't accept script helps or requests personally anymore.
==================================
My Bots used to lock the channel when the channel banlist was full It rarely triggered the locking script tho. I used *!*ident@*.domain.com bans on 99% of my scripts.
The lifecycle of a noob is complex. Fledgling noobs gestate inside biometric pods. Once a budding noob has matured thru gestation they climb out of their pod, sit down at a PC, ask a bunch of questions that are clearly in the FAQ, The Noob is born
I use *!*ident@*.domain.com in all scripts without a drama. As for spam bots, I use a script I have especially written to cope with them. It bans consonant nicks/numerical idents on entry. As soon as they enter the channels are set +cmR, the ban set and the offender kicked. In the case of numerical idents my script emulates DALnet's ChanServ where a numerical ident like "h23f7f990@" will set a ban of *!*0*@*; the last digit in the ident else it sets *!*ident@*.domain.com, both the mode setting and ban are timed.
On average there are two innocent users per channel per 24 hr period that get banned, bot users are ignored.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM