Skip to content

Stop using String names for LinkLayer/DLT types #38

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 12, 2021
Merged

Conversation

synfinatic
Copy link
Owner

Finally understood what was going on... TL;DR: gopacket/layers.LinkType
is kinda fubar because DLT != Linktype.

For more context: https://www.tcpdump.org/linktypes.html

Fixes #37

@synfinatic synfinatic force-pushed the raw-dlt-fix branch 3 times, most recently from a54f37f to 73d00c9 Compare October 21, 2020 05:14
@synfinatic
Copy link
Owner Author

been holding off on merging this.... really should see if I can fix it upstream in gopacket.

@synfinatic
Copy link
Owner Author

been holding off on merging this.... really should see if I can fix it upstream in gopacket.

Ugh, this is even more complicated than I originally understood. So many abstraction layers! Honestly, I really don't understand the whole point of that. Anyways, I'm not sure if there is a "fix" upstream or what. May need to look at this from a different perspective.

Finally understood what was going on... TL;DR: gopacket/layers.LinkType
is kinda fubar because DLT != Linktype.

For more context: https://www.tcpdump.org/linktypes.html

Fixes #37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Figure out & fix the LinkLayer issue with Raw
1 participant