From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 26 Feb 2010 10:49:46 -0800 From: Stephen Hemminger Message-ID: <20100226104946.4168e378@nehalam> In-Reply-To: <4B8815AE.1090909@candelatech.com> References: <20100226165104.GB5364@lenovo> <4B88076F.8030302@openvz.org> <20100226100102.0d52c6e9@nehalam> <20100226.100800.116618587.davem@davemloft.net> <20100226103003.097c39ec@nehalam> <4B8815AE.1090909@candelatech.com> 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: Ben Greear Cc: bridge@linux-foundation.org, netdev@vger.kernel.org, gorcunov@gmail.com, den@openvz.org, David Miller , xemul@openvz.org On Fri, 26 Feb 2010 10:40:46 -0800 Ben Greear wrote: > On 02/26/2010 10:30 AM, Stephen Hemminger wrote: > > 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? > > I use it..helps with using multiple interfaces on the same system, > especially when sending-to-self. > That is a special case which is not related to the discussion. We are talking about being able to setup a bridge and migrate the associated state from the ethernet device to the bridge.