From owner-freebsd-net@freebsd.org  Mon Mar 20 16:29:18 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 4B69AD14BE0
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Mon, 20 Mar 2017 16:29:18 +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 308E4185C
 for <freebsd-net@FreeBSD.org>; Mon, 20 Mar 2017 16:29:18 +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 v2KGTH5s078548
 for <freebsd-net@FreeBSD.org>; Mon, 20 Mar 2017 16:29:18 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: Mon, 20 Mar 2017 16:29:18 +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: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: slw@zxy.spb.ru
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-217637-2472-W0brqcRBqR@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: Mon, 20 Mar 2017 16:29:18 -0000

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

--- Comment #63 from slw@zxy.spb.ru ---
(In reply to Michael Tuexen from comment #62)

Accepted RST can cause silent, immediatly closing connection by client. No
acknowledged will be sent to server (in case of serevr responce will be
delivered to client) and server will be retransmit response until also got =
RST.
In case of responce not delivered to client responce will be lost and no ch=
ance
to deleivered.

Sending RST is ok in case RST accepted and processed after client sent ACK =
so
server FIN (FIN, not server data). Need test this on real clients (Linux,
windows, android and iOS).

Server can do graceful termination of this TCP connection and no reason to
don't do this (application do gracefull close and only rare combination of
packet loss case this behaviour).

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