[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-users
Subject:    [Wireshark-users] why a tcp stream is split into many tcp flows
From:       esolve esolve <esolvepolito () gmail ! com>
Date:       2012-11-07 11:54:58
Message-ID: CAEYCsr49d-N4POKFNYEmNR31M5rnoiF8-9qvid9LMxB-+6J50w () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I use tcpdump to capture video streaming and then use tcpflow to parse the
captured packets. I notice that a tcp stream is split into many tcp flows,
for the tcp flow names, for example, a tcp stream with receiver port 50552
is split into 11 flows, and in the names, the port number is changed to
50552, 50552c1, 50552c2, 50552c3,....etc

what is the reason for this?

[Attachment #5 (text/html)]

I use tcpdump to capture video streaming and then use tcpflow to parse 
the captured packets. I notice that a tcp stream is split into many tcp 
flows, for the tcp flow names, for example, a tcp stream with receiver 
port  50552 is split into 11 flows, and in the names, the port number is
 changed to  50552,  50552c1,  50552c2,  50552c3,....etc<br>
<br>what is the reason for this? <br>


___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@wireshark.org?subject=unsubscribe

[prev in list] [next in list] [prev in thread] [next in thread]