netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: xemul@openvz.org
Cc: shemminger@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: Bridge: request for the via_phys_dev feature discussion
Date: Fri, 26 Feb 2010 04:30:28 -0800 (PST)	[thread overview]
Message-ID: <20100226.043028.245172342.davem@davemloft.net> (raw)
In-Reply-To: <4B7D30B8.2050400@openvz.org>

From: Pavel Emelyanov <xemul@openvz.org>
Date: Thu, 18 Feb 2010 15:21:12 +0300

> 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.

Stephen, please work with Pavel on finding a solution for this issue
that works for you.

Thanks.

      reply	other threads:[~2010-02-26 12:30 UTC|newest]

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

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=20100226.043028.245172342.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.org \
    --cc=xemul@openvz.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).