netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "richardvoigt@gmail.com" <richardvoigt@gmail.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
	netdev@vger.kernel.org, bridge@linux-foundation.org
Subject: Re: [Bridge] [RFC 0/5] bridge - introduce via_phys_dev feature
Date: Fri, 26 Feb 2010 10:52:52 -0600	[thread overview]
Message-ID: <2e59e6971002260852m79d9c79t5293b3b8c7575d46@mail.gmail.com> (raw)
In-Reply-To: <20100226081843.07f37742@nehalam>

On Fri, Feb 26, 2010 at 10:18 AM, Stephen Hemminger
<shemminger@linux-foundation.org> wrote:
> Looking back at this. What if the API was simpler:
>
> Instead of:
>> Typical session looks like
>>
>> | s...@10.10.0.160$ brctl addbr br0
>> | s...@10.10.0.160$ ifconfig br0 up
>> | s...@10.10.0.160$ echo 1 > /sys/class/net/bridge/br0/via_phys_dev
>> | s...@10.10.0.160$ brctl addif br0 eth0
>> | (...waiting a bit...)
>> | s...@10.10.0.160$
>
> Why not:
>  1. Setup bridge (and any other interfaces except eth0); includes bringing br0 up
>  2. Add eth0 to bridge with new flag to inherit
>       a. brctl addif br0 eth0 inherit
>
> Inherit functionality would need to move address (Ether, IP, IPv6)
> and routes from eth0 to br0.
> I will see about doing it as much as possible in userspace.

How about inheriting the up/down status as well, this way the bridge
can be left down until the settings are inherited, and will come up
with the inherited MAC address, IP address, and routing table instead
of changing while live?

> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
>

  parent reply	other threads:[~2010-02-26 16:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 11:46 [RFC 0/5] bridge - introduce via_phys_dev feature Cyrill Gorcunov
2009-05-11 11:46 ` [RFC 1/5] net: bridge - use is_multicast_ether_addr helper Cyrill Gorcunov
2009-05-19 22:18   ` Stephen Hemminger
2009-05-11 11:46 ` [RFC 2/5] net: bridge - add managing of BRCTL_SET_VIA_PHYS_DEV and BRCTL_SET_MASTER_DEV Cyrill Gorcunov
2009-05-11 11:46 ` [RFC 3/5] net: sk_buff - introduce br_seen field to mark skb issued by a bridge Cyrill Gorcunov
2009-05-11 11:46 ` [RFC 4/5] net: dev.c - introduce br_hard_xmit_hook Cyrill Gorcunov
2009-05-11 11:46 ` [RFC 5/5] net: bridge - handle via_phys_dev feature on a bridge level Cyrill Gorcunov
2009-05-11 13:01   ` Cyrill Gorcunov
2009-05-12  5:30 ` [Bridge] [RFC 0/5] bridge - introduce via_phys_dev feature Daniel Robbins
2009-05-12  6:19   ` Cyrill Gorcunov
2009-05-12  7:02     ` Daniel Robbins
2009-05-12 16:24       ` Cyrill Gorcunov
2009-05-12 17:07         ` Daniel Robbins
2009-05-12 17:21           ` Cyrill Gorcunov
2009-05-19 22:21 ` Stephen Hemminger
     [not found]   ` <20090520192726.GF4968@lenovo>
     [not found]     ` <20090520131225.03b7715a@nehalam>
     [not found]       ` <20090521180805.GC4932@lenovo>
     [not found]         ` <20090521140504.1865883b@nehalam>
     [not found]           ` <20090522201850.GF5354@lenovo>
2010-02-26 16:18             ` Stephen Hemminger
2010-02-26 16:51               ` Cyrill Gorcunov
2010-02-26 17:39                 ` Pavel Emelyanov
2010-02-26 18:01                   ` Stephen Hemminger
2010-02-26 18:08                     ` David Miller
2010-02-26 18:30                       ` Stephen Hemminger
2010-02-26 18:40                         ` Ben Greear
2010-02-26 18:49                           ` Stephen Hemminger
2010-02-26 21:16                             ` Pavel Emelyanov
2010-02-26 18:55                         ` Cyrill Gorcunov
2010-02-26 19:01                         ` David Miller
2010-02-26 16:52               ` richardvoigt [this message]
2010-02-26 17:25                 ` [Bridge] " Stephen Hemminger

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=2e59e6971002260852m79d9c79t5293b3b8c7575d46@mail.gmail.com \
    --to=richardvoigt@gmail.com \
    --cc=bridge@linux-foundation.org \
    --cc=gorcunov@gmail.com \
    --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).