From: Chuck Ebbert <76306.1226@compuserve.com>
To: Greg Scott <GregScott@InfraSupportEtc.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: Router stops routing after changing MAC Address
Date: Mon, 13 Mar 2006 01:11:05 -0500 [thread overview]
Message-ID: <200603130115_MC3-1-BA82-CE7@compuserve.com> (raw)
In-Reply-To: <925A849792280C4E80C5461017A4B8A20321CC@mail733.InfraSupportEtc.com>
On Fri, 10 Mar 2006 18:33:15 -0600, Greg Scott wrote:
> 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.
>
> First - ip-fudge-mac.sh
> [root@test-fw2 gregs]# more ip-fudge-mac.sh
> ip link set eth0 down
> ip link set eth0 address 01:02:03:04:05:06
^
Bit zero is set, so this is a multicast address. Is that intentional?
> ip link set eth0 up
>
> ip link set eth1 down
> ip link set eth1 address 17:20:16:01:60:03
^
Ditto.
> ip link set eth1 up
>
> echo "1" > /proc/sys/net/ipv4/ip_forward
--
Chuck
"Penguins don't come from next door, they come from the Antarctic!"
next reply other threads:[~2006-03-13 6:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 6:11 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-16 18:32 Router stops routing after changing MAC Address Greg Scott
2006-03-14 15:30 Greg Scott
2006-03-14 12:12 Simon Mackinlay
[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-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-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=200603130115_MC3-1-BA82-CE7@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=GregScott@InfraSupportEtc.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.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