From: Jim Laurino <nfcan.x.jimlaur@dfgh.net>
To: netfilter@lists.netfilter.org
Subject: Re: FORWARD Chain Question (nfcan: addressed to exclusive sender for this address)
Date: Mon, 12 Dec 2005 19:16:56 -0500 [thread overview]
Message-ID: <20051213001656.GE1795@salty> (raw)
In-Reply-To: <BOEKIIIKCIBKDMDMHHLLAEHGDFAA.gene@poh.com> (from +nfcan+jimlaur+17e0952d2c.gene#poh.com@spamgourmet.com on Mon, Dec 12, 2005 at 16:46:09 -0500)
On 2005.12.12 16:46, Gene Dellinger - gene@poh.com wrote:
> To All:
> I got some helpful information, thanks to those who responded, I am still a
> bit fuzzy though.
> A packet coming in ETH0 destined for a system connected to ETH1, will that
> packet begin in the PREROUTING
> chain on ETH1(sample 1) and then out or go to the FORWARD chain(sample 2)
> and then out.
Neither example matches the structure of netfilter.
There is only one each of prerouting, forward, postrouting.
There is not one chain per interface.
If you need to specify the interface in a rule,
you must use the -i and -o fields in that rule.
One or the other of these fields may not be useable in some chains.
>
> ETH0:PREROUTING---->FORWARD---->POSTROUTING---->OUT
> | | |
> INPUT | OUTPUT
> | \|/ |
> Local Process | Local Process
> |
> ----<---<-----|
> |
> \|/
> ETH1:PREROUTING---->FORWARD---->POSTROUTING---->OUT
> | |
> INPUT OUTPUT
> | |
> Local Process Local Process
>
> sample 1
> _________________________________________________________
>
> ETH0:PREROUTING---->FORWARD---->POSTROUTING---->OUT
> | | |
> INPUT | OUTPUT
> | \|/ |
> Local Process | Local Process
> |
> |
> |
> \|/
> ETH1:PREROUTING---->FORWARD---->POSTROUTING---->OUT
> | |
> INPUT OUTPUT
> | |
> Local Process Local Process
>
> sample 2
> _________________________________________________________
>
>
> Thanks Again
> Gene D.
>
>
> -----Original Message-----
> From: Gene Dellinger [mailto:gene@poh.com]
> Sent: Friday, December 09, 2005 2:40 PM
> To: netfilter@lists.netfilter.org
> Subject: FORWARD Chain Question
>
>
> On a multi-homed machine being used as a firewall, if
> a packet is forward'd from one interface to another.
> Does the packet enter the in at PRE-ROUTING portion of iptables
> chain again for that interface? It may seem obvious but
> I just want to make sure I am clear on that aspect of the
> chain traversal.
>
> Thanks
> Gene D.
>
>
>
--
Jim Laurino
nfcan.x.jimlaur@dfgh.net
Please reply to the list.
Only mail from the listserver reaches this address.
next prev parent reply other threads:[~2005-12-13 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BOEKIIIKCIBKDMDMHHLLEEHFDFAA.gene@poh.com>
2005-12-12 21:46 ` FORWARD Chain Question Gene Dellinger
2005-12-13 0:16 ` Jim Laurino [this message]
2005-12-13 10:30 ` Jörg Harmuth
2005-12-13 19:21 ` Gene Dellinger
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=20051213001656.GE1795@salty \
--to=nfcan.x.jimlaur@dfgh.net \
--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.