From: marty <marty@goodoldmarty.com>
To: linux-hotplug@vger.kernel.org
Subject: duplicate MAC addresses
Date: Sun, 23 Aug 2009 00:36:26 +0000 [thread overview]
Message-ID: <4A908F0A.5090100@goodoldmarty.com> (raw)
In-Reply-To: <4A8B0E98.6030202@goodoldmarty.com>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
Greg KH wrote:
> > On Tue, Aug 18, 2009 at 04:27:04PM -0400, marty wrote:
>> >> I got trouble...
>> >> (duplicate MAC addresses)
> >
> > That's a bug in your hardware, have you asked your manufacturer to
> > resolve this for you? That violates the ethernet spec...
I have resolved that problem as of today. I found this was caused
by the software I had been using. If a hardware issue remains, it is moot.
The bonding driver/utilities normally sets the bond address to the MAC of the
first NIC. But it also set the MAC of the slave (eth3) to the MAC of the first
NIC. This persists through reboots so that is how my MACs got duplicated.
Resetting the MAC corrected those problems and everything works fine now.
Marty B.
--
An artist who is forced to work a specific schedule, is no longer
an artist; he is just hired help. Inspiration cannot be purchased.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-08-23 0:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 20:27 duplicate MAC addresses marty
2009-08-18 21:20 ` Greg KH
2009-08-18 21:36 ` Matthew Dharm
2009-08-19 0:26 ` marty
2009-08-19 9:19 ` Alan Jenkins
2009-08-19 9:45 ` Rui Santos
2009-08-19 16:51 ` marty
2009-08-23 0:36 ` marty [this message]
2009-08-24 18:56 ` John Stoffel
2009-08-24 20:13 ` marty
2009-08-25 8:30 ` Alan Jenkins
2009-08-25 8:31 ` Alan Jenkins
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=4A908F0A.5090100@goodoldmarty.com \
--to=marty@goodoldmarty.com \
--cc=linux-hotplug@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).