Re: l3mdev: Support for sockets bound to enslaved device

2017-08-08 Thread David Ahern
On 8/8/17 5:29 AM, Ondrej Zajicek wrote: > Hi > > We noticed that TCP outgoing sockets that are bound to enslaved devices > by SO_BINDTODEVICE fail to connect, while they work when bound to vrf > device instead. We noticed similar behavior on ICMP (i.e. ping -I vrf0 > worked, while ping -I eth0 do

Re: l3mdev: Support for sockets bound to enslaved device

2017-08-08 Thread Ondrej Zajicek
Hi We noticed that TCP outgoing sockets that are bound to enslaved devices by SO_BINDTODEVICE fail to connect, while they work when bound to vrf device instead. We noticed similar behavior on ICMP (i.e. ping -I vrf0 worked, while ping -I eth0 does not if eth0 is enslaved to vrf0). On the contrary,

Re: [PATCH v3 net-next 0/7] net: l3mdev: Support for sockets bound to enslaved device

2017-08-07 Thread David Ahern
On 8/7/17 12:39 PM, David Miller wrote: > Series applied, let's see if it builds this time :-) I did an allyesconfig build before sending just to make sure, so our mileage better not vary.

Re: [PATCH v3 net-next 0/7] net: l3mdev: Support for sockets bound to enslaved device

2017-08-07 Thread David Miller
From: David Ahern Date: Mon, 7 Aug 2017 08:44:15 -0700 > A missing piece to the VRF puzzle is the ability to bind sockets to > devices enslaved to a VRF. This patch set adds the enslaved device > index, sdif, to IPv4 and IPv6 socket lookups. The end result for users > is the following scope opti

[PATCH v3 net-next 0/7] net: l3mdev: Support for sockets bound to enslaved device

2017-08-07 Thread David Ahern
A missing piece to the VRF puzzle is the ability to bind sockets to devices enslaved to a VRF. This patch set adds the enslaved device index, sdif, to IPv4 and IPv6 socket lookups. The end result for users is the following scope options for services: 1. "global" services - sockets not bound to any

Re: [PATCH v2 net-next 0/7] net: l3mdev: Support for sockets bound to enslaved device

2017-08-07 Thread David Ahern
On 8/7/17 12:51 AM, David Miller wrote: > David, I had to revert. You didn't convert dccp which breaks > the build. > > net/dccp/ipv4.c: In function ‘dccp_v4_err’: > net/dccp/ipv4.c:256:7: error: too few arguments to function > ‘__inet_lookup_established’ > sk = __inet_lookup_established(net,

Re: [PATCH v2 net-next 0/7] net: l3mdev: Support for sockets bound to enslaved device

2017-08-06 Thread David Miller
From: David Miller Date: Sun, 06 Aug 2017 21:39:38 -0700 (PDT) > From: David Ahern > Date: Fri, 4 Aug 2017 13:16:56 -0700 > >> A missing piece to the VRF puzzle is the ability to bind sockets to >> devices enslaved to a VRF. This patch set adds the enslaved device >> index, sdif, to IPv4 and I

Re: [PATCH v2 net-next 0/7] net: l3mdev: Support for sockets bound to enslaved device

2017-08-06 Thread David Miller
From: David Ahern Date: Fri, 4 Aug 2017 13:16:56 -0700 > A missing piece to the VRF puzzle is the ability to bind sockets to > devices enslaved to a VRF. This patch set adds the enslaved device > index, sdif, to IPv4 and IPv6 socket lookups. The end result for users > is the following scope opti

Re: [PATCH net-next 00/10] net: l3mdev: Support for sockets bound to enslaved device

2017-08-04 Thread David Ahern
On 8/1/17 6:41 PM, David Miller wrote: > From: David Ahern > Date: Mon, 31 Jul 2017 20:13:16 -0700 > >> Existing code for socket lookups already pass in 6+ arguments. Rather >> than add another for the enslaved device index, the existing lookups >> are converted to use a new sk_lookup struct. Fro

[PATCH v2 net-next 0/7] net: l3mdev: Support for sockets bound to enslaved device

2017-08-04 Thread David Ahern
A missing piece to the VRF puzzle is the ability to bind sockets to devices enslaved to a VRF. This patch set adds the enslaved device index, sdif, to IPv4 and IPv6 socket lookups. The end result for users is the following scope options for services: 1. "global" services - sockets not bound to any

Re: [PATCH net-next 00/10] net: l3mdev: Support for sockets bound to enslaved device

2017-08-01 Thread David Miller
From: David Ahern Date: Mon, 31 Jul 2017 20:13:16 -0700 > Existing code for socket lookups already pass in 6+ arguments. Rather > than add another for the enslaved device index, the existing lookups > are converted to use a new sk_lookup struct. From there, the enslaved > device index becomes ano

Re: [PATCH net-next 00/10] net: l3mdev: Support for sockets bound to enslaved device

2017-08-01 Thread David Ahern
On 8/1/17 8:15 AM, David Laight wrote: > From: David Ahern >> Sent: 01 August 2017 04:13 > ... >> Existing code for socket lookups already pass in 6+ arguments. Rather >> than add another for the enslaved device index, the existing lookups >> are converted to use a new sk_lookup struct. From there,

RE: [PATCH net-next 00/10] net: l3mdev: Support for sockets bound to enslaved device

2017-08-01 Thread David Laight
From: David Ahern > Sent: 01 August 2017 04:13 ... > Existing code for socket lookups already pass in 6+ arguments. Rather > than add another for the enslaved device index, the existing lookups > are converted to use a new sk_lookup struct. From there, the enslaved > device index becomes another el

[PATCH net-next 00/10] net: l3mdev: Support for sockets bound to enslaved device

2017-07-31 Thread David Ahern
A missing piece to the VRF puzzle is the ability to bind sockets to devices enslaved to a VRF. This patch set adds the enslaved device index, sdif, to IPv4 and IPv6 socket lookups. The end result for users is the following scope options for services: 1. "global" services - sockets not bound to any

[RFC PATCH 00/10] net: l3mdev: Support for sockets bound to enslaved device

2017-07-25 Thread David Ahern
A missing piece to the VRF puzzle is the ability to bind sockets to devices enslaved to a VRF. This patch set adds the enslaved device index, sdif, to IPv4 and IPv6 socket lookups. The end result for users is the following scope options for services: 1. "global" services - sockets not bound to any