First time here? Check out the FAQ!
THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
Ask Your Question
0

How do I view the details of an mmse content in v2.6.1 in the same way as they are displayed in v1.8.15?

  • retag add tags

I have been using Wireshark v1.8.15 to view Bcc data in mmse packets and they are displayed without any issues. When I try to do the same using v2.6.1 all that is displayed under MMS Message Encapsulation is "X-Mms-Message-Type: m-send-req (0x80). In v1.8.15 additional fields are displayed like X-Mms-Transaction-ID, X-Mms-MMS-Version and Bcc.

I'm hoping that it is just an adjustment to a filter or display as according to the Display Filter Reference, Mmse.bcc is still content that should be displayed.

I appreciate any assistance you can provide.

After additional testing with different versions, it appears that this change was introduced between versions 2.5.0 and 2.5.1.

pdkrause's avatar
1
pdkrause
asked 2018-06-05 16:39:16 +0000, updated 2018-06-05 17:00:10 +0000
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

1 Answer

0

You either install an automated build of 2.6.2 or wait for 2.6.2 to come out.

I'm hoping that it is just an adjustment to a filter or display as according to the Display Filter Reference, Mmse.bcc is still content that should be displayed.

Filters don't control the way packets are dissected, they control which packets, in their entirety, are displayed.

The problem there was that a test was backwards. The fix will be in the next 2.6.x, 2.4.x, and 2.2.x releases.

Guy Harris's avatar
19.9k
Guy Harris
answered 2018-06-05 23:31:15 +0000
edit flag offensive 0 remove flag delete link
more

Comments

Thank you for the update. I was pretty sure that it was not an issue with the filter, but sometimes there are options or settings that can be changed on what types of data are on display, so I wanted to rule that out first.

pdkrause's avatar pdkrause (2018-06-05 23:41:24 +0000) edit
more
  • delete

thanks for this! i was able to track down the changeset and rebuild the RPM with the patch from https://code.wireshark.org/review/git...

gitman's avatar gitman (2018-06-22 20:13:02 +0000) edit
more
  • delete
add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer