TCLUG Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [TCLUG:1255] dhcpd problem



On Thu, 17 Sep 1998, Clay Fandre wrote:

> Try tcpdump. This will dump out everything that goes over the wire. I
> actually used it the other day to fix one of my dhcp problems. If you
> have more than one interface make sure you are monitoring the correct
> one. (-i eth0 for example)

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? 

-Tim

--
Timothy D. Wilson			"A little song, a little dance,
University of MN, chem. dept.		a little seltzer down your 
wilson@chem.umn.edu			pants."   -Chuckles the Clown
Phone: (612) 625-9828                       as eulogized by Ted Baxter