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

[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