netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sven Köhler" <skoehler@upb.de>
To: bridge@osdl.org
Cc: netdev@vger.kernel.org
Subject: Re: Bridge & it's MAC address question
Date: Mon, 09 Apr 2007 20:30:12 +0200	[thread overview]
Message-ID: <eve0nv$ang$1@sea.gmane.org> (raw)
In-Reply-To: <20061215160429.GC12679@xi.wantstofly.org>


[-- Attachment #1.1: Type: text/plain, Size: 884 bytes --]

>>>> The bridge physical address is the minimum of all the attached devices.
>>>> This is done because the STP standard requires it.  You can reset it
>>>> to be the same as any of the attached devices. This will not cause a
>>>> problem unless using STP.
>>> You can in fact use any MAC address.  The STP standard recommends using
>>> the minimum address, as that is deterministic, and so it doesn't depend
>>> on the order in which you enslave subdevices.
>> So should restriction be lifted?
> 
> We should definitely allow users to override the MAC address of a
> bridge interface.

Yes, i would love to have that feature.

I'm using a bridge for a Xen host machine. Interfaces of the Xen guests
are dynamically added to and removed from the bridge. At the moment, i
create and add a tun interface to the bridge, so the bridge has a valid
mac address at all.



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

[-- Attachment #2: Type: text/plain, Size: 165 bytes --]

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

      reply	other threads:[~2007-04-09 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30 12:27 Bridge & it's MAC address question Dmitry Mishin
2006-10-30 15:28 ` Stephen Hemminger
2006-12-15 13:19   ` Lennert Buytenhek
2006-12-15 15:52     ` [Bridge] " Stephen Hemminger
2006-12-15 16:04       ` Lennert Buytenhek
2007-04-09 18:30         ` Sven Köhler [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='eve0nv$ang$1@sea.gmane.org' \
    --to=skoehler@upb.de \
    --cc=bridge@osdl.org \
    --cc=netdev@vger.kernel.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).