From: "Patrick Ahler" <patrick@vikus.com>
To: netfilter EMAIL <netfilter@lists.netfilter.org>
Subject: Forwarding Problems
Date: Thu, 6 Mar 2003 11:56:18 -0500 [thread overview]
Message-ID: <ABEKJILKOKKGGDJKHKDFOEBGCAAA.patrick@vikus.com> (raw)
I have iptables FORWARD chain working except for one minor detail... after I
set all the ACCEPT rules, I want to set a drop rule/policy to the FORWARD
CHAIN as well, thus dropping all the packets I haven't accepted. The problem
is, if I use
iptables -A FORWARD -j DROP
or
iptables -P FORWARD DROP
they will drop all packets including the ones I already ACCEPTed.
example (want to allow all incoming and outgoing www traffic):
iptables -A FORWARD -p tcp -d 192.168.1.0/24 --dport 80 -j ACCEPT
iptables -A FORWARD -p tcp -d 192.168.1.0/24 --sport 80 -j ACCEPT
iptables -A FORWARD -p tcp -s 192.168.1.0/24 --dport 80 -j ACCEPT
iptables -A FORWARD -p tcp -s 192.168.1.0/24 --sport 80 -j ACCEPT
iptables -A FORWARD -j DROP
Any help is greatly appreciated
next reply other threads:[~2003-03-06 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 16:56 Patrick Ahler [this message]
2003-03-06 18:17 ` Forwarding Problems Rob Sterenborg
-- strict thread matches above, loose matches on Subject: below --
2003-03-06 18:10 Khanh Tran
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=ABEKJILKOKKGGDJKHKDFOEBGCAAA.patrick@vikus.com \
--to=patrick@vikus.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox