Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Kevin D. White" <web_crawlz@yahoo.com>
To: netfilter@lists.netfilter.org
Subject: RE: mangle, filter & FORWARD
Date: Tue, 1 Jun 2004 22:17:16 -0700 (PDT)	[thread overview]
Message-ID: <20040602051716.80453.qmail@web41705.mail.yahoo.com> (raw)
In-Reply-To: <7C9884991ADAE0479C14F10C858BCDF591E320@alderaan.smgtec.com>


--- Daniel Chemko <dchemko@smgtec.com> wrote:
> 
> > As you can see, there is no reference to either
> the
> > mangle table or filter table...
> 
> The filter table is always implied if not explicitly
> stated otherwise

Perfect, thank you.
 
> >so where does the
> > system append the rule?  An obvious answer might
> be
> > that the system appends the rule in both FORWARD
> > chains, (if there is two chains).
> 
> Nope (thankfully)
I know now that there are two FORWARD chains,
mangle.FORWARD and filter.FORWARD.  They have the same
name and are the same chain structure, they will
contain completely different rules.


> The MANGLE table's are not for filtering data.
> Mangle's are typically
> used for inline parameter modifications like
> changing the TOS/MSS/etc...

Yep, I got that much so far

> The order on any given chain is
> raw/mangle/filter/nat. 

I thought the order for a forwarded packet was
mangle/nat/mangle/filter/mangle/nat

>Not all tables
> are run on each chain. Eg. FORWARD table only has
> mangle/filter.

Ok, you must mean "not all the chains are used in each
table", right?  "The FORWARD chains only appear in the
mangle and filter tables", yes?
 
> 
> For a really good refreence on iptables in general,
> check out
> http://iptables-tutorial.frozentux.net/

Right, this document is the source of some my
confussion, for several reasons but mainly because it
never mentioned that although the chains have the same
name and have the same function, they are in fact
different chains.  I think this is because use of the
mangle.FORWARD chain would be a rare occurance and
most of the time it is going to be empty.  



	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 


  reply	other threads:[~2004-06-02  5:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01 17:58 mangle, filter & FORWARD Daniel Chemko
2004-06-02  5:17 ` Kevin D. White [this message]
2004-06-02  6:34   ` Ludo Stellingwerff
2004-06-02 15:04     ` Dick St.Peters
  -- strict thread matches above, loose matches on Subject: below --
2004-06-01 17:28 Kevin D. White
2004-05-31 20:14 Kevin D. White
2004-05-31 21:39 ` Justin Friel

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=20040602051716.80453.qmail@web41705.mail.yahoo.com \
    --to=web_crawlz@yahoo.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