From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 26 Feb 2010 11:01:15 -0800 (PST) Message-Id: <20100226.110115.229233177.davem@davemloft.net> From: David Miller In-Reply-To: <20100226103003.097c39ec@nehalam> References: <20100226100102.0d52c6e9@nehalam> <20100226.100800.116618587.davem@davemloft.net> <20100226103003.097c39ec@nehalam> 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: shemminger@linux-foundation.org Cc: gorcunov@gmail.com, netdev@vger.kernel.org, bridge@linux-foundation.org, den@openvz.org, xemul@openvz.org From: Stephen Hemminger Date: Fri, 26 Feb 2010 10:30:03 -0800 > 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? Any application that would like to, it's been supported from day one. In fact I bet there are more TCP applications that support SO_BINDTODEVICE than UDP ones.