From: Stephen Hemminger <shemminger@osdl.org>
To: Chris Wedgwood <cw@f00f.org>
Cc: Greg Scott <GregScott@InfraSupportEtc.com>,
Chuck Ebbert <76306.1226@compuserve.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
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: Thu, 16 Mar 2006 09:55:08 -0800 [thread overview]
Message-ID: <20060316095508.00281efd@localhost.localdomain> (raw)
In-Reply-To: <20060316160743.GA13035@taniwha.stupidest.org>
On Thu, 16 Mar 2006 08:07:43 -0800
Chris Wedgwood <cw@f00f.org> wrote:
> On Mon, Mar 13, 2006 at 10:00:41AM -0800, Stephen Hemminger wrote:
>
> > There still is a bug in the 3c59x driver. It doesn't include any
> > code to handle changing the mac address. It will work if you take
> > the device down, change address, then bring it up. But you shouldn't
> > have to do that.
>
> I sent a patch do to this probably a year or two back and it was
> rejected (by akpm if I recall) because of the argument that you could
> and should take it down, change the MAC and bring it back up.
>
> Is this no longer a requirement?
No. most drivers allow changes on the fly.
next prev parent reply other threads:[~2006-03-16 17:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 17:17 Router stops routing after changing MAC Address 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 [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 20:57 Greg Scott
2006-03-13 21:39 ` linux-os (Dick Johnson)
2006-03-13 21:50 ` Rick Jones
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=20060316095508.00281efd@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=76306.1226@compuserve.com \
--cc=GregScott@InfraSupportEtc.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bart@samwel.tk \
--cc=cw@f00f.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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).