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
bpf: improve trace events in SNAT path #28723
bpf: improve trace events in SNAT path #28723
Conversation
julianwiedmann
commented
Oct 23, 2023
•
edited
edited
0b316d7
to
d5164e0
Compare
/test |
This pull request has been automatically marked as stale because it |
This pull request has not seen any activity since it was marked stale. |
@julianwiedmann should we add a note in |
I'll need to refresh my memory, but pretty sure that we can wire up the IPv6 path even today :). We'll populate the |
d5164e0
to
5e6036d
Compare
5e6036d
to
52ee0ba
Compare
/test |
@kaworu I rebased and added the IPv6 handling. Also making sure that the Would you have a moment to double-check this still works as expected? |
When applying SNAT to a packet, also report the original source address in the subsequent trace event. This helps to associate the internal and external view of a connection. We use the `orig_addr` field in the trace event, which was originally introduced back with b3aa583 ("bpf: Report original source IP in TRACE_TO_LXC") Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
This helps to clarify the exact origin of a TO_NETWORK trace event. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
52ee0ba
to
f40f274
Compare
👋 Seems like we might need some extra commits from #26674 for 1.14 backport. |