 | 1 | initial version |
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
| | 2 | No.2 Revision |
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 @alexislagoutte and @grahamb have suggested. If you've already opened an issue, please link to it
| | 3 | No.3 Revision |
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 @alexislagoutte @alexis and @grahamb have suggested. If you've already opened an issue, please link to it
| | 4 | No.4 Revision |
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 Alexis La Goutte and @grahamb have suggested. If you've already opened an issue, please link to it
