netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@openvz.org>
To: Stephen Hemminger <shemminger@linux-foundation.org>,
	Linux Netdev List <netdev@vger.kernel.org>
Subject: Bridge: request for the via_phys_dev feature discussion
Date: Thu, 18 Feb 2010 15:21:12 +0300	[thread overview]
Message-ID: <4B7D30B8.2050400@openvz.org> (raw)

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

             reply	other threads:[~2010-02-18 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 12:21 Pavel Emelyanov [this message]
2010-02-26 12:30 ` Bridge: request for the via_phys_dev feature discussion David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B7D30B8.2050400@openvz.org \
    --to=xemul@openvz.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).