Add bidirectional packet capture#6882
Merged
antoninbas merged 1 commit intoantrea-io:mainfrom Mar 10, 2025
Merged
Conversation
Member
Author
|
@hangyan please let me know what you think about this |
antoninbas
reviewed
Dec 23, 2024
Member
Author
|
Hey @hangyan @antoninbas, I made the changes in the bpf code according to the one generated by tcpdump. When I try to test the bidirectional packet capture, it fails with this log Could you please take a look and help me identify what might be going wrong? Also, golangci-lint is giving me this error even though I have changed the |
Member
this error was reported by golangci on windows, we have a |
hangyan
reviewed
Jan 2, 2025
Member
Author
|
I’ve added the Please let me know if any adjustments are needed or if there's anything else I should update or add. Captured packetsICMP (SourceToDestination) ICMP (DestinationToSource) ICMP (Both) TCP (SourceToDestination) TCP (DestinationToSource) TCP (Both) |
hangyan
reviewed
Jan 8, 2025
antoninbas
reviewed
Jan 8, 2025
Contributor
antoninbas
left a comment
antoninbas
left a comment
There was a problem hiding this comment.
could we add an e2e test with the Both direction?
AryanBakliwal
force-pushed
the
bidirection
branch
from
7b17816 to
7eb34de
Compare
Member
Author
|
@antoninbas @hangyan I have refactored the |
antoninbas
reviewed
Jan 21, 2025
Contributor
antoninbas
left a comment
antoninbas
left a comment
There was a problem hiding this comment.
thanks for your ongoing work on this
antoninbas
reviewed
Jan 28, 2025
antoninbas
reviewed
Feb 3, 2025
hangyan
reviewed
Feb 5, 2025
Member
Author
|
@antoninbas @hangyan Changed the function and param name, and added some comments. Please let me know if there’s anything else I should take care of. |
antoninbas
added
the
action/release-note
Contributor
|
Hi @AryanBakliwal please re-base to the latest main branch and squash all your changes into one commit. Thanks. |
AryanBakliwal
force-pushed
the
bidirection
branch
2 times, most recently
from
474a382 to
4044b23
Compare
AryanBakliwal
force-pushed
the
bidirection
branch
from
4044b23 to
2df63b1
Compare
antoninbas
added
the
area/ops/packetcapture
antoninbas
reviewed
Feb 25, 2025
Contributor
antoninbas
left a comment
antoninbas
left a comment
There was a problem hiding this comment.
Some small comments but overall LGTM. Thanks for all the work and patience.
antoninbas
reviewed
Feb 27, 2025
AryanBakliwal
force-pushed
the
bidirection
branch
from
2df63b1 to
d71b417
Compare
antoninbas
previously approved these changes
Mar 6, 2025
Contributor
antoninbas
left a comment
antoninbas
left a comment
There was a problem hiding this comment.
LGTM, thanks for this great contribution and for your patience during the review process
@hangyan do you want to take another look?
Contributor
|
@AryanBakliwal I just started the Github workflows, let's see if there is any test or linting failure |
Member
sure. will do it now and give my feedback soon |
Member
|
LGTM. Thanks @AryanBakliwal |
Member
Author
|
Thank you @antoninbas and @hangyan for guiding me through this. Your support made it much easier :) |
Contributor
|
/test-all |
Contributor
|
@AryanBakliwal One if your new e2e tests has failed in CI. I'm copying the logs below for convenience. PTAL. Logs for failed test |
Member
Author
I'll look into it. |
AryanBakliwal
force-pushed
the
bidirection
branch
from
d71b417 to
f4fe82d
Compare
Member
Author
|
/test-all |
Signed-off-by: Aryan Bakliwal <aryanbakliwal12345@gmail.com>
AryanBakliwal
force-pushed
the
bidirection
branch
from
f4fe82d to
4f4ed52
Compare
Member
Author
|
/test-e2e |
Member
Author
|
@antoninbas the e2e test is passing now |
Contributor
|
/test-all |
antoninbas
approved these changes
Mar 10, 2025
| if pc.Spec.Direction == crdv1alpha1.CaptureDirectionBoth { | ||
| assert.Contains(t, []string{srcIP.String(), dstIP.String()}, ip.SrcIP.String()) | ||
| assert.Contains(t, []string{srcIP.String(), dstIP.String()}, ip.DstIP.String()) | ||
| } else { |
Contributor
There was a problem hiding this comment.
this code would be wrong for the DestinationToSource direction. Could you add a single e2e test case for the DestinationToSource direction as a follow-up PR, and update this verification function accordingly?
| if ports.SrcPort != nil { | ||
| assert.Contains(t, []int32{int32(tcp.SrcPort), int32(tcp.DstPort)}, *ports.SrcPort) | ||
| } | ||
| } else { |
This file contains hidden or 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
5 participants
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.
fixes: #6862
A new
directionfield is added to the PacketCapture CRD.Packets can now be captured from source to destination (default),
destination to source, or in both directions.
Screenshot of the
.pcapngoutput file (both directions).