[481] in linux-net channel archive
Re: CONFIG_INET_SNARL: What for?
daemon@ATHENA.MIT.EDU (Aleph One)
Tue Jun 13 22:45:21 1995
Date: Tue, 13 Jun 1995 20:33:51 -0500 (CDT)
From: Aleph One <aleph1@dfw.net>
To: Matthias Urlichs <urlichs@smurf.noris.de>
Cc: submit-linux-dev-net@ratatosk.yggdrasil.com
In-Reply-To: <3rjm4e$tlk@smurf.noris.de>
Actually the later makes sense for a network for with multiple subnets in
the same physical network, while the former I guess would use the Path
MTU discovery mechanisims to find out the MTU. (e.g. subnets may be
separeted by slip link, etc).
Aleph One / aleph1@dfw.net
http://underground.org/
On 13 Jun 1995, Matthias Urlichs wrote:
> Subject: CONFIG_INET_SNARL: What for?
>
> Hi,
>
> 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.
>
> I wonder what the reason for this is. I can't think of any correctly-
> configured machine where the latter behavior would make any more sense than
> the former, yet the latter is the default (and more expensive to compute).
> On the other hand, for networks with non-default netmasks, I can think of a
> few cases where the former behavior would make much more sense.
>
