Fix Wireshark parsing logic #671
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Merged, thanks! |
|
@rotu In case you don't get notifications from mavlink/mavlink, I was wondering if you could advise on mavlink/mavlink#1978 (as you were the last person to modify the Wirshark plugin, and will know a lot more than I do)! If not, is there anyone else you recommend we might ask for help? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, fields sometimes showed the wrong value, byte offsets were from the beginning of the IP packet, and truncated fields were omitted.
Now, the correct value is shown, byte offsets are from the beginning of the MAVLink packet, and truncated values are kept.