pwru VS lf

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

I've tried using LF in the past, but it didn't stick. Will definitely give this a go, as I'm trying to move to an pure terminal workflow as closely as possible.

https://github.com/gokcehan/lf

Hi. fff, lf, clifm Won't say they're best or not, rather interesting and maybe worth looking at. Looked up for the z in termux's repos and it's called "zoxide" there.

in the Github page for lf under etc, you can find instruction for making such a function for bash and fish.

I recently discovered an amazing terminal file manager (lf). The package is available for most mainstream distros but not for openSUSE.

For me, the main program missing is "lf" the ranger inspired terminal file manager. 5000 stars on Github, packaged in the official repos for basically anything under the sun except Fedora and a key part in my day-to-day workflow. https://github.com/gokcehan/lf