From: Georgi Alexandrov <georgi.alexandrov@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: FORWARD Chain Question
Date: Sat, 10 Dec 2005 10:15:58 +0200 [thread overview]
Message-ID: <439A8EBE.3030505@gmail.com> (raw)
In-Reply-To: <BOEKIIIKCIBKDMDMHHLLIEPHDEAA.gene@poh.com>
Gene Dellinger wrote:
>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.
>
>
>
>
Actually yes, the first chain that it hits is the PREROUTING chain of
the mangle table.
ref:
http://iptables-tutorial.frozentux.net/iptables-tutorial.html#TRAVERSINGOFTABLES
regards,
Georgi Alexandrov
next prev parent reply other threads:[~2005-12-10 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 0:40 FORWARD Chain Question Gene Dellinger
2005-12-10 8:15 ` Georgi Alexandrov [this message]
[not found] <BOEKIIIKCIBKDMDMHHLLEEHFDFAA.gene@poh.com>
2005-12-12 21:46 ` Gene Dellinger
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=439A8EBE.3030505@gmail.com \
--to=georgi.alexandrov@gmail.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