From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Darren Willis <djw@google.com>
Cc: Jan Engelhardt <jengelh@medozas.de>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH] DHCPv6 connection tracker helper
Date: Sat, 3 Mar 2012 14:35:10 +0100 [thread overview]
Message-ID: <20120303133510.GB18802@1984> (raw)
In-Reply-To: <CAFntDkzLUzL3S6BBhYXMy67gNyCi-xEAUg=eEkaS0WsAgdaz6Q@mail.gmail.com>
On Fri, Mar 02, 2012 at 12:59:15PM +0900, Darren Willis wrote:
> On Wed, Feb 29, 2012 at 08:54, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > Yes. I'd like to send a patch for RFC to the mailing list any time
> > soon. I'll include you in the CC.
>
> Thanks, sounds interesting.
>
> > I'm currently working on one user-space helper infrastructure. We can
> > use that infrastructure to implement this helper and many others.
> >
> > I've got the patch in one branch of my kernel tree, it's still
> > experimental stuff, but I expect to have it done soon.
> >
> > Would you be OK with we make this (and other helpers that will surely
> > follow up) in user-space?
>
> Well, I think long-term that's the way to go. I'd still like to get
> this in its current form, if possible, since it's a simple thing in a
> pretty OK state right now, so it could be ready to go quite quickly.
> Whereas, although I think your helper framework sounds great and is
> the right thing to do, it's also an unknown amount of time away.
> Unless it's going to be landing in the next few weeks?
If we apply this, we'll have to live with it for long time until we
can remove. It's easy to get something it, but not evident to get it
out because somebody will be using it.
> Of course, I don't want to make a lot of work for you - I'll be more
> than happy to revisit this, remove the dhcpv6 helper and re-implement
> it for your new helper framework when it's ready for external
> contributions.
One firewall vendor is supporting the development of this helper
user-space infrastructure, so we'll have the infrastructure soon (by
next kernel release cycle).
Please, ping me in three months or so if you see no advances in this
regard.
prev parent reply other threads:[~2012-03-03 13:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 2:30 [PATCH] DHCPv6 connection tracker helper Darren Willis
2012-02-10 11:18 ` Pablo Neira Ayuso
2012-02-13 4:07 ` Darren Willis
2012-02-13 23:05 ` Pablo Neira Ayuso
2012-02-13 9:55 ` Jan Engelhardt
2012-02-14 0:46 ` Pablo Neira Ayuso
2012-02-15 9:00 ` Darren Willis
2012-02-15 17:13 ` Jan Engelhardt
2012-02-16 4:56 ` Darren Willis
2012-02-24 17:54 ` Pablo Neira Ayuso
2012-02-27 4:18 ` Darren Willis
2012-02-28 23:54 ` Pablo Neira Ayuso
2012-03-02 3:59 ` Darren Willis
2012-03-03 13:35 ` Pablo Neira Ayuso [this message]
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=20120303133510.GB18802@1984 \
--to=pablo@netfilter.org \
--cc=djw@google.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).