From: Ivan Dubrov <wfragg@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Is there routing decision after FORWARD?
Date: Wed, 27 Jun 2007 19:02:49 +0700 [thread overview]
Message-ID: <468251E9.5040407@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 426 bytes --]
Hello,
Look here:
http://iptables-tutorial.frozentux.net/iptables-tutorial.html#TRAVERSINGGENERAL
According to the diagram, there is routing decision after
filter/FORWARD. However, according to the tables before, there is no
such routing (there is only one routing before mangle/FORWARD). The
question is, which one is correct?
Please CC me since I'm not subscribed to the list.
--
WBR,
Ivan S. Dubrov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2007-06-27 12:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=468251E9.5040407@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox