From: Timothy Covell <timothy.covell@ashavan.org>
To: "Prof. Brand " <brand@jupiter.cs.uni-dortmund.de>,
timothy.covell@ashavan.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: strange kernel message when hacking the NIC driver
Date: Sat, 12 Jan 2002 15:44:50 -0600 [thread overview]
Message-ID: <200201122148.g0CLmfSr008317@svr3.applink.net> (raw)
In-Reply-To: <200201122137.g0CLbDR26750@jupiter.cs.uni-dortmund.de>
In-Reply-To: <200201122137.g0CLbDR26750@jupiter.cs.uni-dortmund.de>
On Saturday 12 January 2002 15:37, Prof. Brand wrote:
> Timothy Covell <timothy.covell@ashavan.org> said:
> > On Friday 11 January 2002 06:07, David S. Miller wrote:
> > > From: Timothy Covell <timothy.covell@ashavan.org>
> > > Date: Fri, 11 Jan 2002 05:55:20 -0600
> > >
> > > Let me clarify what I said earlier. You cannot have
> > > identical MAC addresses on two different NICs.
> > >
> > > There is nothing illegal about that at all. As long at
> > > the NICs live on different subnets, it is perfectly fine.
> > > In fact this is pretty common on Sun machines.
> >
> > True. I was assuming that the context of the post was
> > that the NICs were on the same network link.
>
> This is not the typical setup...
>
> > Solaris _defaults_ to using the MAC address from the
> > primary (hostname) NIC for the rest of them.
>
> Sun sets the MAC from the machine ID on all network interfaces by
> default. Not Solaris, AFAIU it is done by the PROM.
>
> > IMHO, this
> > is a really stupid thing to do, and I disable it tout de suite
> > when given a choice. Of course, if you like it, then
> > why don't you try to convince Linus to change his mind
> > about it?
>
> Why should DaveM convince Linus to get Sun to change their mind on NIC
> setup?
You have it backwards. If you all seem to like the Sun way of doing things,
then Linus should change Linux to do likewise.
>
> Especially if it works just fine for 99.95% of Suns, and has the bonus that
> you can track each machine by a _single_ MAC, even if you change NICs or
> add more?
If you are already keeping a MAC <--> Host table, then it's not very hard to
expand it to keep track of other NICs. That is, of course, if you care about
tracking your inventory.
--
timothy.covell@ashavan.org.
next prev parent reply other threads:[~2002-01-12 21:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 4:19 Pei Zheng
2002-01-11 5:20 ` Timothy Covell
2002-01-11 11:55 ` Timothy Covell
2002-01-11 13:11 ` Alan Cox
2002-01-11 19:02 ` Timothy Covell
2002-01-11 19:24 ` Paul Walmsley
2002-01-11 22:51 ` Timothy Covell
2002-01-12 21:37 ` Prof. Brand
2002-01-12 21:58 ` Timothy Covell
2002-01-11 12:07 ` David S. Miller
2002-01-11 12:20 ` Timothy Covell
2002-01-12 21:37 ` Prof. Brand
2002-01-12 21:44 ` Timothy Covell [this message]
2002-01-11 12:28 ` David S. Miller
2002-01-11 19:33 ` Pei Zheng
2002-01-14 6:32 Zwane Mwaikambo
2002-01-14 7:41 ` Bernd Eckenfels
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=200201122148.g0CLmfSr008317@svr3.applink.net \
--to=timothy.covell@ashavan.org \
--cc=brand@jupiter.cs.uni-dortmund.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®