lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 1 Apr 2008 13:25:43 +0200
From:	"Julius Volz" <juliusv@...gle.com>
To:	"Simon Horman" <horms@...ge.net.au>
Cc:	"Patrick McHardy" <kaber@...sh.net>, netdev@...r.kernel.org
Subject: Re: Adding IPv6 support to IPVS: some general questions about kernel development

On Tue, Apr 1, 2008, Simon Horman wrote:
> On Mon, Mar 31, 2008 at 08:29:30PM +0200, Julius Volz wrote:
>  > On Mon, Mar 31, 2008, Patrick McHardy <kaber@...sh.net> wrote:
>  > >  net/ipvs or net/netfilter/ipvs sound fine. The second is probably
>  > >  better since at some point we should try to merge the duplicated
>  > >  conntrack functionality if possible.
>  >
>  > Sure, since IPVS is basically a netfilter extension, that sounds good
>  > to me. Could all the IPv4- and IPv6-specific functionality (as opposed
>  > to the commonly used code) also end up in there or would that still
>  > have to reside under ipv[4,6]/...?
>  >
>  > Does it seem wise to do this move as the first thing in this process?
>  > That would probably be a good starter exercise to get to know the
>  > whole process!
>
>  I think that sounds like an excellent idea. net/netfilter/ipvs sounds
>  fine to me, though think that IPVS is fairly loosely tied to nefilter,
>  so if it was only up to me I would go for net/ipvs.

Ok, I will do this soon then! I will go for net/netfilter/ipvs (I
don't really care though) unless anyone complains.

Julius

-- 
Google Switzerland GmbH
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ