1 |
I just wonder where this patch resides? and for which version what version |
2 |
it applies and such... I saw it in a earlier post but it got lost somewhere |
3 |
in my inbox. Anybody care to post it? |
4 |
|
5 |
Thanks. |
6 |
|
7 |
On 10/10/05, Dave Strydom <strydom.dave@×××××.com> wrote: |
8 |
> |
9 |
> I think there is an easier way of doing this... |
10 |
> |
11 |
> Why not use the GEOIP IPTABLES patch and then just use this in your |
12 |
> firewall: |
13 |
> |
14 |
> |
15 |
> ----------------------------------------------------------------------------------------- |
16 |
> $IPTABLES -A INPUT -p tcp -m geoip --src-cc CN -j DROP |
17 |
> $IPTABLES -A INPUT -p tcp -m geoip --src-cc KR -j DROP |
18 |
> $IPTABLES -A INPUT -p tcp -m geoip --src-cc TW -j DROP |
19 |
> $IPTABLES -A INPUT -p tcp -m geoip --src-cc HK -j DROP |
20 |
> |
21 |
> ----------------------------------------------------------------------------------------- |
22 |
> |
23 |
> This way you have 4 simple rules which do the work of that entire script. |
24 |
> |
25 |
> |
26 |
> On 10/10/05, Taka John Brunkhorst <antiwmac@×××××.com> wrote: |
27 |
> > |
28 |
> > nice but why do we need to block them? |
29 |
> > ssh worms? or just lamers? |
30 |
> > |
31 |
> > -- |
32 |
> > antiwmac@×××××.com |
33 |
> > Taka John Brunkhorst |
34 |
> |
35 |
> |
36 |
> |