All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsa@cumulusnetworks.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: ipv6/l3mdev: Move host route on saved address if necessary
Date: Tue, 1 Mar 2016 17:46:46 -0800	[thread overview]
Message-ID: <56D64606.7040202@cumulusnetworks.com> (raw)
In-Reply-To: <20160301.172312.1539246311423803200.davem@davemloft.net>

On 3/1/16 2:23 PM, David Miller wrote:
> 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.
>

This is an example of what I meant by complications with the suggestion 
of stashing the prefix route. Would you prefer the host route always get 
freed on a down and re-created on an up?

  reply	other threads:[~2016-03-02  1:46 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
2016-03-02  1:46   ` David Ahern [this message]
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=56D64606.7040202@cumulusnetworks.com \
    --to=dsa@cumulusnetworks.com \
    --cc=davem@davemloft.net \
    --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 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.