On Thu, 8 Jul 1999, Allen Briggs wrote:

> Hi.  I'm trying to netboot a NeXT from a dhcp/tftp server.  It looks
> like I'm getting the RRQs from the NeXT, but the server isn't
> responding.  I'm wondering if this is due to the vm=auto setting that is
> specified in the HOW-TO for bootp.  Anyone know?  Here's a bit of the
> tcpdump...
> 
> 16:28:20.386112 arp who-has 207.107.26.17 tell seka.netbsd.canuck.com
> 16:28:21.138930 207.107.26.17.1555 > seka.netbsd.canuck.com.tftp: [no cksum] 24 RRQ "netboot.next68k" (ttl 255, id 0)
> 16:28:21.154117 arp who-has 207.107.26.17 tell seka.netbsd.canuck.com
> 16:28:25.381233 arp who-has 207.107.26.17 tell seka.netbsd.canuck.com
> 16:28:26.151223 arp who-has 207.107.26.17 tell seka.netbsd.canuck.com
> 16:28:28.052972 207.107.26.17.1555 > seka.netbsd.canuck.com.tftp: [no cksum] 24 RRQ "netboot.next68k" (ttl 255, id 0)
[...]

I'd also double-check the arp setup.
According to your dump, the server never gets a reply to his arp request
about the client.

Regards,
Timm
-- 
Timm Wetzel     	<twetzel@gwdg.de>
Biomed. NMR GmbH        Tel +49 551 201-1091    FAX +49 551 201-1307
Am Fassberg 11, D-37077 Goettingen, Germany