From: Ivan Dubrov <wfragg@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Routing decision after FORWARD
Date: Sat, 30 Jun 2007 14:13:16 +0700 [thread overview]
Message-ID: <4686028C.1020007@gmail.com> (raw)
In-Reply-To: <46854467.7060309@nicaraguaopensource.com>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
There are three escenaries:
>
> (1) Packets destined to our machine
> (2) Packets originated inside our machine
> (3) Packets forwarded
>
> The table only have a reference to escenary (1) and the diagram after
> the tables hits all escenaries.
>
> Not all packets traverse all chains, that depends on the escenary.
>
I'm was already told that both are correct. There are two routing
decisions for forwarded packets (as it is drawn on the diagram) and the
second routing decision is mentioned in the table 6-3, step 8. However,
it is not clear, what kind of rules could be applied during the second
routing decision. The same as in first decision? In that case, does that
mean that I can set mark on the packet during the mangle/FORWARD and
route that packet to self in the second routing decision? And it will
traverse the table again, this time through INPUT chains?
Anyway, I've found easier solution for my needs, so these questions are
just for curiosity. :)
--
WBR,
Ivan S. Dubrov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-06-30 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 13:15 Routing decision after FORWARD Ivan Dubrov
2007-06-29 17:41 ` Jorge Davila
2007-06-30 7:13 ` Ivan Dubrov [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=4686028C.1020007@gmail.com \
--to=wfragg@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 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.