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

pack_addr supports parsing AF_NETLINK protocol #1494

Open
lclin56 opened this issue Nov 21, 2023 · 5 comments
Open

pack_addr supports parsing AF_NETLINK protocol #1494

lclin56 opened this issue Nov 21, 2023 · 5 comments
Labels
kind/feature New feature or request
Milestone

Comments

@lclin56
Copy link

lclin56 commented Nov 21, 2023

Motivation

I found that the parsing of pack_addr only supports protocols such as AF_INET, AF_INET6, and AF_UNIX. When I need to track syscalls related to NETLINK protocol, the current version does not support AF_NETLINK. So when I try to use pack_addr to parse NETLINK protocol, I encounter difficulties.

Feature

I hope to add support for AF_NETLINK protocol in pack_addr, so that I can correctly parse and track syscalls related to NETLINK protocol.

Alternatives

I could consider using other tools or libraries to obtain syscall information related to NETLINK protocol. However, I prefer to implement this feature directly in pack_addr because it allows me better control over the parsing process and a better understanding of the behavior of NETLINK protocol.

Additional context

I need to track syscalls related to NETLINK protocol because I want to better understand and manage network-related system calls. I hope that pack_addr can add support for AF_NETLINK protocol, so that I can more easily parse and track these calls.

@lclin56 lclin56 added the kind/feature New feature or request label Nov 21, 2023
@Andreagit97
Copy link
Member

hi @lclin56 thank you for reporting! This seems a valuable feature request, we will try to find some time to implement it!

@Andreagit97 Andreagit97 added this to the TBD milestone Nov 22, 2023
@ecbadeaux
Copy link
Contributor

I'll try to work on this.

@poiana
Copy link
Contributor

poiana commented Mar 29, 2024

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

@poiana
Copy link
Contributor

poiana commented Apr 28, 2024

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

@Andreagit97
Copy link
Member

/remove-lifecycle rotten

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants