From: Robert Hancock <hancockr@shaw.ca>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Router stops routing after changing MAC Address
Date: Mon, 13 Mar 2006 18:23:19 -0600 [thread overview]
Message-ID: <44160CF7.8020008@shaw.ca> (raw)
In-Reply-To: <5Q3RY-4b9-15@gated-at.bofh.it>
linux-os (Dick Johnson) wrote:
>> And sometimes the routers are not accessible - you can't cycle them even
>> if you had permission. Consider the cases of bridged DSL service -
>
> Bzzzzst... Not! There are not any MAC addresses associated with any
> of the intercity links, usually not even in WANs! MAC is for
> Ethernet!
Bzzzt.. Plenty of DSL and cable services have a MAC address for both
ends of the connection that can be seen from the other end. Essentially
the link appears like a restricted Ethernet link.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-03-14 0:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5Q3yI-3MW-57@gated-at.bofh.it>
[not found] ` <5Q3RY-4b9-15@gated-at.bofh.it>
2006-03-14 0:23 ` Robert Hancock [this message]
2006-03-16 18:32 Router stops routing after changing MAC Address Greg Scott
-- strict thread matches above, loose matches on Subject: below --
2006-03-14 15:30 Greg Scott
2006-03-14 12:12 Simon Mackinlay
2006-03-13 22:15 Greg Scott
2006-03-13 22:35 ` linux-os (Dick Johnson)
2006-03-14 11:40 ` Bart Samwel
2006-03-14 12:52 ` linux-os (Dick Johnson)
2006-03-14 23:57 ` Valdis.Kletnieks
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
2006-03-13 6:11 Chuck Ebbert
2006-03-12 20:52 Greg Scott
2006-03-12 19:38 Greg Scott
2006-03-12 20:54 ` Alan Cox
2006-03-12 15:34 Greg Scott
2006-03-12 18:14 ` Alan Cox
2006-03-12 20:44 ` Randy.Dunlap
2006-03-11 3:08 Greg Scott
2006-03-11 2:33 Greg Scott
2006-03-11 0:33 Greg Scott
2006-03-11 0:39 ` Stephen Hemminger
2006-03-11 0:43 ` Michael Clark
2006-03-11 1:17 ` David S. Miller
2006-03-11 0:50 ` Bart Samwel
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=44160CF7.8020008@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.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