[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1422289165.2687.34.camel@stressinduktion.org>
Date: Mon, 26 Jan 2015 17:19:25 +0100
From: Hannes Frederic Sowa <hannes@...essinduktion.org>
To: David Miller <davem@...emloft.net>
Cc: harouth@...eaurora.org, netdev@...r.kernel.org
Subject: Re: [PATCH v3 net-next] net: ipv6: Add sysctl entry to disable MTU
updates from RA
On Sa, 2015-01-24 at 23:14 -0800, David Miller wrote:
> From: Harout Hedeshian <harouth@...eaurora.org>
> Date: Tue, 20 Jan 2015 10:06:05 -0700
>
> > The kernel forcefully applies MTU values received in router
> > advertisements provided the new MTU is less than the current. This
> > behavior is undesirable when the user space is managing the MTU. Instead
> > a sysctl flag 'accept_ra_mtu' is introduced such that the user space
> > can control whether or not RA provided MTU updates should be applied. The
> > default behavior is unchanged; user space must explicitly set this flag
> > to 0 for RA MTUs to be ignored.
> >
> > Signed-off-by: Harout Hedeshian <harouth@...eaurora.org>
>
> Under what circumstances would userland ignore a router advertized
> MTU, and are the RFCs ok with this?
Sometimes those advertised MTUs are used to perform DoS attacks /
performance-degrading attacks (force generation of fragments e.g.) on
hosts. In larger, maybe non-controlled networks, it would be desirable
if one could disable acceptance of the MTU option.
Of course, there are similar issues with other options in RAs, too, but
mostly they result in more catastrophic connection failures. ;)
Bye,
Hannes
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists