cilium/pwru

Packet, where are you? -- eBPF-based Linux kernel networking debugger

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 18th, 2026
Created on October 12th, 2021
Open Issues & Pull Requests: 39 (+0)
GitHub issues: Enabled
Number of forks: 229
Total Stargazers: 3,829 (+0)
Total Subscribers: 29 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.2 days
Mean response time: 50.2 days
90th percentile: 137.7 days
Tracked items: 53

Most active contributors

Sign in to see contributor activity.

How this project is maintained

67% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Three people close 85% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 27
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 514 days
Stale 30+ days: 25
Stale 90+ days: 19

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (9)
  • bug (7)
  • enhancement (7)
  • good first issue (6)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

pwru is an eBPF-based Linux kernel networking debugger that traces packet flow through the kernel network stack.

The tool addresses the challenge of understanding where packets go and why they behave unexpectedly within the Linux kernel. It uses eBPF programs to instrument the kernel at multiple points in the networking path, allowing developers to observe packet movement in real time without modifying kernel code or restarting the system. By attaching to kernel functions and tracepoints, pwru captures detailed information about how packets traverse the network stack, making it possible to diagnose connectivity issues, performance problems, and unexpected packet drops.

Developers working on Linux networking, kernel debugging, or container networking should consider pwru when they need visibility into kernel-level packet handling. It suits projects where traditional packet capture tools like tcpdump provide insufficient detail about what happens inside the kernel, or where the problem manifests as packets disappearing or behaving unexpectedly at the kernel level. The tool is particularly valuable for those running containerized workloads or complex networking setups where kernel-level issues are difficult to isolate.

The project shows active development with regular commits addressing bug fixes and feature improvements. The codebase demonstrates attention to code quality through consistent updates and refinements to the eBPF instrumentation logic. Development activity reflects ongoing maintenance and responsiveness to issues, with changes focused on improving the reliability and accuracy of packet tracing across different kernel versions and networking scenarios.