Subject: Re: Default netmask
To: Brian C. Grayson <bgrayson@marvin.ece.utexas.edu>
From: Todd Vierling <tv@pobox.com>
List: tech-install
Date: 08/27/1998 14:52:42
On Thu, 27 Aug 1998, Brian C. Grayson wrote:
: 1. Is there anyone in their right mind on a class A or B that
: _really_ wants broadcasts to go to _all_ machines, i.e., that
: doesn't subnet internally? If not, maybe the default
: should be 0xffffff00, to avoid boneheads like me. :)
Actually, you should set a netmask all the time these days - there's _lots_
of CIDR (classless) networks out there now. The TCP/IP implementation is
expected to use classful netmasks as default, so it used 255.255.0.0 for
128.x.x.x.
: Or maybe a note should pop up for class A and B saying
: `most class A and B folks subnet internally, so the proper
: netmask is 0xffffff00. Do you want to use a netmask of
: 0xffffff00, or 0xff..0000?'
Actually, I lean more towards requiring the user to enter the right netmask,
and not have a default in sysinst at all. As above, 0xffffff00 isn't even
right many places these days.
: 2. In sysinst's net.c, it appears that the netmask for class C
: nets (192.* -- 223.*) is still set to 0xffff0000 --
: shouldn't that be 0xffffff00?
The default should be 0xffffff00. If it's 0xffff0000, it's wrong in the
source.
--
-- Todd Vierling (Personal tv@pobox.com; Bus. todd_vierling@xn.xerox.com)