This is our old Q&A Site. Please post any new questions and answers at

The new interface has a different behaviour for hiding/filtering tcp streams and for my usage, it's a lot less useful. Si I'm looking to see if I can configure the new interface to "do the right thing".

My scenario: We have a client-server set up where the client will send a series of http requests, and get responses. A session consists of multiple http request/responses, and there may be several sessions.

When I'm using wireshark, I look at one request/response pair (or maybe several, if persistent connections happen). Once I'm done with that, I want to hide it and move on to the next.

Old interface had "filter out this stream". New one has "hide this stream". But the old one kept hiding previous streams I'd also filtered out, the new one just hides the current one, and any previous ones I'd hidden now reappear.

Which is a pain, since they're "in the past", and I don't want to see them again. I want to move on to the next request/response.

Can I configure "Hide this stream" to still hide previously hidden streams? Shouldn't this be the default anyway? Is it ever useful just to hide one stream at a time?

asked 08 Dec '15, 12:07

The%20Archetypal%20Paul's gravatar image

The Archetyp...
accept rate: 0%

Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 08 Dec '15, 12:07

question was seen: 7,241 times

last updated: 08 Dec '15, 12:07

p​o​w​e​r​e​d by O​S​Q​A