In <URL:news:local.port-arm26> on Sat 06 May, Ben Harris wrote:
> On Sat, 6 May 2000, Leo Smiers wrote:
> 
> > When I try to boot the kernel displays:
> > 
> > root on ea0
> > mountroot: trying nfs...
> > nfs_boot: trying DHCP/BOOTP
> > nfs_boot: wrong xid
> > nfs_boot: wrong xid
> > nfs_boot: wrong xid
> > nfs_boot: wrong xid
> > nfs_boot: wrong xid
> > nfs_boot: timeout...
> > nfs_boot: wrong xid
> > nfs_boot: timeout...
> > nfs_boot: timeout...
> 
> Hmm.  Can you show me (a) the log output from dhcpd and (b) relevant
> tcpdump output (e.g. from "tcpdump port bootps or port bootpc" on the 
> server)?  It looks as if the Arc's sending packets correctly,
> and _almost_ understanding the response.
> 

Here is what is written in the /var/lof/messages file.

May  6 07:00:48 localhost dhcpd: DHCPDISCOVER from 00:02:07:01:1a:40 via eth0
May  6 07:00:48 localhost dhcpd: DHCPOFFER on 192.168.0.2 to 00:02:07:01:1a:40 via eth0

These two lines are repeated 7 times.

Here is the tcpdump output:
07:54:38.562470 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0x6ffffff [|bootp] [ttl 1]
07:54:38.574329 portier.bootps > mozart.bootpc:  xid:0x6ffffff Y:mozart S:localhost [|bootp] [tos 0x10]
07:54:39.621753 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0x6ffffff secs:1 [|bootp] [ttl 1]
07:54:39.629462 portier.bootps > mozart.bootpc:  xid:0x6ffffff secs:1 Y:mozart S:localhost [|bootp] [tos 0x10]
07:54:41.680360 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0x6ffffff secs:3 [|bootp] [ttl 1]
07:54:41.687898 portier.bootps > mozart.bootpc:  xid:0x6ffffff secs:3 Y:mozart S:localhost [|bootp] [tos 0x10]
07:54:44.737781 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0x6ffffff secs:6 [|bootp] [ttl 1]
07:54:44.745613 portier.bootps > mozart.bootpc:  xid:0x6ffffff secs:6 Y:mozart S:localhost [|bootp] [tos 0x10]
07:54:48.795428 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0x6ffffff secs:10 [|bootp] [ttl 1]
07:54:48.803064 portier.bootps > mozart.bootpc:  xid:0x6ffffff secs:10 Y:mozart S:localhost [|bootp] [tos 0x10]
07:54:53.897322 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0x6ffffff secs:15 [|bootp] [ttl 1]
07:54:53.904515 portier.bootps > mozart.bootpc:  xid:0x6ffffff secs:15 Y:mozart S:localhost [|bootp] [tos 0x10]
07:54:58.994368 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0x6ffffff secs:20 [|bootp] [ttl 1]
07:54:59.006262 portier.bootps > mozart.bootpc:  xid:0x6ffffff secs:20 Y:mozart S:localhost [|bootp] [tos 0x10]
07:55:04.100557 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0x6ffffff secs:25 [|bootp] [ttl 1]
07:55:04.111320 portier.bootps > mozart.bootpc:  xid:0x6ffffff secs:25 Y:mozart S:localhost [|bootp] [tos 0x10]

There is a time difference between the messages file and the tcpdump because:
a) The dhcpd is on 'portier' and he is still running in wintertime
b) I have made the tcpdump on 'ravel' running netbsd-arm32. (the tcpdump on
   portier didn't show the respons messages.)
   
As an extra test (I had to reboot ravel to go run netbsd-arm32) I also run
the netbsd dhcpd but this gave the same result as running the dhcpd from
portier (which is a linux machine).

I hope this info will help you further.

Leo

-- 
Leo Smiers
System specialist FB/SP                    bv Nederland Haarlem
!PDF 0.73a | !Flash 0.49b                  http://people.a2000.nl/lsmiers