Wireshark-bugs: [Wireshark-bugs] [Bug 12383] The stream number in tshark's "-z follow, tcp, <str
Date: Sun, 01 May 2016 01:53:40 +0000

changed bug 12383


What Removed Added
Status UNCONFIRMED CONFIRMED
CC   mmann78@netscape.net
Ever confirmed   1
Severity Major Normal

Comment # 1 on bug 12383 from
This behavior isn't specific to TShark.  The TCP dissector is the one starting
the numbering streams at 0, so Wireshark will show tcp.stream == 0 on its
Follow TCP Stream dialog.  Don't have a strong opinion on if code or
documentation should change.

Code would be just changing tcp_stream_count = 1 in tcp_init(), MPTCP should
probably follow suit.

But also not that UDP should also be changed to match (it is also 0-origin).


You are receiving this mail because:
  • You are watching all bug changes.