From: Roopa Prabhu <roopa@cumulusnetworks.com>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: 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: Sun, 29 Jan 2017 18:20:24 -0800 [thread overview]
Message-ID: <588EA2E8.2040302@cumulusnetworks.com> (raw)
In-Reply-To: <71e661bd-e26d-2629-06bb-888f6a09b06d@cumulusnetworks.com>
On 1/29/17, 5:29 PM, David Ahern wrote:
[snip]
> Let's give an example for each case:
>
> 1. Add - full multipath route
>
> This route command:
> ip -6 ro add vrf red 2001:db8:200::/120 nexthop via 2001:db8:1::2 nexthop via 2001:db8:2::2
>
> generates this notification (ip -t mon ro):
>
> 2001:db8:200::/120 table red metric 1024
> nexthop via 2001:db8:1::2 dev eth1 weight 1
> nexthop via 2001:db8:2::2 dev eth2 weight 1
>
ack,
> 2. Delete - 1 notification for each hop for all combinations of delete commands
here I was trying to say, for people deleting the full multipath route, you should send a RTA_MULTIPATH.
For the odd case of ipv6 single nexthop delete, you can continue to send a single nexthop delete (like today ..without RTA_MULTIPATH)
because there is no other way to notify a single nexthop delete with a RTM_DELROUTE.
The reason I say this is because: keeping future in mind, this will make things consistent for majority of people who will
start using RTA_MULTIPATH for both ipv4 and ipv6 for adds and deletes (requests/notifications and dumps) the same way.
single next hop delete will just be around because of fear of breaking existing applications.
>
>
> 3. Replace - full multipath route
>
> This route command (with the one from Add case already in place):
> ip -6 ro replace vrf red 2001:db8:200::/120 nexthop via 2001:db8:1::16 nexthop via 2001:db8:2::16
>
> generates a single notification:
>
> Replaced 2001:db8:200::/120 table red metric 1024
> nexthop via 2001:db8:1::16 dev eth1 weight 1
> nexthop via 2001:db8:2::16 dev eth2 weight 1
ack,
>
> 4. Append - 1 route after all hops are appended
>
> This append command (starting with the one installed from the Replace case):
> ip -6 ro append vrf red 2001:db8:200::/120 nexthop via 2001:db8:2::20 nexthop via 2001:db8:1::20
>
> generates a single notification:
>
> Append 2001:db8:200::/120 table red metric 1024
> nexthop via 2001:db8:2::20 dev eth2 weight 1
> nexthop via 2001:db8:1::20 dev eth1 weight 1
> nexthop via 2001:db8:1::16 dev eth1 weight 1
> nexthop via 2001:db8:2::16 dev eth2 weight 1
>
> (The Replaced and Append annotations are due to a local iproute2 patch; iproute2 does
> not currently distinguish NEWROUTE cases.)
>
ack,
thanks
next prev parent reply other threads:[~2017-01-30 2:20 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 [this message]
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
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=588EA2E8.2040302@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.