From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 26 Feb 2010 10:30:03 -0800 From: Stephen Hemminger Message-ID: <20100226103003.097c39ec@nehalam> In-Reply-To: <20100226.100800.116618587.davem@davemloft.net> References: <20100226165104.GB5364@lenovo> <4B88076F.8030302@openvz.org> <20100226100102.0d52c6e9@nehalam> <20100226.100800.116618587.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Bridge] [RFC 0/5] bridge - introduce via_phys_dev feature List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Miller Cc: gorcunov@gmail.com, netdev@vger.kernel.org, bridge@linux-foundation.org, den@openvz.org, xemul@openvz.org On Fri, 26 Feb 2010 10:08:00 -0800 (PST) David Miller wrote: > From: Stephen Hemminger > Date: Fri, 26 Feb 2010 10:01:02 -0800 > > > TCP connections are never really bound to device. TCP routing is > > flexible; if packets can get through, it doesn't care. > > I think he might be talking about SO_BINDTODEVICE What application does that with TCP?