From: Dmitry Mishin <dim@openvz.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@vger.kernel.org, bridge@osdl.org, devel@openvz.org
Subject: Bridge & it's MAC address question
Date: Mon, 30 Oct 2006 15:27:14 +0300 [thread overview]
Message-ID: <200610301527.15018.dim@openvz.org> (raw)
Hi,
Could somebody explain, why bridge uses minimal MAC of the attached devices?
It makes this address instable, variable during bridge life-cycle, which is
not good for DHCP. For example, I want to attach multiple virtual devices to
one physical. Then, I need to make sure that after each virtual device
addition, bridge addr is not changed and still addr of the physical device.
Why not to use MAC of the first attached device?
--
Thanks,
Dmitry.
next reply other threads:[~2006-10-30 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 12:27 Dmitry Mishin [this message]
2006-10-30 15:28 ` Bridge & it's MAC address question 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
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=200610301527.15018.dim@openvz.org \
--to=dim@openvz.org \
--cc=bridge@osdl.org \
--cc=devel@openvz.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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).