From: "Julius Volz" <juliusv@google.com>
To: netdev@vger.kernel.org, lvs-devel@vger.kernel.org
Cc: horms@verge.net.au, kaber@trash.net, vbusam@google.com
Subject: Re: [PATCHv3 00/24] Add first IPv6 support to IPVS
Date: Tue, 2 Sep 2008 15:54:00 +0200 [thread overview]
Message-ID: <f4845fc0809020654x6af2a5bdk5dc646b009bbd7c@mail.gmail.com> (raw)
In-Reply-To: <1220363423-8618-1-git-send-email-juliusv@google.com>
Sorry, please ignore the bogus patches in response to this email. I
was in the wrong directory when using git-send-email with *.patch :(
Real patches in next post in a second.
On Tue, Sep 2, 2008 at 3:50 PM, Julius Volz <juliusv@google.com> wrote:
> Hi Horms,
>
> Here comes the whole batch again! I've fixed almost all style issues
> reported by checkpatch.pl, except for some little things which look like
> they could stay like they are for now (down to 3 warnings and 2 errors).
> I also integrated your other comments and removed the patch that
> adds the changelog information (not needed anymore, according to
> Stephen).
>
> These patches are based lvs-2.6:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/horms/lvs-2.6.git
>
> - Full kernel patch in one file:
> http://www-user.tu-chemnitz.de/~volz/ipvs_ipv6/ipvs_ipv6_v3.patch
>
> While not all IPv6 features are working or tested, existing IPv4 features
> should still work as before. However, to use any of the new features, you
> will need a new ipvsadm with support for genetlink and IPv6:
>
> http://sixpak.org/vince/google/ipvsadm/
> (by Vince Busam)
>
> To enable IPv6 support in IPVS, set CONFIG_IP_VS_IPV6=y.
>
> Short overview:
>
> What works with IPv6:
> - forwarding mechanisms: NAT, DR, maybe Tunnel (not fully tested yet)
> - protocols: TCP, UDP, ESP, AH (last two not tested)
> - manipulation and inspection of both IPv4 and IPv6 entries with ipvsadm
> - 6 out of 10 schedulers
>
> What is not supported with IPv6:
> - handling fragmentation or other extension headers
> - FTP application helper (can be loaded, but only operates on v4)
> - sync daemon (can be started, but only operates on v4)
> - probably some incorrect handling of ICMPv6 or other corner cases
>
> Since fragmentation and extension headers should not occur very often,
> things should "mostly" work. I tested HTTP and DNS over NAT and DR
> with various supported schedulers without encountering any problems.
> But we didn't test any exotic situations. Also, there are some TODOs
> in the code for things that haven't been tested or implemented yet.
>
> Thanks for any comments!
>
> Julius
> --
> To unsubscribe from this list: send the line "unsubscribe lvs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Julius Volz - Corporate Operations - SysOps
Google Switzerland GmbH - Identification No.: CH-020.4.028.116-1
next prev parent reply other threads:[~2008-09-02 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 13:50 [PATCHv3 00/24] Add first IPv6 support to IPVS Julius Volz
2008-09-02 13:50 ` Julius Volz
2008-09-02 13:50 ` Julius Volz
2008-09-02 13:50 ` Julius Volz
2008-09-02 13:54 ` Julius Volz [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-02 13:55 Julius Volz
2008-09-03 0:40 ` Simon Horman
2008-09-03 9:03 ` Julius Volz
2008-09-05 1:25 ` Simon Horman
2008-09-05 11:05 ` Julius Volz
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=f4845fc0809020654x6af2a5bdk5dc646b009bbd7c@mail.gmail.com \
--to=juliusv@google.com \
--cc=horms@verge.net.au \
--cc=kaber@trash.net \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vbusam@google.com \
/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).