pwru
bpfcov
Our great sponsors
| pwru | bpfcov | |
|---|---|---|
| 7 | 5 | |
| 2,464 | 121 | |
| 6.9% | 3.3% | |
| 9.1 | 0.0 | |
| 1 day ago | about 2 years ago | |
| C | C | |
| Apache License 2.0 | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pwru
- GitHub - cilium/pwru: Packet, where are you? -- eBPF-based Linux kernel networking debugger
- cilium/pwru: Packet, where are you? -- eBPF-based Linux kernel networking debugger
-
Packet, where are you? – eBPF-based Linux kernel networking debugger
if you have a recent enough kernel, this change https://github.com/cilium/pwru/pull/148 means that it will print the reason the packet was dropped in the output - see https://lwn.net/Articles/885729/
There's a whole heap of reasons a packet can be dropped:
-
A list of new(ish) command line tools – Julia Evans
[pwru](https://github.com/cilium/pwru) is a fun new tool from the Cilium folks for tracing network packets in the kernel. Like tcpdump but it shows you the full path including kernel syscalls. Lets you debug much deeper than "when the packet gets to this port it gets dropped".
-
Better visibility into Linux packet-dropping decisions
I recently came across another useful utility for debugging unexpected packet drops - PWRU[0] (Packet, Where Are You) by Cilium.
It uses eBPF to try to trace the path of the packet through the kernel. Haven't needed to use it yet, but it could have saved me a lot of trouble in the past.
[0]: https://github.com/cilium/pwru
bpfcov
- Bpfcov – source-based code coverage for eBPF programs
- Show HN: Bpfcov – source-based code coverage for eBPF programs
- Coverage for eBPF programs
-
Source-based code coverage for eBPF programs
Lazyweb: the LLVM pass (libBPFCov.so) and the CLI source code is at: https://github.com/elastic/bpfcov
- elastic/bpfcov: Source-code based coverage for eBPF programs actually running in the Linux kernel
What are some alternatives?
parca-agent - eBPF based always-on profiler auto-discovering targets in Kubernetes and systemd, zero code changes or restarts needed!
adorad - Fast, Expressive, & High-Performance Programming Language for those who dare
fsmon - monitor filesystem on iOS / OS X / Android / FirefoxOS / Linux
npf - NPF: packet filter with stateful inspection, NAT, IP sets, etc.
libbpf - Automated upstream mirror for libbpf stand-alone build.
redcanary-ebpf-sensor - Red Canary's eBPF Sensor
glow - Render markdown on the CLI, with pizzazz! 💅🏻
traffico - Shape your traffic the BPF way
up - Ultimate Plumber is a tool for writing Linux pipes with instant live preview
checkedc - Checked C is an extension to C that lets programmers write C code that is guaranteed by the compiler to be type-safe. The goal is to let people easily make their existing C code type-safe and eliminate entire classes of errors. Checked C does not address use-after-free errors. This repo has a wiki for Checked C, sample code, the specification, and test code.
lnav - Log file navigator
bmc-cache - In-kernel cache based on eBPF.