From: Andrew Beverley <andy@andybev.com>
To: netfilter@buglecreek.com
Cc: netfilter@vger.kernel.org
Subject: Re: Correct Chains to Apply Rules
Date: Tue, 17 May 2011 23:19:38 +0100 [thread overview]
Message-ID: <1305670778.2741.10.camel@andybev-desktop> (raw)
In-Reply-To: <1305669045.20717.1453045045@webmail.messagingengine.com>
On Tue, 2011-05-17 at 15:50 -0600, netfilter@buglecreek.com wrote:
Please don't top post.
> OK. Thanks. So to block/allow traffic from network A to/from network B
> I would apply my rules to the FORWARD chain using a source/destination.
Yes.
> The INPUT and OUTPUT chains on eth0 and eth1 are only for traffic bound
> for the firewall/router box itself?
Yes.
A picture paints a thousand words:
http://upload.wikimedia.org/wikipedia/commons/3/37/Netfilter-packet-flow.svg
Or if you want a simpler version:
http://www.docum.org/docum.org/kptd/
Andy
prev parent reply other threads:[~2011-05-17 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 21:14 Correct Chains to Apply Rules netfilter
2011-05-17 21:29 ` Pascal Hambourg
2011-05-17 21:50 ` netfilter
2011-05-17 22:06 ` Jorge Dávila
2011-05-17 22:19 ` Andrew Beverley [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=1305670778.2741.10.camel@andybev-desktop \
--to=andy@andybev.com \
--cc=netfilter@buglecreek.com \
--cc=netfilter@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).