From: "David S. Miller" <davem@redhat.com>
To: Thomas Zehetbauer <thomasz@hostmaster.org>
Cc: netfilter-devel@lists.netfilter.org, linux-kernel@vger.kernel.org
Subject: Re: netfilter IPv6 support
Date: Thu, 26 Aug 2004 13:00:24 -0700 [thread overview]
Message-ID: <20040826130024.6ff83dff.davem@redhat.com> (raw)
In-Reply-To: <1093546367.3497.23.camel@hostmaster.org>
On Thu, 26 Aug 2004 20:52:47 +0200
Thomas Zehetbauer <thomasz@hostmaster.org> wrote:
> Although linux was one of the first to support IPv6 it seems to me that
> netfilter support has almost stuck. There is still not even a REJECT
> target not to mention stateful filtering for IPv6.
Why not ask the netfilter development lists such questions?
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.
WARNING: multiple messages have this Message-ID (diff)
From: "David S. Miller" <davem@redhat.com>
To: Thomas Zehetbauer <thomasz@hostmaster.org>
Cc: linux-kernel@vger.kernel.org, netfilter-devel@lists.netfilter.org
Subject: Re: netfilter IPv6 support
Date: Thu, 26 Aug 2004 13:00:24 -0700 [thread overview]
Message-ID: <20040826130024.6ff83dff.davem@redhat.com> (raw)
In-Reply-To: <1093546367.3497.23.camel@hostmaster.org>
On Thu, 26 Aug 2004 20:52:47 +0200
Thomas Zehetbauer <thomasz@hostmaster.org> wrote:
> Although linux was one of the first to support IPv6 it seems to me that
> netfilter support has almost stuck. There is still not even a REJECT
> target not to mention stateful filtering for IPv6.
Why not ask the netfilter development lists such questions?
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.
next prev parent reply other threads:[~2004-08-26 20:00 UTC|newest]
Thread overview: 11+ 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 [this message]
2004-08-26 20:00 ` David S. Miller
2004-08-26 21:25 ` Thomas Zehetbauer
2004-08-26 22:05 ` Willy Tarreau
2004-08-26 22:05 ` Willy Tarreau
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=20040826130024.6ff83dff.davem@redhat.com \
--to=davem@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.