Wireshark 3.6 contains code to dissect it.
If it's not dissecting it in your capture, either the frame isn't properly formed or there's a bug in the dissector.
If you want us to determine what it is, you must open an issue on GitLab, and attach a capture showing the problem, as Alexis La Goutte and @grahamb have suggested. If you've already opened an issue, please link to it
Asked: 2021-11-22 16:11:27 +0000
Seen: 179 times
Last updated: Nov 24 '21
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
I saw it on 3.6.0. Thanks
We don't close "answered" questions here, we just accept the answer which I've done for you.
Hi,
can you open an issue with a pcap ?
Issues can be opened at the Wireshark GitLab instance.
And that's not an answer in any case, it's just an indication of the release in which it was found (which is useful information - 3.4.x doesn't include code to dissect it, so if it was 3.4.x the answer is "yes, it can support it, and does in 3.6.0", but, as it's 3.6.0, it's either "yes, it can support it, but the code to support it in 3.6.0 might have a bug").