<Zircon> .+ban *!*@76.68.206.166
<VaLkyRie> New ban: *!*@76.68.206.166 (requested)
In the channel :
* TesT (TesT@bas4-montreal28-1279577766.dsl.bell.ca) has joined #Zircon
* VaLkyRie sets mode: +b *!*TesT@bas?-montreal??-??????????.dsl.bell.ca
* TesT was kicked by VaLkyRie (DNS/IP matching an existing ban)
<Zircon> .+ban *!*@76.68.206.166
<VaLkyRie> New ban: *!*@76.68.206.166 (requested)
In the channel :
* TesT (TesT@bas4-montreal28-1279577766.dsl.bell.ca) has joined #Zircon
* VaLkyRie sets mode: +b *!*TesT@bas?-montreal??-??????????.dsl.bell.ca
* TesT was kicked by VaLkyRie (DNS/IP matching an existing ban)
This script is fully working for me.
For some unknown reason it started working for Amr (sort of) today; it bans only UK hosts apparently and leaves all the others alone.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM
For some unknown reason it started working for Amr (sort of) today; it bans only UK hosts apparently and leaves all the others alone. Laughing
hihi, that s a good start, the script is just getting familiar with all the IPs it has to ban
For me, this script works everytime it s supposed to, so i guess there is a problem in configuration the script, or some IP he wants to ban having the +f flag, or something like that, but the problem isnt with this script itself.
# Example: Say you ban 24.72.12.*, and someone enters the channel
# with a hostname of poached.eggheads.org.
# poached.eggheads.org's DNS entry is 24.72.12.134, so the
# user would be considered banned and treated as such. Same
# in reverse (ban *.eggheads.org would ban 24.72.12.134).