From: Stephen Hemminger <stephen@networkplumber.org>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: Roopa Prabhu <roopa@cumulusnetworks.com>,
netdev@vger.kernel.org, nicolas.dichtel@6wind.com
Subject: Re: [PATCH net-next v3 0/4] net: ipv6: Improve user experience with multipath routes
Date: Mon, 30 Jan 2017 15:56:30 -0800 [thread overview]
Message-ID: <20170130155630.787daf0a@xeon-e3> (raw)
In-Reply-To: <7a363b93-bf14-9a13-d154-42a26ac06a06@cumulusnetworks.com>
On Mon, 30 Jan 2017 16:53:44 -0700
David Ahern <dsa@cumulusnetworks.com> wrote:
> On 1/30/17 2:16 PM, Stephen Hemminger wrote:
> > My fear is that routing daemons already adapt to the funny semantics of multi-path routing in IPv4 vs IPv6
> > and therefore any change in semantics or flags risks breaking existing user space.
>
> That is a possibility, but so far the 2 open source code bases I know of have problems with IPv6 mpath.
Breaking closed source is not acceptable either.
>
> As I mentioned quagga does not work with IPv6 multipath as is today.
>
> I just looked at bird. IPv6 mpath support was added in Sept. 2016. It specifically hard codes not accepting RTA_MULTIPATH for IPv6 which I think is an odd choice and clearly coding to quirks as opposed to rtnetlink design. Having never looked at bird code I was able to get it working in < 1 hour. I will contact the patch author about that limitation. That said, the bird implementation needs work when you look at the add/delete/replace/append permutations, so the current code has its problems as well.
Also what if quagga was fixed but had to work with existing enterprise distros?
next prev parent reply other threads:[~2017-01-30 23:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 23:20 [PATCH net-next v3 0/4] net: ipv6: Improve user experience with multipath routes David Ahern
2017-01-27 23:20 ` [PATCH net-next v3 1/4] net: ipv6: add NLM_F_APPEND in notifications when applicable David Ahern
2017-01-27 23:20 ` [PATCH net-next v3 2/4] net: ipv6: Allow shorthand delete of all nexthops in multipath route David Ahern
2017-01-27 23:20 ` [PATCH net-next v3 3/4] net: ipv6: Add support to dump multipath routes via RTA_MULTIPATH attribute David Ahern
2017-01-27 23:20 ` [PATCH net-next v3 4/4] net: ipv6: Use compressed IPv6 addresses showing route replace error David Ahern
2017-01-29 1:00 ` [PATCH net-next v3 0/4] net: ipv6: Improve user experience with multipath routes Roopa Prabhu
2017-01-29 18:02 ` David Ahern
2017-01-29 23:55 ` Roopa Prabhu
2017-01-30 1:29 ` David Ahern
2017-01-30 2:20 ` Roopa Prabhu
2017-01-30 2:57 ` David Ahern
2017-01-30 11:13 ` Nicolas Dichtel
2017-01-30 15:59 ` David Ahern
2017-01-30 15:49 ` Roopa Prabhu
2017-01-30 16:12 ` David Ahern
2017-01-30 18:45 ` Roopa Prabhu
2017-01-30 21:16 ` Stephen Hemminger
2017-01-30 23:53 ` David Ahern
2017-01-30 23:56 ` Stephen Hemminger [this message]
2017-01-31 0:02 ` David Ahern
2017-01-30 11:08 ` Nicolas Dichtel
2017-01-30 15:45 ` Roopa Prabhu
2017-01-30 16:41 ` Nicolas Dichtel
2017-01-30 11:07 ` Nicolas Dichtel
2017-01-30 15:23 ` David Ahern
2017-01-30 17:03 ` Nicolas Dichtel
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=20170130155630.787daf0a@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=roopa@cumulusnetworks.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).