From: Alejandro Flores <alejandro.flores@triforsec.com.br>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: droping in forward/postrouting
Date: Sat, 31 Jul 2004 09:11:31 -0300 [thread overview]
Message-ID: <1091275890.17060.20.camel@aflores> (raw)
In-Reply-To: <a0f69e504072923151d18afa3@mail.gmail.com>
Hi there,
> hi
> I duno but filter table "FORWARD" not blocking/dropping any of these
> site actaully these are spywares a gift from windowz and why i want to
> drop these dirty shits coz they consume lot of my precious bandwidth
> "dialup" ;)
>
> iptables -I FORWARD -s 0/0 -d 66.35.229.0/24 -j DROP
> iptables -I FORWARD -s 0/0 -d 212.4.208.105 -j DROP
> iptables -I FORWARD -s 0/0 -d 66.35.229.185 -j DROP
> iptables -I FORWARD -s 0/0 -d 64.152.73.0/24 -j DROP
> iptables -I FORWARD -s 0/0 -d 66.35.229.236 -j DROP
>
> However PREROUTING do working and dropping it :)
>
> iptables -t nat -I PREROUTING -s 0/0 -d 66.35.229.0/24 -j DROP
> iptables -t nat -I PREROUTING -s 0/0 -d 212.4.208.105 -j DROP
> iptables -t nat -I PREROUTING -s 0/0 -d 66.35.229.185 -j DROP
> iptables -t nat -I PREROUTING -s 0/0 -d 64.152.73.0/24 -j DROP
> iptables -t nat -I PREROUTING -s 0/0 -d 66.35.229.236 -j DROP
>
> Therefore my confusion still exists, as rule is that to filter in
> fiter table and other things NATting , mangling in nat and mangle
> table respectively.
>
> Then why FOWARD not blocking these sites and nat PREROUTING does?
If you're using both (drop in prerouting and forward), the packets are
dropped in nat prerouting. You know why? When the packet starts the
'netfilter journey' it goes to:
1. table mangle -> chain PREROUTING
2. table nat -> chain PREROUTING (you're dropping packets here)
(routing decision)
3b. table mangle -> chain FORWARD
4b. table filter -> chain FORWARD
5. table mangle -> chain POSTROUTING
6. table nat -> chains POSTROUTING
Remove the drop in PREROUTING, and change your FORWARD rules to
something like:
iptables -A FORWARD -i LAN_IF -o EXT_IF -d spywarez_site/mask -j DROP
You don't have to specify the source if the source is any (-s 0/0).
Regards,
Alejandro Flores
next prev parent reply other threads:[~2004-07-31 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 15:54 droping in forward/postrouting richardo
[not found] ` <a0f69e504072913084fc39ee8@mail.gmail.com>
2004-07-30 6:15 ` Askar Ali Khan
2004-07-31 7:48 ` Antony Stone
2004-07-31 12:27 ` Askar Ali Khan
2004-07-31 12:11 ` Alejandro Flores [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-31 23:58 Jason Opperisano
2004-07-30 8:15 richardo
2004-07-29 10:19 Askar Ali Khan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1091275890.17060.20.camel@aflores \
--to=alejandro.flores@triforsec.com.br \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.