From: David Miller <davem@davemloft.net>
To: dsa@cumulusnetworks.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: ipv6/l3mdev: Move host route on saved address if necessary
Date: Tue, 01 Mar 2016 17:23:12 -0500 (EST) [thread overview]
Message-ID: <20160301.172312.1539246311423803200.davem@davemloft.net> (raw)
In-Reply-To: <1456595957-29477-1-git-send-email-dsa@cumulusnetworks.com>
From: David Ahern <dsa@cumulusnetworks.com>
Date: Sat, 27 Feb 2016 09:59:17 -0800
> Commit f1705ec197e70 allows IPv6 addresses to be retained on a link down.
> The address can have a cached host route which can point to the wrong
> FIB table if the L3 enslavement is changed (e.g., route can point to local
> table instead of VRF table if device is added to an L3 domain).
>
> On link up check the table of the cached host route against the FIB
> table associated with the device and correct if needed.
>
> Signed-off-by: David Ahern <dsa@cumulusnetworks.com>
Ugly... but applied, thanks.
next prev parent reply other threads:[~2016-03-01 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 17:59 [PATCH net-next] net: ipv6/l3mdev: Move host route on saved address if necessary David Ahern
2016-03-01 22:23 ` David Miller [this message]
2016-03-02 1:46 ` David Ahern
2016-03-03 22:11 ` David Miller
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=20160301.172312.1539246311423803200.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
/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).