Presumably you are using the 10.x.x.x network number because you are using
private addresses right? The bug is that you have manually configured the
other devices on your fake 10 net to have a netmask of 255.255.255.0 when
the default class A netmask is 255.0.0.0, which is why you see this:
   >23:12:54.133405 vaxine.ep.1023 > 10.255.255.255.sunrpc: udp 96
					^^^^^
				broadcast address on the 10 class A network
It should be 10.x.y.255 where (x.y are the network number)

You can "fix" this by configuring your rarp/mopd/netserver to be on the
class A 10 network and later when you've booted you can go into rc.conf and
change the config options to set up a 24 bit netmask.

--Chuck


At 11:38 PM 3/10/99 +0100, Hans Christian Saustrup wrote:
>On Wed, Mar 10, 1999 at 10:29:10PM +0100, Hans Christian Saustrup wrote:
>
>> I've got it hanging at "nfs_boot: timeout..."
>
>.. and I did some more research. A tcpdump on my linux shows several of
>these lines:
>23:12:54.133405 vaxine.ep.1023 > 10.255.255.255.sunrpc: udp 96
>
>The Vax displays this:
> nfs_boot: trying RARP (and RPC/bootparam)
> nfs_boot: client_addr=0xa000042 (RARP from 0xa000001)
> nfs_boot: timeout... (several of these)
>
>I doublechecked the netboot faq, and I think I got everything right - mop
>has to work, because it's getting the bootloader. bootparamd should be up
>too, because it knows where to get the kernel. The kernel loads, and
>something goes wrong.. ?
>
>Kind regards,
>HC
>
>-- 
>Hans Christian Saustrup [HCS13-RIPE]
>System Administrator and Student of Computer Science       
>Please use PGP when possible.