-
Notifications
You must be signed in to change notification settings - Fork 180
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
Proposal: introduce --filter-trace-tunnel-type and --filter-trace-tunnel-pcap #450
Comments
I like this, thank you! Just to be clear,
① filters inner packet, from Since a vxlan can't have an outer icmp, no traffic will be captured. |
Oh, what are we missing here? It's the bool logic between ① and ②. It should be "① or ②" by default. And use |
What is the use case of "or"? I think "and" is more useful to catch "out ip 172.1.1.1 and vxlan and inner ip 10.1.1.1" |
This seems better for me. Why not use "and vxlan", "or vxlan" instead of Same for |
Was thinking about this. I have an ambiguous feeling of cool and dangerous about what we are doing here: extend pcap filter. |
As for VxLAN env, it'll be really convenient to trace skb with filtering inner-VxLAN packet info with pcap-filter, as pcap-filter does not support filtering inner-VxLAN packet info directly.
To achieve it, let me introduce
--filter-trace-tunnel-type
and--filter-trace-tunnel-pcap
options to accept a pcap-filter expr to filter inner-VxLAN packet info.$ sudo pwru --filter-trace-tunnel-type vxlan --filter-trace-tunnel-pcap 'host 1.1.1.1 and icmp' host 1.1.1.1 and icmp
Then,
pwru
is able to trace skb before decapsulating VxLAN and after encapsulating VxLAN.And
--filter-track-skb
does not work well before decapsulating VxLAN.Furthermore,
--filter-trace-tunnel-type
should support geneve, ipip and so on.TODOs:
--filter-trace-tunnel-type vxlan
--filter-trace-tunnel-type geneve
--filter-trace-tunnel-type ipip
The text was updated successfully, but these errors were encountered: