From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: 'netfilter' <netfilter@lists.netfilter.org>
Subject: Re: Problems with kernel 2.6.1 and iptables
Date: Mon, 16 Feb 2004 10:47:18 +0000 [thread overview]
Message-ID: <200402161047.18866.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <1076927162.2333.6.camel@raylinux.internal>
On Monday 16 February 2004 10:26 am, Ray Leach wrote:
> The 'filter' table does not exist by default, but the 'FILTER' table
> does. Is this a user chain than you created?
I think you're getting confused here about the difference between chains and
tables.
Chains are normally named in uppercase; standard ones are INPUT, OUTPUT,
PREROUTING, POSTROUTING, FORWARD. User-defined chains can of course be
added.
Tables are normally named in lowercase; standard ones are filter, nat, mangle.
Adding a user-defined table is quite a significant programming task, and not
to be assumed in a reasonably standard configuration of netfilter :)
The 'filter' table should exist in any healthy netfilter install.
Regards,
Antony.
--
If at first you don't succeed, destroy all the evidence that you tried.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-02-16 10:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 15:39 Routing problem Carlos Fernandez Sanz
2004-02-13 15:50 ` Antony Stone
2004-02-13 16:30 ` Carlos Fernandez Sanz
2004-02-13 17:12 ` Antony Stone
2004-02-14 8:41 ` Carlos Fernandez Sanz
2004-02-14 9:09 ` Antony Stone
2004-02-14 15:15 ` Carlos Fernandez Sanz
2004-02-14 15:19 ` Carlos Fernandez Sanz
2004-02-14 15:38 ` Antony Stone
2004-02-16 10:13 ` Problems with kernel 2.6.1 and iptables Jan Kaastrup
2004-02-16 10:26 ` Ray Leach
2004-02-16 10:47 ` Antony Stone [this message]
2004-02-16 11:19 ` Ray Leach
2004-02-16 13:18 ` Alexis
2004-02-16 14:05 ` Jan Kaastrup
2004-02-13 17:16 ` Routing problem Scott MacKay
2004-02-14 8:47 ` Carlos Fernandez Sanz
2004-02-13 16:53 ` John A. Sullivan III
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=200402161047.18866.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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