Mike --------------------------------- Cleary_Mike@emc.com --------------------------------- Even a blind hog finds an acorn once in a while. -----Original Message----- From: Rick Green [mailto:rtg@mich.com] Sent: Tuesday, July 30, 2002 11:18 AM To: Cleary_Mike@emc.com Cc: suse-linux-e@suse.com Subject: RE: [SLE] DHCP problems - Solved? Maybe...? In /etc/dhclient.conf, I changed initial-interval 2; to initial-interval 5; and DHCP negotiation has been successful on the first try every time since! HTH, Rick Green On Tue, 30 Jul 2002 Cleary_Mike@emc.com wrote:
Well, I finally got an IP out of DHCP, although I'm not entirely sure why. After re-configuring the network card to obtain an IP via DHCP, I did the following:
# rcnetwork stop # ifconfig eth0 up # rcnetwork -n # rcnetwork start (DHCP "failed") # rcnetwork -n # rcnetwork restart (DHCP succeeded)
I then rebooted the machine and DHCP succeeded....:) I may still play around w/ Ethereal to see if I can find out what was going on.
Thanks to all for the suggestions!
Mike --------------------------------- Cleary_Mike@emc.com --------------------------------- Even a blind hog finds an acorn once in a while.
-----Original Message----- From: Rick Green [mailto:rtg@mich.com] Sent: Monday, July 29, 2002 1:52 AM To: Cleary_Mike@emc.com Cc: suse-linux-e@suse.com Subject: RE: [SLE] DHCP problems
On Sat, 27 Jul 2002 Cleary_Mike@emc.com wrote:
I booted up both of my machines in linux last night, and one got an IP via DHCP, and the other failed. Both have the same motherboard w/ the same on-board NIC. The one which worked has a Duron 1Gig, and the one which failed has an Athlon 1600+. Both are running 8.0 and set up virtually the same. I had reset my router (to the factory default values) also. Strange......
I've been having similar problems ever since I loaded SuSE 8.0 on my laptop. At first, I thought my PCMCIA ethernet card had gone flaky, but I eventually came to the conclusion that the DHCP client dhcpcd was timing out way too quickly. It's only giving about 5 seconds before it 'backgrounds', even though the manpage says it will listen for 60 seconds, and then it'll only retry after 15 minutes or so. Somehow, I was able to edit a config file somewhere, and extend the grace period, so it's been working fine for a few months now. Today, I was playing with my latest toy, a D-Link CF WiFI card. I ended up switching from the 'kernel' PCMCIA support to the 'external' one, and I got a driver to load, but the fast-timeout problem reappeared!
Issueing `dhcpcd -n` causes it to wake up and retry immediately, and at least today, I was able to complete the negotiation on the second or third try. WHen I find the location of the timeout parameter again, I'll post a value that works for me...
-- Rick Green "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -Benjamin Franklin