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.
0

How do I get help with and/or report a dissector problem?

  • retag add tags

I am using version 3.4.0 of wireshark, 64-bits, running on a windows10 computer. I also have a TAP which provides me with all the packet data, from the beginning of the preamble to the end of the FCS. I have pcaps that include frames to which preemption has been applied (Clause 99 of IEEE 802.3-2018 and 6.7.1, 6.7.2 and 8.6.8 of IEEE 802.1Q-2018). The current dissector seems to have problems correctly reporting the express, frames to which preemption has been applied, particularly the fragments.... For example, the dissector recognizes the first fragment and provides information on this fragment, such as a good mCRC and that the frame has an SMD-S3. The second fragment, seems to be partially recognized, but it reports a Bad CRC, when there is a good mCRC. It lists the frame as a 2nd fragment, and even has all the data for the two fragments. For the third and last fragment, there is reported a Bad mCRC when there is in fact a good CRC. This fragment also seems to have lost the fact that it belongs to the other preceeding fragments. What can be done to fix this? Can I help? -Paul Andrews

pandrews's avatar
1
pandrews
asked 2021-05-14 20:52:12 +0000
edit flag offensive 0 remove flag close merge delete

Comments

Can you provider a sample capture shared somewhere like dropbox or other online file share?

Chuckc's avatar Chuckc (2021-05-14 21:20:14 +0000) edit
add a comment see more comments

1 Answer

0

There are a couple of things to look at:

  1. Try the latest stable version, currently 3.4.5, available from the download page.
  2. Try the latest development version, 3.5.0, available from the automated build area.

If the problem is still present raise an Issue at the Wireshark GitLab site,attaching a capture to the issue.

grahamb's avatar
23.8k
grahamb
answered 2021-05-14 21:26:16 +0000
edit flag offensive 0 remove flag delete link

Comments

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