Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-users: [Wireshark-users] WS version 1.2.0 - TCP Stream Index

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Alex Lee <Alex.Lee@xxxxxxxxxxxx>
Date: Mon, 6 Jul 2009 10:14:47 -0700

Hi Wireshark Community –

 

I just recently upgraded my WS to 1.2.0 and when I do look at traces, I tend to “follow a TCP stream” and typically cut/paste the actual stream _expression_ so that others can view the trace and cut/paste the stream I was referring to.

 

It seems in this new version, it lists stream #’s, for example “tcp.stream eq 2” – I figure this means the second TCP stream, which is great but I prefer the old method where a “follow tcp stream” resulted in the actual _expression_ filter but I can’t seemingly find that option (if it does exist). Any help?

 

Alex

 

  • Follow-Ups:
    • Re: [Wireshark-users] WS version 1.2.0 - TCP Stream Index
      • From: Sake Blok
  • Prev by Date: Re: [Wireshark-users] (no subject)
  • Next by Date: [Wireshark-users] should Tshark use both the header and payload of MPEG transport stream packet to calculate jitter, delay, packet loss and bandwidth?
  • Previous by thread: [Wireshark-users] Hansang's Sharkfest Presentation (with answers)
  • Next by thread: Re: [Wireshark-users] WS version 1.2.0 - TCP Stream Index
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation