From: Thomas Zehetbauer <thomasz@hostmaster.org>
To: linux-kernel@vger.kernel.org
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: netfilter IPv6 support
Date: Fri, 27 Aug 2004 12:02:14 +0200 [thread overview]
Message-ID: <1093600934.3497.50.camel@hostmaster.org> (raw)
In-Reply-To: <20040826220501.GA564@alpha.home.local>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On Fre, 2004-08-27 at 00:05 +0200, Willy Tarreau wrote:
> These features are available in patch-o-matic-ng. They're not in mainline
> because the netfilter team only pushes well tested and non-intrusive changes.
> But there are lots of people using features from patch-o-matic in production.
It seems that the netfilter developers are far to conservative in this
case.
- Linux 2.6 is itself is still not deemed completely stable.
- IPv6 support is still marked experimental.
So I doubt someone would blame them for pushing a not so well tested
patch in this case but the current netfilter implementation for IPv6 is
far from useful completeness.
Tom
--
T h o m a s Z e h e t b a u e r ( TZ251 )
PGP encrypted mail preferred - KeyID 96FFCB89
finger thomasz@hostmaster.org for key
History has shown that the people who make history do not learn from it.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 481 bytes --]
next prev parent reply other threads:[~2004-08-27 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 18:52 netfilter IPv6 support Thomas Zehetbauer
2004-08-26 20:00 ` David S. Miller
2004-08-26 21:25 ` Thomas Zehetbauer
2004-08-26 22:05 ` Willy Tarreau
2004-08-27 10:02 ` Thomas Zehetbauer [this message]
2004-08-26 20:25 ` Jeff Garzik
2004-08-26 21:06 ` David S. Miller
2004-08-26 21:11 ` Jeff Garzik
2004-08-27 10:02 ` Thomas Zehetbauer
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=1093600934.3497.50.camel@hostmaster.org \
--to=thomasz@hostmaster.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@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