From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 26 Feb 2010 21:55:06 +0300 From: Cyrill Gorcunov Message-ID: <20100226185506.GB13393@lenovo> References: <20100226165104.GB5364@lenovo> <4B88076F.8030302@openvz.org> <20100226100102.0d52c6e9@nehalam> <20100226.100800.116618587.davem@davemloft.net> <20100226103003.097c39ec@nehalam> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100226103003.097c39ec@nehalam> 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: Stephen Hemminger Cc: den@openvz.org, netdev@vger.kernel.org, bridge@linux-foundation.org, David Miller , xemul@openvz.org On Fri, Feb 26, 2010 at 10:30:03AM -0800, 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? > Seems g500i uses it http://goo.gl/5lIi (function open_tcp_socket), which is either router firmware or kind of modile device. But frankly -- this seems to be unrelated to a bridge. -- Cyrill