netdev - Bridge: request for the via_phys

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B7D30B8.2050400@openvz.org>
Date:	Thu, 18 Feb 2010 15:21:12 +0300
From:	Pavel Emelyanov <xemul@...nvz.org>
To:	Stephen Hemminger <shemminger@...ux-foundation.org>,
	Linux Netdev List <netdev@...r.kernel.org>
Subject: Bridge: request for the via_phys_dev feature discussion

Hi, Stephen.

Some time ago Cyrill Corcunov sent a patches, that added to bridges the 
ability to send/receive packets via ethernet device in it rather than via 
the bridge device itself. Here's the link on the thread:
http://www.mail-archive.com/bridge@lists.linux-foundation.org/msg01108.html

That time you told, that the problem we were trying to solve with the 
patches could be solved by other means. If you don't mind can we discus
this in more details?

In simple situation containers users want to bridge their containers through
veth device with the host eth0 adapter. But after one add his eth0 to bridge
he need to
a) reconfigure everything including IP addresses, routing tables and
   netfilter rules
b) recreate connections that were bound to eth0

That's OK if one setup the box from the scratch and adds eth0 to bridge from
the very beginning, but for those who start using containers on pre-configured
boxes or for those, who decided to switch to bridge+veth from some other 
virtual device (e.g. macvlan or venet device in OpenVZ) this becomes real pain.

I don't insist you accept the patches Cyrill proposed, I don't even insist
we rework them keeping the idea intact. I just want to know your opinion about
how to solve the above problem better.

Thanks,
Pavel
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html