public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta•com>
To: sclark46@earthlink•net
Cc: Linux Kernel Network Developers <netdev@vger•kernel.org>
Subject: Re: Bridging broken/unfriendly
Date: Wed, 28 Sep 2011 08:30:21 -0700	[thread overview]
Message-ID: <20110928083021.2edf43a6@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <4E7E5976.1070200@earthlink.net>

On Sat, 24 Sep 2011 18:28:06 -0400
Stephen Clark <sclark46@earthlink•net> wrote:

> Hi,
> 
> Is there some reason Linux bridging won't let the ip address be on
> one of the interfaces, like FreeBSD does, instead of the bridge device?
> 
> This makes it very difficult or impossible to remotely add the interface
> you are remoted in on to a bridge, or is there some sneaky way to
> do this without losing your connection?
> 

I would like to see a clean solution to setting up a bridge.
There was a patch that was never completed to allow migrating a ethernet
interface into a bridge. It is possible to do it with a script, by
dumping routes with ip command and replaying that into the bridge.
To really do it right (including neighbor table and iptables rules)
would be complex, especially considering the error cases.

Having looked at the FreeBSD code, that is not the answer. Trying to keep
a clean separation between IP and bridging is much better.

  parent reply	other threads:[~2011-09-28 15:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-24 22:28 Bridging broken/unfriendly Stephen Clark
2011-09-28 15:21 ` Michal Soltys
2011-09-28 15:30 ` Stephen Hemminger [this message]
2011-09-28 16:10   ` Stephen Clark

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=20110928083021.2edf43a6@nehalam.linuxnetplumber.net \
    --to=shemminger@vyatta$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=sclark46@earthlink$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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