LinuxQuestions.org - Debian-amd64: dhcp-client stopped working

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - Debian-amd64: dhcp-client stopped working (https://www.linuxquestions.org/questions/debian-26/debian-amd64-dhcp-client-stopped-working-458546/)

Debian-amd64: dhcp-client stopped working

The source isn't with me this week. While trying to get Ati's drivers to work (http://www.linuxquestions.org/questi...d.php?t=457707) I did do some updating from within aptitude. So now I am running sarge, with more and more packages coming from etch.

Well somehow the dhcp-client broke. I've tried purging it, reinsatlling it, didn't help :(
I had my network up and running, without problems, then after a reboot, dhclient fails to find my network:

Code:

dhclient eth0

gives me something like:

Code:

Sending on Socket/fallback/fallback-net

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8

uli526x: eth0 Nic Link is Down

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16

...

No DHCPOFFERS received

No working leases in persistent database



Exiting

Failed to bring up eth0

I assume that during a packet update, some config got rewritten, which is now blocking dhclient. I know that the network works (dhcp under windows is still working), I don't really want to assign a static ip. I am runngin etch's kernel, 2.6.15.1 (I think) and have done so before, so I know it shouldn't be a driver issue with uli526x, although at one point I read something about "loosing to many clicks...maybe a driver ist blocking interrupts..." on the console... :scratch:

Any suggestions, are welcome!

Well it says the link is down and you are using dhclient from the command line do you have the /etc/network/interfaces file setup for dhcp and an auto eth0 line in there to bring the nic up on boot/restart of the networking.

Yes, I have added the required information to the 'interfaces' file...

What I don't quite understand is the 255.255.255.255, I'm no expert on networks, but isn't that address (or is it the netmask?) rather odd ?

No its normal, its sending it to a broadcast adress because it is trying to discover a dhcp server.

I don't see the point of using dhcp for little network configurations... it begins to be interesting over 5 machines... Static IP is more secure and fits more to your need. But its your machine, do what you want ;)

maybe try to look in the logs for a nic failure?
tail /var/log/messages

Quote:

While trying to get Ati's drivers to work...

Same thing happened to me. I wound up reinstalling. (Post #8) I have had some success in the past running dpkg-reconfigure xserver-xorg in the past to recover from such an error, but it didn't work this time.

If you're still determined to try to get those ATI drivers working, check this out. I got all the .deb files to build and execute, but couldn't get the module to load. Next thing I knew I had no network. Oh well ... fresh installs are nice anyway.

Hi rickh.
Offtopic, skip this post..
As you seem to be quite involved in the 64bits series, may I ask you if you have a good link to a comparison 32b/64b performance because last time some hardware guys explained me it was not worth switching but now that debian begins to have some 64bits support, I'm getting interested to make the big switch :)

Thx!