[480] in linux-net channel archive
Re: CONFIG_INET_SNARL: What for?
daemon@ATHENA.MIT.EDU (Philip J. Nesser)
Tue Jun 13 21:34:33 1995
Date: Tue, 13 Jun 95 17:04:30 PDT
To: shields@tembel.org
Cc: urlichs@smurf.noris.de, submit-linux-dev-net@ratatosk.yggdrasil.com
In-Reply-To: <m0sLcTj-000DYFC@yage.tembel.org> (shields@tembel.org)
From: "Philip J. Nesser" <Pjnesser@rocket.com>
>From: shields@tembel.org (Michael Shields)
>Date: Tue, 13 Jun 1995 20:22:26 +0000 (GMT)
>Cc: submit-linux-dev-net@ratatosk.yggdrasil.com
>> CONFIG_INET_SNARL selects whether to use the netmask of a device (set by
>> ifconfig) or the IP-class-default netmask (i.e. 255.255.255.0 for a class C
>> address) for figuring out which MTU to use for TCP.
>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.
>--
>Shields.
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.
---> Phil
