I think there is an easier way of doing this...<br>
<br>
Why not use the GEOIP IPTABLES patch and then just use this in your firewall:<br>
<br>
-----------------------------------------------------------------------------------------<br>
$IPTABLES -A INPUT -p tcp -m geoip --src-cc CN -j DROP<br>
$IPTABLES -A INPUT -p tcp -m geoip --src-cc KR -j DROP<br>
$IPTABLES -A INPUT -p tcp -m geoip --src-cc TW -j DROP<br>
$IPTABLES -A INPUT -p tcp -m geoip --src-cc HK -j DROP<br>-----------------------------------------------------------------------------------------<br>
<br>
This way you have 4 simple rules which do the work of that entire script.<br>
<br>
<br><div><span class="gmail_quote">On 10/10/05, <b class="gmail_sendername">Taka John Brunkhorst</b> &lt;<a href="mailto:antiwmac@...">antiwmac@...</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
nice but why do we need to block them?<br>
ssh worms? or just lamers?<br clear="all"><br>-- <br><a href="mailto:antiwmac@..." target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">antiwmac@...</a><br><span class="sg">Taka John Brunkhorst

</span></blockquote></div><br>