Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Mar 2017 12:04:13 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-net@FreeBSD.org
Subject:   [Bug 217637] One TCP connection accepted TWO times
Message-ID:  <bug-217637-2472-8AEpDoQMRh@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/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217637

--- Comment #14 from Michael Tuexen <tuexen@freebsd.org> ---
(In reply to Alexandre martins from comment #13)
> I want to remind you that the original client is a smartphone. The first =
time that
> I saw the problem, I made a tcpdump on the wireless box, not on the
> smartphone itself.

OK. That explains why the client has not processed TCP segments which were
reported
as received. They are just dropped between the wireless box and the smartph=
one.

> The server response may have been delayed into the wifi process (poor sig=
nal ?)
> and takes time to reach the phone (but has already been captured into the=
 pcap).
> The phone may have done a re-transmit because it thinks that the http req=
uest
> was lost.
I guess this is exactly why the client was retransmitting the complete HTTP
request.
Please note that the retransmission looks like the third message (an ACK) of
the
three way handshake. It only contains in addition some data and has the PSH=
 bit
set.
Therefore it looks like such a handshake message and the server accepts it =
and
establishes the TCP connection (again).=20

>I just managed that to reproduce it through the scapy script on the ubuntu=
 with
>a iptables configuration that drops the TCP reset.
The packetdrill script allows you to reproduce the double accept behaviour
on a FreeBSD head system. I used that to figure out why it happens.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217637-2472-8AEpDoQMRh>