From: Stephen Clark <sclark46@earthlink•net>
To: Stephen Hemminger <shemminger@vyatta•com>
Cc: Linux Kernel Network Developers <netdev@vger•kernel.org>
Subject: Re: Bridging broken/unfriendly
Date: Wed, 28 Sep 2011 12:10:37 -0400 [thread overview]
Message-ID: <4E8346FD.9000306@earthlink.net> (raw)
In-Reply-To: <20110928083021.2edf43a6@nehalam.linuxnetplumber.net>
On 09/28/2011 11:30 AM, Stephen Hemminger wrote:
> 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.
>
>
Hi Stephen,
Thanks for taking the time to reply. I had pretty much decided I would
have to do some kind
of script that would do everything at once, instead of trying to do the
commands one at a
time from the console.
Regards,
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
prev parent reply other threads:[~2011-09-28 16:10 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
2011-09-28 16:10 ` Stephen Clark [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=4E8346FD.9000306@earthlink.net \
--to=sclark46@earthlink$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shemminger@vyatta$(echo .)com \
/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