From: ebiederm@xmission.com (Eric W. Biederman)
To: Rick Jones <rick.jones2@hp.com>
Cc: David Miller <davem@davemloft.net>,
jeff@garzik.org, netdev@vger.kernel.org,
Patrick McHardy <kaber@trash.net>
Subject: Re: on the topic of alternate MAC addresses
Date: Thu, 25 Oct 2007 11:36:53 -0600 [thread overview]
Message-ID: <m13avz5c5m.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <4720CEE2.1010007@hp.com> (Rick Jones's message of "Thu, 25 Oct 2007 10:14:10 -0700")
Rick Jones <rick.jones2@hp.com> writes:
> Eric W. Biederman wrote:
>> Duplicate mac addresses across interfaces on the same machine
>> should generally be a don't care. Although there may some
>> cases we don't mind.
>
> What might the switches think of that? Outside of the context of a
> link-aggregate I would think that could do some unhappy things when multiple
> interfaces are connected to the same broadcast domain.
>
> That the "all interfaces have one MAC" default behaviour on SPARC systems often
> ran into troubles is probably cautionary here.
Sure we don't want to duplicate mac addresses globally by default.
The case that is always wrong is duplicate mac addresses going
in and out the same interface, and skimming through the code
it looks like we already have the data structures necessary to
prevent duplicate use of unicast mac addresses already.
Eric
prev parent reply other threads:[~2007-10-25 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 1:05 on the topic of alternate MAC addresses David Miller
2007-10-24 2:25 ` Jeff Garzik
2007-10-24 2:30 ` Jeff Garzik
2007-10-24 3:22 ` David Miller
2007-10-24 9:28 ` Johannes Berg
2007-10-25 16:14 ` Eric W. Biederman
2007-10-25 17:14 ` Rick Jones
2007-10-25 17:36 ` Eric W. Biederman [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=m13avz5c5m.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
/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).