From owner-freebsd-net@freebsd.org  Wed Aug  9 01:16:24 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 C15D1DABED7
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Wed,  9 Aug 2017 01:16:24 +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 B00738026E
 for <freebsd-net@FreeBSD.org>; Wed,  9 Aug 2017 01:16:24 +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 v791GMaI008654
 for <freebsd-net@FreeBSD.org>; Wed, 9 Aug 2017 01:16:24 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 217637] One TCP connection accepted TWO times
Date: Wed, 09 Aug 2017 01:16:22 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords: needs-qa
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jtl@freebsd.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: tuexen@freebsd.org
X-Bugzilla-Flags: mfc-stable10? mfc-stable11+
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-217637-2472-kJPzrIEvw3@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217637-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-217637-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: Wed, 09 Aug 2017 01:16:24 -0000

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

Jonathan T. Looney <jtl@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jtl@freebsd.org

--- Comment #89 from Jonathan T. Looney <jtl@freebsd.org> ---
FWIW, I have created a patch to address the behavior reported in comment #8=
7.
It maintains the RFC-compliant behavior of sending ACKs, but rate limits th=
em.
This isn't perfect, but seems better (to me) than either of the extreme
alternatives (drop every packet or ACK every packet). I'd be curious to have
someone try this and see if it provides effective mitigation.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=