Subject: Re: vaxserver 3100 netbooting, nfs_boot timeout
To: None <port-vax@netbsd.org>
From: Thorsten Jens <thojens@gmx.de>
List: port-vax
Date: 09/10/2000 21:01:37
* Johnny Billquist:

> On Sun, 10 Sep 2000, Thorsten Jens wrote:
> 
> > 
> > Hmm -- I *am* using a subnet mask of 255.255.255.0, and I honestly
> > don't know what should be wrong about subnetting that way. I never
> > had any problems with this setup, with no OS. Tell me why I should
> > change that :-)
> 
> Thought so. :-)
> 
> The problem is that 10.x.y.z is an A-network address (I hope you forgive
> me if you already know this) and the broadcast address is 10.255.255.255.
> In addition to this, if you are subnetting a network, you also get a
> subnet broadcast address. So in your case, there are actually two
> broadcast addresses: 10.255.255.255 and 10.10.10.255. Unfortunately, many
> IP stacks ignore the network broadcast address.
> 
> I'm not sure if netword broadcasts have been demoted to a thing of the
> past or not, but obviously this is your problem right now.
> (I think I've seen some RFC talking about this, but my memory is really
> not trustowrthy.)

I thought the classification into A-B-C network classes was a thing
of the past, actually.  
 
> Anyway, you have several options.
> 
> 1. See to it that you recognize network broadcasts.
> 2. See to it that the VAX does a subnet broadcast.
> 3. Change your network mask.

I think I'll go for choice #3 -- since I *know* how to do that ;-)
 
> Actually, give me a good reason *why* you are subnetting 10? :-)

I'll tell you in private mail since it's so embarassing :-)

Thorsten
-- 
Thorsten Jens <thojens@gmx.de>

Am thinkink is signature.