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

After capturing traffic and selecting all RTP streams then selecting a packet. The find reverse button no longer finds the reverse part of the stream. Why is this? is there a new step? It worked on older versions of Wireshark. Thanks for any help!

asked 28 Sep '16, 08:25

Nugget_59's gravatar image

accept rate: 0%

Does the same capture still work in an older version, i.e. is the issue with the capture rather than the newer version?

(28 Sep '16, 08:27) grahamb ♦

Yes it works with the capture on older version. The older version of WS will allow you to click find reverse and it then highlights the reverse stream and then you can analyze both streams simultaneously. The newer version of WS. nothing happens when you click find reverse.

(28 Sep '16, 08:32) Nugget_59

Same case here, worth filing a bug.

(28 Sep '16, 08:34) sindy

Just joined for this one issue. Where do I file bug report?

(28 Sep '16, 08:35) Nugget_59

The Wireshark Bugzilla, noting the information on the wiki page about submitting bug reports.

(28 Sep '16, 08:45) grahamb ♦
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: 28 Sep '16, 08:25

question was seen: 1,109 times

last updated: 28 Sep '16, 08:45

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