On Thu, Jun 05, 2003 at 08:49:01PM +0200, Wolfgang Denk wrote:
[root@ohm2-cx etc]# tcpdump -i eth1 -s 200 -n -x tcpdump: listening on eth1 10:17:05.789993 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x721dffff [|bootp] (DF) 4500 0240 8de3 4000 2011 caca 0000 0000 ffff ffff 0044 0043 022c 8397 0101 0600 721d ffff 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00a0 c600 c741 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
Without looking up the bootp spec (again), I'd guess that the bootp server isn't responding. I believe that if the packet were ill formed, tcpdump would show something peculiar.