Hello,

I am having some trouble with configuring my dhcp client. My client sends DHCPDISCOVER packets on 255.255.255.255 port 67, but doesn't receive any DHCPOFFER packet. This is the output of dhclient.

Listening on LPF/eth0/00:40:05:17:1E:53
Sending on LPF/eth0/00:40:05:17:1E:53
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
| |
| |
| |
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

I've read several threads on this topics. The folowing solutions didn't work out:

*Replugging the NIC
*Using etherconf for network configuration
*Trying other dhcp-clients, like dhcpd or pump.

One thread mentioned DHCPOFFERS not being recognized. So I downloaded tcpdump to see if I there is any incoming traffic, there isn't. I only found lines like this one:

_time_ 0.0.0.0.68 > 255.255.255.255.67 xid:0x_code_ secs:__ [:bootp] [tos 0x10]

Can I use ping, without having a valid ip myself, to verify this path, incl. ports?

My administrator is not cooperative. I get some info from the configuration of my laptop (win98). The dhcp server is at 131.155.239.140. Can I use ping, without having a valid ip myself, to contact it there? Can configure dhclient to contact that address? I've tried to do it with prepend, but DHCPDISCOVERS keep going at the standard broadcast address 255.255.255.255.

I've never installed a firewall, so I don't think that's the cause of the problem. How can I find out if my dhcp receiving port is open?

I'm running debian 2.2.x with dhcp3-client (and common). My network card is installed propperly using the ne module. However, it is an old ISA NIC, so fast functionality checks would be something I am interested in. Using ping, a cross-link and my laptop (without changing it's precious settings, since my ISP is very Lame) seems a good one, how would I do that? Has anyone got experience with the ne2k_diag proggie from Donald? Is that one useful to me? I've got and know how to compile it but what on earth does it have to say?

Answers to my questions or new tips would be something I really appreciate. It would be nice to break the endless loop with the following commands:



I hope to get a good solution soon.

Gilion

I think I found the solution to my problem. It seems to be a problem with electro-magnetic interference, which raises some new questions. However, these will be more appropriate in a fresh thread.