Re: [PATCH net-next] net: ipv6/l3mdev: Move host route on saved address if necessary

2016-03-03 Thread David Miller
From: David Ahern Date: Tue, 1 Mar 2016 17:46:46 -0800 > Would you prefer the host route always get freed on a down and > re-created on an up? That would create yet another thing that can cause the re-up to fail :-/

Re: [PATCH net-next] net: ipv6/l3mdev: Move host route on saved address if necessary

2016-03-01 Thread David Ahern
On 3/1/16 2:23 PM, David Miller wrote: From: David Ahern 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

Re: [PATCH net-next] net: ipv6/l3mdev: Move host route on saved address if necessary

2016-03-01 Thread David Miller
From: David Ahern 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

[PATCH net-next] net: ipv6/l3mdev: Move host route on saved address if necessary

2016-02-27 Thread David Ahern
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 chec