[ale] DHCP strangeness

[Carl Forsell]

In my former life, as a Novell admin, I used Netgear FA310TX  nic's for a
while, and was very unhappy with them.  Lots of "weird" problems that I, at
first, thought were coming from users screwing around all went away when I
swapped out thos nics.  If I were you, I would replace the nic and see if
problems go away.  The obvious is sometimes the hardest to see....

-----Original Message-----
From: Joe Knapka <jknapka at earthlink.net>
To: ale at ale.org
To: ale at ale.org <ale at ale.org>
Date: Wednesday, August 16, 2000 2:44 PM
Subject: [ale] DHCP strangeness


>Hi, everyone,
>
>My Slackware 7.1 workstation ("whyknot") sometimes behaves
>strangely with respect to DHCP on bootup. I can see the
>DHCPREQUEST and DHCPACK packets for whyknot go by
>on the DHCP server's log, but whyknot never seems to
>see the DHCPACKs. Eventually it sends a DHCPDISCOVER and
>gets a DHCPOFFER from the server, but even that it
>doesn't respond to. When this occurs, I have to log in
>and manually run dhcpcd, and even then it sometimes takes
>two or three tries before it gets an address. It only acts
>this way about half the time; the other half it boots,
>DHCPREQUESTS, gets a DHCPACK, and is happy.
>
>The ethercard is a Netgear FA310TX in 10Mbit, half-duplex
>mode. I'm running kernel 2.2.16, and the tulip driver
>from the kernel tree.
>
>Anyone seen this kind of thing before?
>
>TIA,
>
>-- Joe
>
>--
>*** Joseph Knapka ***
>In any formula, constants (especially those obtained from handbooks)
>are to be treated as variables.
>--
>To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message
body.
>

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.