From: Bart Samwel <bart@samwel.tk>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Greg Scott <GregScott@InfraSupportEtc.com>,
Rick Jones <rick.jones2@hp.com>,
Chuck Ebbert <76306.1226@compuserve.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Simon Mackinlay <smackinlay@mail.com>
Subject: Re: Router stops routing after changing MAC Address
Date: Tue, 14 Mar 2006 12:40:33 +0100 [thread overview]
Message-ID: <4416ABB1.8020802@samwel.tk> (raw)
In-Reply-To: <Pine.LNX.4.61.0603131730100.5785@chaos.analogic.com>
linux-os (Dick Johnson) wrote:
> On Mon, 13 Mar 2006, Greg Scott wrote:
> Bzzzzst... Not! There are not any MAC addresses associated with any
> of the intercity links, usually not even in WANs! MAC is for
> Ethernet! Once you go to fiber, ATM, T-N, etc., there are no MAC addresses.
Bzzzzt. According to WikiPedia:
http://en.wikipedia.org/wiki/MAC_address
MAC addresses are used for:
- Token ring
- 802.11 wireless networks
- Bluetooth
- FDDI
- ATM (switched virtual connections only, as part of an NSAP address)
- SCSI and Fibre Channel (as part of a World Wide Name)
FDDI = fiber, ATM = ATM.
--Bart
next prev parent reply other threads:[~2006-03-14 11:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 22:15 Router stops routing after changing MAC Address Greg Scott
2006-03-13 22:35 ` linux-os (Dick Johnson)
2006-03-14 11:40 ` Bart Samwel [this message]
2006-03-14 12:52 ` linux-os (Dick Johnson)
2006-03-14 23:57 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2006-03-16 18:32 Greg Scott
2006-03-14 15:30 Greg Scott
2006-03-14 12:12 Simon Mackinlay
2006-03-13 20:57 Greg Scott
2006-03-13 21:39 ` linux-os (Dick Johnson)
2006-03-13 21:50 ` Rick Jones
2006-03-13 17:17 Greg Scott
2006-03-13 18:00 ` Stephen Hemminger
2006-03-13 20:27 ` linux-os (Dick Johnson)
2006-03-13 22:10 ` Randy.Dunlap
2006-03-14 14:16 ` Bjørn Mork
2006-03-16 16:07 ` Chris Wedgwood
2006-03-16 17:55 ` Stephen Hemminger
2006-03-13 12:15 Greg Scott
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=4416ABB1.8020802@samwel.tk \
--to=bart@samwel.tk \
--cc=76306.1226@compuserve.com \
--cc=GregScott@InfraSupportEtc.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=smackinlay@mail.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).