Skip to content
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

Support monitoring wireguard events #1770

Open
ciarand opened this issue Sep 1, 2021 · 2 comments
Open

Support monitoring wireguard events #1770

ciarand opened this issue Sep 1, 2021 · 2 comments

Comments

@ciarand
Copy link

ciarand commented Sep 1, 2021

I have a wireguard network with two defined peers. I was hoping to use sysdig to examine the traffic (even if it's just "received X bytes from peer with address Y"). Unfortunately I haven't been able to get sysdig to do anything except ignore these connections. Tcpdump works as expected.

Here's what I tried (all examples running from the "server" that forwards incoming traffic from the remote "client" peer):

$ sysdig 'evt.is_io=true'
# (nothing relevant gets printed here)

On the other hand, tcpdump -i any 'src ${MY_PEER_IP}' does print the expected events. And because tcpdump produces I/O events you can see where sysdig is missing these packets:

$ sysdig 'evt.is_io=true'
15270 16:40:45.023115699 1 tcpdump (1503) < write res=89 data=16:40:44.952576 IP
example.com > ${MY_PEER_IP}53386: 27145 NXDomain 0/ 

Is this somehow related to sysdig not being able to monitor the in-kernel wireguard implementation? Is there a magic set of flags I can provide sysdig for it to be able to do the same thing tcpdump can?

@ciarand
Copy link
Author

ciarand commented Sep 1, 2021

alternatively: is this supposed to work and I have just made some sort of mistake configuring my system that is preventing sysdig from doing its thing?

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Feb 22, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 2, 2023
@therealbobo therealbobo reopened this Mar 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants