Re: [RFC PATCH net-next 04/19] ipv6: Prepare to handle multiple netdev events

2018-01-02 Thread Ido Schimmel
On Tue, Jan 02, 2018 at 09:29:42AM -0700, David Ahern wrote: > On 12/31/17 9:14 AM, Ido Schimmel wrote: > > To make IPv6 more in line with IPv4 we need to be able to respond > > differently to different netdev events. For example, when a netdev is > > unregistered all the routes using it as their n

Re: [RFC PATCH net-next 04/19] ipv6: Prepare to handle multiple netdev events

2018-01-02 Thread David Ahern
On 12/31/17 9:14 AM, Ido Schimmel wrote: > To make IPv6 more in line with IPv4 we need to be able to respond > differently to different netdev events. For example, when a netdev is > unregistered all the routes using it as their nexthop device should be > flushed, whereas when the netdev's carrier

[RFC PATCH net-next 04/19] ipv6: Prepare to handle multiple netdev events

2017-12-31 Thread Ido Schimmel
To make IPv6 more in line with IPv4 we need to be able to respond differently to different netdev events. For example, when a netdev is unregistered all the routes using it as their nexthop device should be flushed, whereas when the netdev's carrier changes only the 'linkdown' flag should be toggle