From: Rick Jones <rick.jones2@hp.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Greg Scott <GregScott@InfraSupportEtc.com>,
Chuck Ebbert <76306.1226@compuserve.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Bart Samwel <bart@samwel.tk>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Simon Mackinlay <smackinlay@mail.com>
Subject: Re: Router stops routing after changing MAC Address
Date: Mon, 13 Mar 2006 13:50:09 -0800 [thread overview]
Message-ID: <4415E911.8090504@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0603131636470.5608@chaos.analogic.com>
> Anyway, if the device fails, you have
> routers and hosts ARPing the interface, trying to establish a
> route anyway.
But only after what may be a much longer time than the customer is
willing to accept or able to configure. I know of a number of HA
situations where the "new" device is given the "old" MAC just to avoid
that speicific situation of ARP caches not being updated except after
quite some time. Not necessarily on the end-systems, the issue can be
with intermediate devices (routers).
And if one has to work with static ARP entries to deal (however
imperfectly) with ARP poisioning or whatnot...
Indeed, there is a large onus on the software doing the MAC override to
make sure it does not break the required uniqueness. Just as if one
were using locally administered MAC addresses.
rick jones
next prev parent reply other threads:[~2006-03-13 21:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 20:57 Router stops routing after changing MAC Address Greg Scott
2006-03-13 21:39 ` linux-os (Dick Johnson)
2006-03-13 21:50 ` Rick Jones [this message]
-- 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 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 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=4415E911.8090504@hp.com \
--to=rick.jones2@hp.com \
--cc=76306.1226@compuserve.com \
--cc=GregScott@InfraSupportEtc.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bart@samwel.tk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=netdev@vger.kernel.org \
--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).