Update gopacket vendor from google to gopacket #43
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
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.
Hello,
While playing a recent AD CTF, we used tcpdump to log the network traffic from our vulnbox. When running
tcpdump -i any, it outputs packets with theLinkTypeSLL2 (Linux "cooked" capture encapsulation v2), which is not supported by Google's gopacket library. As a result, Tulip was unable to process the packets.Since Google's gopacket library hasn't seen any commits in two years, a fork has been created to continue maintaining this library.
Support for SLL2 has been implemented in gopacket and merged into the fork.
This pull request switches the gopacket library to the current fork, adding SLL2 support to Tulip. The change was tested with pcaps.
Best regards
Markus