From: Michael F Gordon <Michael.Gordon@ee.ed.ac.uk>
To: David Lang <david.lang@digitalinsight.com>
Cc: Garett Spencley <gspen@home.com>,
Michael F Gordon <Michael.Gordon@ee.ed.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.4 breaks dhcpcd with Realtek 8139
Date: Sat, 28 Apr 2001 23:11:51 +0100 [thread overview]
Message-ID: <20010428231151.A11841@ee.ed.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.30.0104281142520.3423-100000@localhost.localdomain> <Pine.LNX.4.33.0104281126570.16046-100000@dlang.diginsite.com>
In-Reply-To: <Pine.LNX.4.33.0104281126570.16046-100000@dlang.diginsite.com>; from david.lang@digitalinsight.com on Sat, Apr 28, 2001 at 11:29:15AM -0700
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.
Michael Gordon
next prev parent reply other threads:[~2001-04-28 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 15:30 2.4.4 breaks dhcpcd with Realtek 8139 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 [this message]
2001-04-29 11:04 ` Ingo Oeser
2001-04-29 15:46 ` Garett Spencley
2001-05-01 0:16 ` Chmouel Boudjnah
-- strict thread matches above, loose matches on Subject: below --
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=20010428231151.A11841@ee.ed.ac.uk \
--to=michael.gordon@ee.ed.ac.uk \
--cc=david.lang@digitalinsight.com \
--cc=gspen@home.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