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] [thread-next>] [day] [month] [year] [list]
Message-ID: <f4845fc0803311129w4bdb0415p56c3f11c935c3020@mail.gmail.com>
Date:	Mon, 31 Mar 2008 20:29:30 +0200
From:	"Julius Volz" <juliusv@...gle.com>
To:	"Patrick McHardy" <kaber@...sh.net>
Cc:	netdev@...r.kernel.org, "Simon Horman" <horms@...ge.net.au>
Subject: Re: Adding IPv6 support to IPVS: some general questions about kernel development

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!

Thanks so much for helping!

Kind Regards,
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