Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Aug 2015 22:43:38 +0000
From:      Glen Barber <gjb@FreeBSD.org>
To:        sbruno@freebsd.org
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Possible Error in the FreeBSD 10.2 Release Notes/Man page for TCP
Message-ID:  <20150812224338.GC1460@FreeBSD.org>
In-Reply-To: <55CBCB91.9010301@ignoranthack.me>
References:  <131f8a0f25200031103639e969702727@dweimer.net> <20150812221546.GB1460@FreeBSD.org> <55CBCB91.9010301@ignoranthack.me>

next in thread | previous in thread | raw e-mail | index | archive | help

--MnLPg7ZWsaic7Fhd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 12, 2015 at 03:41:21PM -0700, Sean Bruno wrote:
> On 08/12/15 15:15, Glen Barber wrote:
> > On Wed, Aug 12, 2015 at 01:09:31PM -0500, dweimer wrote:
> >> I was reading through the Release notes, and decided to enable=20
> >> net.inet.tcp.pmtud_blackhole_detection in my test environment. It
> >> appears that the monitoring tunable
> >> net.inet.tcp.pmtud_blackhole_min_activated is incorrectly listed.
> >> Using sysctl -a | grep net.inet.tcp.pmtud, doesn't show it as a
> >> result. The test system is running RC3 built on the 7th from=20
> >> revision 286391 of the https://svn.freebsd.org/base/releng/10.2
> >> tree.
> >>=20
> >> root@freebsd:/usr/src # sysctl -a | grep net.inet.tcp.pmtud=20
> >> net.inet.tcp.pmtud_blackhole_mss: 1200=20
> >> net.inet.tcp.pmtud_blackhole_failed: 0=20
> >> net.inet.tcp.pmtud_blackhole_activated_min_mss: 0=20
> >> net.inet.tcp.pmtud_blackhole_activated: 0=20
> >> net.inet.tcp.pmtud_blackhole_detection: 1
> >>=20
> >> I did confirm that the pmtud_blackhole_min_activated option is
> >> also listed in the tcp(4) man page page as well.
> >>=20
> >> If anyone is more familiar with this than I am can they look into
> >> seeing if there is indeed an error, or if I am missing something
> >> here.
> >>=20
> >=20
> > This appears to be an error based on the content of the commit
> > log. I will confirm with the person that committed the code, and
> > will note the findings in the 10.2-RELEASE errata document.
> >=20
>=20
> This looks like I failed to MFC r276345 to stable 10 in order to
> update tcp.4 leading to this confusion.
>=20

Thank you for confirming.  I'll update the 10.2-RELEASE errata
accordingly.

What should the proper sysctls be, for completeness?

Glen


--MnLPg7ZWsaic7Fhd
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVy8waAAoJEAMUWKVHj+KTYeAQAI3pG0N8jUnATRtGRvrjIui2
4bhZuHdlMGRmSftudxVa5ObOmknG5JUroJ+DBi6P9S+3hixFThsHJ4enCywboQV8
9Ghf59bMCGqk9CiEHe0cH2aCD5355zoH89xwAhlMV4KDi8Y5bC9dtYoHMBrghuqs
4ku2Naia5NJHXNokweT8sj+jzAYzOGwBggeuHiJJH5CwjQl9marVidRj+AeMU4zo
XAKXF1FttQm8lIoSQ6RNlfnPzg0fE6EccYJRQ6AMuU8XS55w1PQPkscfAJUuGlJA
yZeGgEt9umMr53AsxB4pubIAAqLL+1pgiNJBdtmmkRvOVoVasj13aPEvvCSbLFmC
O/jl7Zb4aJ3g931S1L4l0cTv3babVZjHJXZmpypymPhL9qVozuRSae4wXOgLXB3T
cQK+kHlXvJaa4E4XSJELpnzS3LrtMc5VA1Mll7jM6qCQyIe+J8VBZkymHNXTqxXa
hc1NAxfbMsgtgEK/kACDMiIU0ZL3X43SV946taDvrO1FuvP+jTCimA88hEb+WMIK
8UMUoOPFaAPFVYD1til7XWEiizFHHx1orzayKXdUytFP8p34X+BnjpipX/ZUL6hn
PhUluhB4PaXT5bppyPEwrFF1gsi5LHq9w4mKmVgAplXl5zXWyA8lZNhKm8LOdOwR
r1HImfoKMJlOc7kn2bhg
=TkAM
-----END PGP SIGNATURE-----

--MnLPg7ZWsaic7Fhd--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150812224338.GC1460>