From owner-freebsd-net@freebsd.org  Fri Mar 31 01:10:37 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB2A1D23625
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Fri, 31 Mar 2017 01:10:37 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id DADEADEC
 for <freebsd-net@FreeBSD.org>; Fri, 31 Mar 2017 01:10:37 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2V1AbFi082255
 for <freebsd-net@FreeBSD.org>; Fri, 31 Mar 2017 01:10:37 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken
Date: Fri, 31 Mar 2017 01:10:38 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 8.3-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: ae@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-173444-2472-7ELXhbpgnv@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-173444-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-173444-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Mar 2017 01:10:38 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173444

--- Comment #12 from Andrey V. Elsukov <ae@FreeBSD.org> ---
(In reply to marka from comment #10)
> (In reply to Andrey V. Elsukov from comment #8)
> So what!  Most DNS/TCP response is a few of packets.  What does it
> matter if it is the 3 or 4 packets.

Zone transfers need a lot of such few packets.

> What matters is avoiding PMTUD as it is NOT reliable.  Setting the
> IPv6 packet size to 1280 avoids triggering PMTUD issues.  Limiting
> the packet size avoids timeout and retransmissions due to PTB not
> been generated due to rate limiting or being lost due to stupid
> load balancers and firewalls that drop ICMP.
>=20
> Go put your validating resolvers behind a IPv6 in IPv4 link then
> come back and say this is not needed.

When I build the network in the DC, I know better what MTU can be used in my
network. And forcing 1280 bytes size for the network, where 9k is the defau=
lt
MTU is at least strange in the 2017.

--=20
You are receiving this mail because:
You are the assignee for the bug.=