On Sun, 7 Sep 2003, Jochen Kunz wrote:
> > root on le0
> > nfs_boot: trying RARP (and RFC/bootparam)
> > nfs_boot: client_addr=192.0.0.10 (RARP from 192.0.0.1)
> > nfs_boot: timeout
> I had (possibly) the same error when I netbooted a SPARCstation 1+ from
> a FreeBSD machine. It was quite simple. The primitive IP stack of the
> netloader on the client machine can't answer arp requests. But the
> server broadcasts a arp (arp, not rarp) when the tftp or NFS action is
> starting. Solution was simple: Set the arp information for the client
> on the host paermanent. Somthing like
> arp -s 192.0.0.10 00:11:22:33:44:55 permanent
> on the boot server.
This is why non-broken rarpd servers do this themselves :)
--f
Received on Tue Sep 16 2003 - 06:03:01 BST
This archive was generated by hypermail 2.3.0
: Fri Oct 10 2014 - 23:36:26 BST