From: Michael Clark <michael@metaparadigm.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Router stops routing after changing MAC Address
Date: Sat, 11 Mar 2006 08:43:48 +0800 [thread overview]
Message-ID: <44121D44.5030008@metaparadigm.com> (raw)
In-Reply-To: <20060310163958.1215b0c4@localhost.localdomain>
Stephen Hemminger wrote:
>On Fri, 10 Mar 2006 18:33:15 -0600
>"Greg Scott" <GregScott@InfraSupportEtc.com> wrote:
>
>
>
>>Hello - This feels like a kernel issue. I spent hours and hours and
>>hours looking for documentation and archives around this but did not
>>find anything.
>>
>>I have a Linux router and I need the ability to swap hardware without
>>causing downtime. The problem, of course, is ARPs. The NICs in the
>>replacement system need the same MAC Addresses as the NICs in the
>>original system. I'd like this all to be in the kernel and not depend
>>on a daemon process that can die.
>>
>>How to change MAC addresses is documented well enough - and it works -
>>but when I change MAC addresses, my router stops routing. From the
>>router, I can see the systems on both sides - but the router just
>>refuses to forward packets. Here are my little test scripts to change
>>MAC Addresses.
>>
>>
>
>You probably just need to flush the route cache after the address change?
>
>
Or do a gratutious arp for the address with the new HW address (tool to
do this is included in HA failover software such as heartbeat and others).
~mc
next prev parent reply other threads:[~2006-03-11 0:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 0:33 Router stops routing after changing MAC Address Greg Scott
2006-03-11 0:39 ` Stephen Hemminger
2006-03-11 0:43 ` Michael Clark [this message]
2006-03-11 1:17 ` David S. Miller
2006-03-11 0:50 ` Bart Samwel
-- strict thread matches above, loose matches on Subject: below --
2006-03-11 2:33 Greg Scott
2006-03-11 3:08 Greg Scott
2006-03-12 15:34 Greg Scott
2006-03-12 18:14 ` Alan Cox
2006-03-12 20:44 ` Randy.Dunlap
2006-03-12 19:38 Greg Scott
2006-03-12 20:54 ` Alan Cox
2006-03-12 20:52 Greg Scott
2006-03-13 6:11 Chuck Ebbert
2006-03-13 12:15 Greg Scott
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 20:57 Greg Scott
2006-03-13 21:39 ` linux-os (Dick Johnson)
2006-03-13 21:50 ` Rick Jones
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
[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
2006-03-14 12:12 Simon Mackinlay
2006-03-14 15:30 Greg Scott
2006-03-16 18:32 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=44121D44.5030008@metaparadigm.com \
--to=michael@metaparadigm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.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