[504] in linux-net channel archive
Re: CONFIG_INET_SNARL: What for?
daemon@ATHENA.MIT.EDU (Michael Shields)
Wed Jun 14 23:56:41 1995
From: shields@tembel.org (Michael Shields)
To: cmetz@sundance.itd.nrl.navy.mil (Craig Metz)
Date: Thu, 15 Jun 1995 00:46:41 +0000 (GMT)
Cc: shields@tembel.org, linux-net@vger.rutgers.edu
In-Reply-To: <9506150034.aa07716@cs.nrl.navy.mil> from "Craig Metz" at Jun 14, 95 07:34:40 pm
> In
> the vast majority of environments, SNARL actually still does benefit you
> because it will increase the number of (sub)networks on which you will use
> a large MSS from one (ONLY your local subnet) to (n::n > 0) where n is based
> on your classed allocation size and subnet mask. In no case that I can see
> will it actually hurt you.
Let's say I get a /28 from one of my provider's class C's. SNARL will
consider the "all subnets" mask to be 255.255.255.0, which is broader
than the correct value of 255.255.255.240. This means that packets to
other sites in the same class C will be sent with a large MTU over that
small-MTU link, simply because we happen to have similar addresses.
--
Shields.
