[482] in linux-net channel archive
Re: CONFIG_INET_SNARL: What for?
daemon@ATHENA.MIT.EDU (Michael Shields)
Tue Jun 13 23:06:54 1995
From: shields@tembel.org (Michael Shields)
To: Pjnesser@rocket.com (Philip J. Nesser)
Date: Wed, 14 Jun 1995 01:55:23 +0000 (GMT)
Cc: shields@tembel.org, urlichs@smurf.noris.de,
submit-linux-dev-net@ratatosk.yggdrasil.com
In-Reply-To: <9506140004.AA19727@asgaard.rocket.com> from "Philip J. Nesser" at Jun 13, 95 05:04:30 pm
> >With CIDR the two high bits are no longer meaningful. There is no longer
> >any such thing as inherent "class C".
>
> >CONFIG_INET_SNARL should be removed.
>
> Thats not completely true. If your upstream providor aggregates your route
> then its true, but if you are not part of an aggregate (ie you got your
> class C more than about 2 years ago) then that logic doesn't hold. There
> are other reasons that isn't true but I won't go into them.
It still doesn't work, because in the future blocks will be assigned from
"class A" space. Net 39 is already experimentally split. This means
that you might get the "class C" 39.1.2, and there is no way to tell from
the address whether all of 39.x.x.x is at your site or just 39.x.x.(x<16).
You cannot tell the size of the block from the address. ifconfig knows
the correct netmask and that's what should be used.
--
Shields.
