From: Willy Tarreau <willy@w.ods.org>
To: Thomas Zehetbauer <thomasz@hostmaster.org>
Cc: linux-kernel@vger.kernel.org, netfilter-devel@lists.netfilter.org
Subject: Re: netfilter IPv6 support
Date: Fri, 27 Aug 2004 00:05:01 +0200 [thread overview]
Message-ID: <20040826220501.GA564@alpha.home.local> (raw)
In-Reply-To: <1093555510.3497.33.camel@hostmaster.org>
On Thu, Aug 26, 2004 at 11:25:10PM +0200, Thomas Zehetbauer wrote:
> On Don, 2004-08-26 at 13:00 -0700, David S. Miller wrote:
> > Stateful netfilter is not there because it's a total waste
> > to completely duplicate all of the connection tracking et al.
> > code into ipv6 counterparts when %80 of the code is roughly
> > the same. People are working on a consolidation of these
> > things so that there is no code duplication but it is a lot
> > of work and there are bigger fires to put out at the moment.
>
> Of course it's a waste to duplicate the code but as far as I remember
> the status of netfilter for IPv6 has not changed for almost a year. As
> said there is still not even the basic REJECT target available.
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.
You can get those here :
ftp://ftp.netfilter.org/pub/patch-o-matic-ng/
Please also take a look at the mailing list archives since it's an area
which is currently moving :
http://marc.theaimsgroup.com/?l=netfilter-devel
Regards,
Willy
next prev parent reply other threads:[~2004-08-26 22:09 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 [this message]
2004-08-27 10:02 ` Thomas Zehetbauer
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=20040826220501.GA564@alpha.home.local \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=thomasz@hostmaster.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