Subject: Re: vaxserver 3100 netbooting, nfs_boot timeout
To: Johnny Billquist <bqt@Update.UU.SE>
From: Andrew Gillham <firstname.lastname@example.org>
Date: 09/10/2000 15:11:25
Johnny Billquist writes:
> 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 :-)
I would recommend using a class C "reserved" address here. If you want
to use multiple subnets just use another reserved class C.
So something like '192.168.1.0' and '192.168.2.0', etc.
> 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.
> Actually, give me a good reason *why* you are subnetting 10? :-)
Uhmm, more than one subnet? Think wireless, or 10Mbit/s shared coax
versus 100Mbit/s shared, etc.
There are countless scenarios where a person might want more than one
subnet at their house (or in a lab, whatever) and obviously subnetting
is the only way to accomplish this. Now if NetBSD had decent bridging
support you could just call it all a big flat "10" and be done.
Otherwise you'll subnet. If NetBSD can't handle it correctly, it is a
But.. as most people want to subnet down to a /24 with whatever they pick
for addresses, they should probably just start with 192.168.0.0 in the
first place. Then the classfull broadcast and the classless will match.