Comments on: 3 Ways to Find Out Which Process Listening on a Particular Port

By: Jerammy

Jerammy — Tue, 05 Oct 2021 14:42:12 +0000

In the topic, there isn’t a solution to find a kernel-level service/program listening to a specific port.

In my case, it was a wireguard service like the solution that i have found here https://serverfault.com/questions/1078483/how-to-find-out-what-service-is-listening-on-a-specific-port-of-a-ubuntu-server

By: llutz

llutz — Fri, 17 Sep 2021 06:49:50 +0000

There is ss too, like "ss -tlpn port 80".

By: Sergio K

Sergio K — Sun, 04 Jul 2021 22:59:58 +0000

-w works with ":::80" but misses "0.0.0.0:80". Using ":80 " (with blank) works. Example: netstat -ltnp | grep -E ':80 |:443 '

By: Aaron Kili

Aaron Kili — Mon, 30 Sep 2019 05:22:53 +0000

In reply to Jason.

@Jason

Many thanks for sharing your experience from the embedded Linux side of it.

By: Jason

Jason — Fri, 27 Sep 2019 15:07:15 +0000

The hard way: on an embedded Linux 2.6 device, with read-only filesystem, without `lsof` or `fuser` binaries, where netstat exists, but '-p' option is invalid, you can `cat /proc/net/tcp` and see several 'local_address' 00000000:####, where #### was the listening port in Hex. In the same row under 'inode' column you can see the FD#, and correlate that to /proc//fd/N (each N symlinks to socket:[FD#] or /dev/null).