NETOBSERV-2143 improve pcapng implementation#293
Conversation
|
Skipping CI for Draft Pull Request. |
go.mod
Outdated
| sigs.k8s.io/yaml v1.4.0 // indirect | ||
| ) | ||
|
|
||
| replace github.com/google/gopacket v1.1.19 => github.com/GameFabric/sts-pkg-gopacket v0.0.0-20230307093013-7b513277b714 |
There was a problem hiding this comment.
This points on an open PR which never been merged: google/gopacket#1076
Let me know if you prefer to have our own implementation in netobserv org
There was a problem hiding this comment.
is there a reason to use google/gopacket rather than gopacket/gopacket? I kind of remember in the ebpf agent we switch to the latter, can't remember the exact reason, but I think gopacket/gopacket was more up to date.
And it sounds like it also have ngread: https://github.com/search?q=repo%3Agopacket%2Fgopacket%20ngread&type=code
There was a problem hiding this comment.
I compared GameFabric/sts-pkg-gopacket to gopacket/gopacket and it doesn't contains the comments capabilities I'm looking for:
So I need to keep the replace part wich forces me to keep the google one since the modules been renamed between the two:
module declares its path as: github.com/google/gopacket
but was required as: github.com/gopacket/gopacket
Unless we want to have our own implementation in netobserv repos as mentionned before ?
There was a problem hiding this comment.
So I think we need to fork it. The replacement used here seems to be from 2023, could be pretty bad for security...
There was a problem hiding this comment.
oh it seems like the main branch actually contains something for comments !
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #293 +/- ##
==========================================
+ Coverage 22.60% 22.83% +0.22%
==========================================
Files 14 14
Lines 1451 1454 +3
==========================================
+ Hits 328 332 +4
Misses 1099 1099
+ Partials 24 23 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
| // scanner returns on exit request | ||
| os.Exit(0) | ||
| }() | ||
| go scanner() |
There was a problem hiding this comment.
scanner return code seems always ignored, if that's on purpose I'd suggest to make it not returning anything then
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
nice! |

Description
Rely on comments to add enrichment to the pcap:

Also fixed the end capture behavior
Dependencies
n/a
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.