From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: iptables <netfilter@lists.samba.org>
Subject: Re: seeking heavy weaponry !!
Date: Sun, 7 Jul 2002 21:43:09 +0100 [thread overview]
Message-ID: <20020707204311.KLDF23840.mta03-svc.ntlworld.com@there> (raw)
In-Reply-To: <002201c2260e$b9fd7b70$28d33cd0@nebuchadnezza>
On Monday 08 July 2002 12:32 am, Tim wrote:
> Hey ppl,
>
> echo "[--Setting Policies--]"
> iptables -P INPUT DROP
> iptables -P OUTPUT DROP
> iptables -P FORWARD ACCEPT
Please set this one to DROP as well :-)
> #
> #
> ## Allow inside traffic to get to the DMZ and back
> iptables -A FORWARD -i $INTERNAL_NET -o $DMZ_NET -j ACCEPT
> iptables -A FORWARD -i $DMZ_NET -o $INTERNAL_NET -j ACCEPT
> iptables -A INPUT -i $INTERNAL_NET -s 192.168.1.0/24 -d 172.16.1.0/24
> -p icmp -j ACCEPT
> iptables -A OUTPUT -o $DMZ_NET -s 172.16.1.0/24 -d 192.168.1.0/24 -p icmp
> -j ACCEPT
> iptables -A INPUT -i $DMZ_NET -s 192.168.1.0/24 -d 172.16.1.0/24 -p icmp
> -j ACCEPT
> iptables -A OUTPUT -o $INTERNAL_NET -s 192.168.1.0/24 -d 172.16.1.0/24
> -p icmp -j ACCEPT #
You seem to have a big misunderstanding of how packets go through the chains
in iptables (hint: it's very different from ipchains...)
The INPUT chain is *only* for packets addressed to the firewall itself.
The FORWARD chain is *only* for packets going through the firewall from a
machine on one side to another machine on the other.
The OUTPUT chain is *only* for packets originated on the firewall itself.
No packet will ever go through both INPUT and FORWARD, or through both
FORWARD and OUTPUT.
Antony.
prev parent reply other threads:[~2002-07-07 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 23:32 seeking heavy weaponry !! Tim
2002-07-07 20:43 ` Antony Stone [this message]
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=20020707204311.KLDF23840.mta03-svc.ntlworld.com@there \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.samba.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