All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lopsch <lopsch@lopsch.com>
To: Netfilter-Mailinglist <netfilter@lists.netfilter.org>
Subject: [Fwd: Re: questions about chain traversal, new ascii diagram]
Date: Thu, 06 Jan 2005 22:11:17 +0100	[thread overview]
Message-ID: <41DDA975.1010607@lopsch.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1225 bytes --]

Curby . schrieb:
> ----Original Message Follows----
>
>> http://joerg.fruehbrodt.bei.t-online.de/pics/abb3_netfilter_ablaufdiagramm.jpg
>>
>>
>> What about the mangle decisions, do you also want to include them :D?
>
>
> It looks reasonable, but if this is true then the article I mentioned
> was wrong.  Perhaps there should be a disclaimer by the link on the
> netfilter documentation page?
>
> Does anyone know the answers to my other questions? Specifically, is it
> due to style or technical reasons that people don't filter traffic in
> PREROUTING, and instead put the same rules in both FORWARD and INPUT?
>
> I think you were probably just being facetious, but I wouldn't mind
> knowing when the mangle chains come into play.  If we have to jump to
> them explicitly though, then I'll just RTFM. =)
>
> Thanks again!
>
> --Curby
>
>
>
They are traversed before the other ones e.g.

PREROUTING mangle -> PREROUTING nat -> FORWARD mangle -> FORWARD filter
-> POSTROUTING mangle -> POSTROUTING nat

PREROUTING mangle -> PREROUTING nat -> INPUT mangle -> INPUT FILTER ->
local process

local process -> OUTPUT mangle -> OUTPUT nat -> OUTPUT filter ->
POSTROUTING mangle -> POSTROUTING nat

Greets

--

PGP-ID 0xF8EAF138


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 851 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

                 reply	other threads:[~2005-01-06 21:11 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=41DDA975.1010607@lopsch.com \
    --to=lopsch@lopsch.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.