Networking & Firewall (Ss/Netstat/Iptables/Nftables/Curl)
Stop losing your mind over why your local service is totally invisible to the network
🧩 The Challenge
Spent half a morning yesterday wondering why my dev database wouldn’t accept incoming traffic even though I knew the port was open. Turns out the service was happily listening on 127.0.0.1 while I was trying to hammer it from a separate container across the virtual bridge.
đź’ˇ The Fix
Use the numeric and process flags on ss to actually see which interface your socket is bound to. It saves you from staring at a list of connections that tell you nothing about the local binding.
ss -tulpn | grep LISTEN⚙️ Why It Works
By flipping those flags, you get the actual PID paired with the local address, which instantly reveals if you accidentally bound to localhost instead of the public IP or 0.0.0.0. Looking at the local address column is usually the “aha!” moment when you realize why your firewall rules were doing nothing.
🚀 Pro-Tip: Alias this to ss-listen in your .bashrc and stop typing the flags every single time you’re debugging connectivity.
Linux Tips & Tricks | © ngelinux.com | 10/30/2026