Report information
The Basics
Id:
43683
Status:
open
Priority:
Medium/Medium
Queue:

People
Owner:
Nobody in particular
Cc:
AdminCc:

BugTracker
Version Fixed:
(no value)
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
(no value)
Priority:
P2 Normal
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
BIND Server
Area:
bug

Dates
Created:Fri, 18 Nov 2016 06:17:16 -0500
Updated:Thu, 31 Aug 2017 09:12:40 -0400
Closed:Not set



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

Subject: TCP segment handling issue?
Date: Fri, 18 Nov 2016 20:17:07 +0900
To: bind9-bugs@isc.org
From: "Ray Bellis" <ray@isc.org>
Via kato@wide.ac.jp: bind-9.11.0-p1 seems to me that it applys TCP_MAXSEG to 1220byte even in IPv4, resulting TCP transmission a little bit less efficient. At around line 3698 of lib/isc/unix/socket.c, the code should be executed only if protocol family is AF_INET6: if (NEWCONNSOCK(dev)->pf == AF_INET6) { use_min_mtu(NEWCONNSOCK(dev)); set_tcp_maxseg(NEWCONNSOCK(dev), 1280 - 20 - 40); } This relates to the survey done by Geoff Huston and reported on his blog earlier this week.
Subject: Re: [ISC-Bugs #43683] TCP segment handling issue?
Date: Sat, 19 Nov 2016 11:46:33 +1100
To: bind9-bugs@isc.org
From: "Mark Andrews" <marka@isc.org>
In message <rt-4.2.8-98277-1479467836-1082.43683-3-0@isc.org>, "Ray Bellis via RT" writes: > Via kato@wide.ac.jp: > > bind-9.11.0-p1 seems to me that it applys TCP_MAXSEG to 1220byte even > in IPv4, resulting TCP transmission a little bit less efficient. At > around line 3698 of lib/isc/unix/socket.c, the code should be executed > only if protocol family is AF_INET6: > > if (NEWCONNSOCK(dev)->pf == AF_INET6) { > use_min_mtu(NEWCONNSOCK(dev)); > set_tcp_maxseg(NEWCONNSOCK(dev), 1280 - 20 - 40); > } > > > This relates to the survey done by Geoff Huston and reported on his blog > earlier this week. And there is nothing wrong with this. We really don't want PMTUD to happen over IPv4 or IPv6. Setting the max seg to 1220 avoids triggering PMTUD for IPv6 over IPv4 and IPv4 over IPv6. If anything the pf test should be removed. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org