graymon
graymon
I hope this helps me understand how Cilium CT works. Even after 18 months since onboarding, CT is still a mystery to me.
I labelled this "don't merge' because it's on the top of https://github.com/cilium/pwru/pull/477 which is pending.
https://github.com/daeuniverse/dae/pull/600 把 direct access 滚回去了，所以不再需要这个了。
@linglilongyi Hi thanks for asking! I was wondering if calling syscall (wrapped by 3rd party library of course) rather than relying on external commands is a good idea. For example,...
@linglilongyi netfilter is notorious for the lack of programmable APIs: > 4.5 Is there an C/C++ API for adding/removing rules? > The answer unfortunately is: No. https://www.netfilter.org/documentation/FAQ/netfilter-faq-4.html#ss4.5 So feel free...
@linglilongyi Currently `dae trace` dumps huge amount of packets, most of them are not necessary. In most cases, we care about packets that are dropped by kernel, aka processed by...
@linglilongyi `dae trace` prints packets' (skbs') lifetime, `--drop-only` is supposed to print the lifetime of dropped packet. It's more like: ``` if dropOnly && NearestSymbol() == "kfree_skb_reason" { droppedSkbEvents :=...
@sachintiptur By default, pwru traces events from skb functions, such as `ip_rcv`. When setting `--filter-trace-xdp`, pwru **also** traces events from xdp bpf prog; when settings `--filter-trace-tc`, pwru **also** traces events...
Is it possible to unwind stack (to get stackid) in native/offload XDP? Honestly I don't even know if `bpf_get_stackid()` can be used in XDP, https://docs.ebpf.io/linux/helper-function/bpf_get_stackid/ doesn't show BPF_PROG_TYPE_XDP for this...