Dave Harman wrote:


> # ------------------------------------------------------------------
> #
> SYNOPT="-m limit --limit 5/second --limit-burst 10" # Page 99
> INTERNET="eth0"
> PRIVATE="eth1"
> NSW2IP="66.138.30.243"
> PIP="192.168.1.0/24"
> GEOCITIES="66.218.77.68"
> ONBITCHX="81.196.20.133"
> SCRIPTKIDDIE1="24.197.112.13"
> SCRIPTKIDDIE2="66.194.6.80"
> SCRIPTKIDDIE3="65.54.188.73"
> SCRIPTKIDDIE4="69.41.171.93"
> SCRIPTKIDDIE5="24.28.185.170"
> SCRIPTKIDDIE6="134.253.26.12"
> SCRIPTKIDDIE7="155.147.191.139"
> # ------------------------------
> CLASS_A="10.0.0.0/8" # Class-A Private (RFC-1918)
.... snip ...
>
>
>
> Thanks Again
>
> Dave Harman

A bit offtopic but: rather than spend all this time looking for script
kiddies to block, why don't you just block everything except for the stuff
that you do.

Then enable stateful firewalling to ensure that you can connect to them but
they can't connect to you...

It's pointless posting a huge iptables script and expect someone to go over
it with a toothpick looking for your problem - people generally won't be
bothered with the time it takes.

A good firewall script needn't be more than 10k in size. I have one that's
about 25k, but then there are 6 physical interfaces and up to another 50
virtual ones.