-
Notifications
You must be signed in to change notification settings - Fork 189
Track skb by address #194
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
Track skb by address #194
Conversation
This commit introduces a bpf map `skb_addresses` to store matched skbs, so the consequent skbs whose addresses can be found in the map are seen as matched ones without filter checks. Signed-off-by: Zhichuan Liang <gray.liang@isovalent.com>
a7c509f
to
53d648c
Compare
Now pwru can clearly see the full process of IPsec:
First it's (And I changed perf_output to bpf_queue locally to avoid event loss) |
This is super useful, thanks for working on this! Also, I think it would be nice to have a --follow-skb-clones option where we add new addresses to that tracker map whenever there was a clone or copy of the skb in order to get visibility where their paths go. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Minor suggestion.
Created #200 to track Daniel's suggestion. |
Signed-off-by: Zhichuan Liang <gray.liang@isovalent.com>
53d648c
to
7048cd5
Compare
This PR introduces a bpf map to store matched skb addresses, so for any skb whose address can be found in the map, we see it a matched one without filter check.
This can be useful to observe NAT-ed / encrypted / encapsulated traffic.
Fixes: #84
Signed-off-by: Zhichuan Liang gray.liang@isovalent.com