From: Marian Jancar <m.jancar@satca.net>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] MAC addresses on ports
Date: Wed, 16 Jan 2008 15:09:48 +0100 [thread overview]
Message-ID: <478E102C.8050006@satca.net> (raw)
Hi,
I need some explanation/help with a probably bit uncommon bridge setup. I have
devices that come with their manufacturer MAC addresses, and I need to create
a bridge that uses my MAC address instead and has to look about like this:
br0: unique MAC address from my range
wlan0: same MAC as br0
(madwifi supports 4 MAC frames in STA mode so the actual bridging works,
just if you are curious :p)
eth0: any MAC address higher than the br0 MAC,
and as long as the assumptions below hold, unique in just this bridge,
eth1: ditto
...
ethN: ditto
Now, the only reason I can think about from my naive point of view, why the bridge
cares about port MAC address at all, is maintaining a reliable and persistent
connection between the logical port and the actual physical device for STP
purposes.
So if I'm right, I can assign any MAC addresses to the ethernet ports, as long
as they are higher than the wlan0 address, to ensure that the bridge selects
the wlan0 MAC as its own, and as long as they are locally unique.
The MAC addresses of the ethernet ports will not appear in any non-STP
packets and don't have to be globally unique, because they identify ports in
just this bridge and STP handles that, just a port has always to have the
same address and not a random one.
Is this correct? If not, is there any other way to create a bridge and
not to have to allocate a unique MAC to each port?
Any comments and/or pointers to relevant documentation are highly appreciated.
Best Regards
Marian
next reply other threads:[~2008-01-16 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 14:09 Marian Jancar [this message]
2008-01-16 18:31 ` [Bridge] MAC addresses on ports Stephen Hemminger
2008-01-22 5:58 ` richardvoigt
2008-01-22 9:19 ` [Bridge] " Marian Jancar
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=478E102C.8050006@satca.net \
--to=m.jancar@satca.net \
--cc=bridge@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.