From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Michael F Gordon <Michael.Gordon@ee.ed.ac.uk>
Cc: David Lang <david.lang@digitalinsight.com>,
Garett Spencley <gspen@home.com>,
linux-kernel@vger.kernel.org,
Jeff Garzik <jgarzik@mandrakesoft.com>
Subject: Re: 2.4.4 breaks dhcpcd with Realtek 8139
Date: Sun, 29 Apr 2001 13:04:32 +0200 [thread overview]
Message-ID: <20010429130432.I679@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <Pine.LNX.4.30.0104281142520.3423-100000@localhost.localdomain> <Pine.LNX.4.33.0104281126570.16046-100000@dlang.diginsite.com> <20010428231151.A11841@ee.ed.ac.uk>
In-Reply-To: <20010428231151.A11841@ee.ed.ac.uk>; from Michael.Gordon@ee.ed.ac.uk on Sat, Apr 28, 2001 at 11:11:51PM +0100
On Sat, Apr 28, 2001 at 11:11:51PM +0100, Michael F Gordon wrote:
> On Sat, Apr 28, 2001 at 11:29:15AM -0700, David Lang wrote:
> > what sort of switch are you plugged into? some Cisco switches have a
> > 'feature' that ignores all traffic from a port for X seconds after a
> > machine is plugged in / powered on on a port (they claim somehting about
> > preventing loops) it may be that the new kernel now boots up faster then
> > the old one so that the DHCP request is lost in the switch, a few seconds
> > later when you do it by hand the swich has enabled your port and
> > everything works.
>
> I'm plugged in to a cable modem, with the DHCP server at the ISP. The
> server requires the MAC address to be registered, so sending the DHCP
> request with a different MAC address could cause the symptoms. I doubt
> it's a timing problem - replacing the 8139 driver with the 2.4.3 version
> but otherwise using the distributed 2.4.4 makes DHCP work as expected.
The Windows drivers distributed along with that Realtek cards
have this problem[1] any many users of the CSN[2] run into the
"secure mode" on our hubs/switches, causing their port to be
disabled.
So we have just ported a BUG from Windows to Linux, if you are
right ;-)
BTW: CC'ed the maintainer. He might be interested, as maintainers
usally are on BUGs ;-)
Regards
Ingo Oeser
[1] Sometimes forgetting their MAC and sending either random or
zero MAC out. This depends on whatever.
[2] Chemnitz Students Network - large LAN with >1000 computers
--
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< been there and had much fun >>>>>>>>>>>>
next prev parent reply other threads:[~2001-04-29 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 15:30 Michael F Gordon
2001-04-28 15:44 ` Garett Spencley
2001-04-28 18:29 ` David Lang
2001-04-28 22:11 ` Michael F Gordon
2001-04-29 11:04 ` Ingo Oeser [this message]
2001-04-29 15:46 ` Garett Spencley
2001-05-01 0:16 ` Chmouel Boudjnah
2001-04-28 15:46 André Cruz
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=20010429130432.I679@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=Michael.Gordon@ee.ed.ac.uk \
--cc=david.lang@digitalinsight.com \
--cc=gspen@home.com \
--cc=jgarzik@mandrakesoft.com \
--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
all inboxes | Powered by JetHome®