Re: [TCLUG:1255] dhcpd problem

[Clay Fandre <cfandre@minn.net>]

> I tried what Clay advised. I started tcpdump using the command 'tcpdump -i
> eth0' and then went to the other machine and tried to get an IP address
> using DHCP. The following is what I saw on the server. Each of these
> messages appeared several times. The only difference between them was the
> time.
> 
> Here's the tcpdump output:
> 
> 11:20:27.476048 10.22.2.250.route > 255.255.255.255.route: rip-resp 12:
> 192.168.141.0(2)[|rip]
> 11:21:03.876048 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x28286824
> [|bootp]
> 
> The first line appears to be communication between my server and the
> school's router (it's IP 10.22.2.250). Incidentally, I can ping the router
> (Novell BorderManager), but I can't get through it yet to the outside
> world. Our district sys admin is working on it, but any suggestions would
> be greatly appreciated.
> 
> The second would have to be the dhcp request. Why would it say bootpc?
> bootp is not running on the server, and I definitely selected dhcp on the
> client side. Does this make sense to anyone?

DHCP is an enhanced version of bootp. The functionality is the same, but
DHCP has a lot more build in. It still uses the basic protocol, so you
will see it show up as bootp. This is normal. The
0.0.0.0.bootpc>255.255.255.255.bootps is a client to server broadcast
for a DHCP (bootp) ip address. That part looks good. The DHCP server
should then respond to the client with an ip address. If it isn't, your
DHCP service may not be working correctly.

Usually the DHCP request will appear 3 times before it times out. I
would focus your investigation on the server.

Clay


-- 
***************************************************
** Clayton T. Fandre      cfandre@minn.net       **
***************************************************
Key fingerprint =  80 8C 43 89 C3 DB 80 4F  3F F1 90 28 2B 9B 22