From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: "Curby ." <kirbysdl@hotmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: questions about chain traversal, new ascii diagram
Date: Fri, 07 Jan 2005 22:08:39 +0000 [thread overview]
Message-ID: <41DF0867.2060505@dsl.pipex.com> (raw)
In-Reply-To: <BAY101-F23030A22FC86C1A88C1F93DF930@phx.gbl>
Curby . wrote:
> ----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?
Respecting johns answer - as I don't do much firewall stuff, but I
thought it was because there are no filter tables in pre/post.
http://www.docum.org/docum.org/kptd/
>
> 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. =)
AIUI use mangle if you want to mark/change(mangle) packets eg TOS bits.
>
> Thanks again!
>
> --Curby
>
>
>
>
next prev parent reply other threads:[~2005-01-07 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 17:23 questions about chain traversal, new ascii diagram Curby .
2005-01-06 17:49 ` Lopsch
2005-01-06 19:20 ` Curby .
2005-01-07 2:12 ` John A. Sullivan III
2005-01-07 22:08 ` Andy Furniss [this message]
2005-01-06 20:50 ` Ipfilter for DHCP client sisdis
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=41DF0867.2060505@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=kirbysdl@hotmail.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.