Re: [PATCH net-next] net: vrf: Do not allow looback to be moved to a VRF

2017-04-27 Thread David Miller
From: David Ahern Date: Wed, 26 Apr 2017 07:58:22 -0700 > Moving the loopback into a VRF breaks networking for the default VRF. > Since the VRF device is the loopback for VRF domains, there is no > reason to move the loopback. Given the repercussions, block attempts >

Re: [PATCH net-next] net: vrf: Do not allow looback to be moved to a VRF

2017-04-26 Thread Greg Rose
On Wed, 2017-04-26 at 07:58 -0700, David Ahern wrote: > Moving the loopback into a VRF breaks networking for the default VRF. > Since the VRF device is the loopback for VRF domains, there is no > reason to move the loopback. Given the repercussions, block attempts > to set lo into a VRF. > >

[PATCH net-next] net: vrf: Do not allow looback to be moved to a VRF

2017-04-26 Thread David Ahern
Moving the loopback into a VRF breaks networking for the default VRF. Since the VRF device is the loopback for VRF domains, there is no reason to move the loopback. Given the repercussions, block attempts to set lo into a VRF. Signed-off-by: David Ahern ---