From: Julian Gomez <kluivert@tm.net.my>
To: netfilter@lists.netfilter.org
Subject: Re: why packet get through the netfilter even if i drop all in FORWARD
Date: Sun, 8 Jun 2003 20:43:16 +0800 [thread overview]
Message-ID: <20030608124316.GA1140@floyd> (raw)
In-Reply-To: <001e01c32d84$34f4fe70$95dc6f89@wonderland>
On Sun, Jun 08, 2003 at 04:07:11PM +1000, Calvin spoke thusly:
>I running netfilter with freeswan, I add a rule in FORWARD chain to drop
>all packets forward from internal iface(eth0) to public iface(eth1).
> iptables - A FORWARD -i eth0 -i eth1 -j DROP
Should that be 'iptables -A OUTPUT -i eth0 -o eth1 -j DROP' instead ?
>however once I start up the IPSEC, I do the ping again and A can ping
>GWb's eth0. The rule in FORWARD chain is still there.
iptables -A OUTPUT -p all -o eth1 -d GWb-IP-address -j DROP
>Why does this happen? Is that anyway I can fix this?
Explain your IPsec setup in detail, and then we can give you a proper
answer without guesswork.
next prev parent reply other threads:[~2003-06-08 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-08 6:07 why packet get through the netfilter even if i drop all in FORWARD Calvin
2003-06-08 12:43 ` Julian Gomez [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-08 23:21 George Vieira
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=20030608124316.GA1140@floyd \
--to=kluivert@tm.net.my \
--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.