From: "Dick St.Peters" <stpeters@NetHeaven.com>
To: netfilter@lists.netfilter.org
Subject: RE: mangle, filter & FORWARD
Date: Wed, 2 Jun 2004 11:04:47 -0400 [thread overview]
Message-ID: <16573.60559.927239.101640@saint.heaven.net> (raw)
In-Reply-To: <1086158045.4482.19.camel@laptop.stwerff.xs4all.nl>
Ludo Stellingwerff writes:
> Chains are now called tables and you have 3 root-tables: mangle, nat and
This is utterly wrong. Chains are still called chains. See
"man iptables" and "iptables --help". Tables are groups of
related-purpose chains.
> Then you have 5 'hooks': the places in the network subsystem where these
> tables can be used:
> PRE-ROUTING, INPUT, FORWARD, OUTPUT, POST-ROUTING
PREROUTING, INPUT, FORWARD, OUTPUT, and POSTROUTING are the names of
chains. Fulling specifying a chain requires giving its chain name and
the table it's in.
I realize most users on the list know this, but I felt this
needed correcting for the archives.
> > > 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.
It also has very little to do with ntfilter/iptables.
--
Dick St.Peters, stpeters@NetHeaven.com
next prev parent reply other threads:[~2004-06-02 15:04 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
2004-06-02 15:04 ` Dick St.Peters [this message]
-- 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=16573.60559.927239.101640@saint.heaven.net \
--to=stpeters@netheaven.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