From: Ludo Stellingwerff <ludo@protactive.nl>
To: "Kevin D. White" <web_crawlz@yahoo.com>
Cc: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: RE: mangle, filter & FORWARD
Date: Wed, 02 Jun 2004 08:34:06 +0200 [thread overview]
Message-ID: <1086158045.4482.19.camel@laptop.stwerff.xs4all.nl> (raw)
In-Reply-To: <20040602051716.80453.qmail@web41705.mail.yahoo.com>
<<snip>>
> >
> > 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.
It's quite confusing for people used to working with ipchains:)
The terminology changed a bit:
Chains are now called tables and you have 3 root-tables: mangle, nat and
filter. To select them you would use the '-t' option of iptables,
defaulting to 'filter'.
Then you have 5 'hooks': the places in the network subsystem where these
tables can be used:
PRE-ROUTING, INPUT, FORWARD, OUTPUT, POST-ROUTING
Differents hooks accept different tables:
the mangle table at all-5 hooks.
the nat table at OUTPUT, PRE- and POST-ROUTING.
and filter table at INPUT, FORWARD and OUTPUT.
> >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?
>
Therefore it was the correct terminology: not all tables are tun on each
chain (hook).
In ipchains it was the other way around.
> >
> > For a really good refreence on iptables in general,
> > check out
> > http://iptables-tutorial.frozentux.net/
>
Did you check the http://lartc.org/howto/ ?
It very clear and handson.
Greetings,
Ludo Stellingwerff.
next prev parent reply other threads:[~2004-06-02 6:34 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
2004-06-02 6:34 ` Ludo Stellingwerff [this message]
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=1086158045.4482.19.camel@laptop.stwerff.xs4all.nl \
--to=ludo@protactive.nl \
--cc=netfilter@lists.netfilter.org \
--cc=web_crawlz@yahoo.com \
/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