pwru VS fselect

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:

[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".

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

Shameless plug: a tool I wrote to manage downloads directory :)

https://github.com/jhspetersson/fselect

Mine alternatives/helpers bringing a new extra functionality are the following: - https://github.com/facebook/pathpicker/ - Facebook PathPicker is a simple command line tool that solves the perpetual problem of selecting files out of bash output. - https://github.com/jhspetersson/fselect - Find files with SQL-like queries - https://github.com/junegunn/fzf - fzf is a general-purpose command-line fuzzy finder.

I really like fselect, which I use more than fd

https://github.com/jhspetersson/fselect

A tiny tool I wrote to search within file piles (mostly unsorted downloads, torrents, and such). I could never remember `find` options, and more advanced queries are a pain. Now one can use some kind of SQL flavor to get the job done.

fselect - Command-line tool to search files with SQL-like queries.