Date: Fri, 20 Dec 2002 23:22:24 +0100 From: Emiel Kollof <coolvibe@hackerheaven.org> To: Mike Hogsett <hogsett@csl.sri.com> Cc: "Scott M. Nolde" <scott@smnolde.com>, redjupiter <redjupiter@ntlworld.com>, David Wolfskill <david@catwhisker.org>, freebsd-stable@FreeBSD.ORG Subject: Re: fxp0 device - Intel NIC Message-ID: <20021220222224.GH81599@hackerheaven.org> In-Reply-To: <200212202214.gBKMEbvV000679@beast.csl.sri.com> References: <20021220215907.GE67177@smnolde.com> <200212202214.gBKMEbvV000679@beast.csl.sri.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Mike Hogsett (hogsett@csl.sri.com) wrote: > > > The MAC address must be unique to the network > > Must be unique on the LAN segment, but not necessaryily across the > enterprise (as long as your switch infrastructure doesn't see the same MAC > in two places). This can be a problem on older Sun hardware with multiple > network cards, since the Suns seemed to set all the cards on the host to > the same MAC address (that of the primary card). True. The MAC adress on the SparcStations I own don't have the hardware address stored on the NIC itself. Kinda funny when you first notice it. Hey, that le0 and that hme0 have the same MAC address! :) Downside is when your NVRAM gets corruped though, all nics default to FF:FF:FF:FF:FF:FF. It's fixable, but having everything set to broadcast might give an unsuspecting sysadmin some headaches :) Cheers, Emiel -- In 1869 the waffle iron was invented for people who had wrinkled waffles. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021220222224.GH81599>