Networking & Firewall (Ss/Netstat/Iptables/Nftables/Curl)

Stop wondering why your application is blind to remote traffic

🧩 The Challenge

You’ve triple-checked your firewall rules and the app config, but the server is just dropping connections into the void. I’ve spent way too many Friday nights staring at these logs only to realize the traffic was hitting a local loopback instead of the wire.

💡 The Fix

Use a specific flag to force your socket queries to show the actual interface bound to each connection. It saves you from guessing which IP the process is actually listening on.

ss -tulpn4

⚙️ Why It Works

Adding the n flag stops the system from wasting time performing reverse DNS lookups on every single port, while the 4 flag filters out all the IPv6 noise that usually clutters up the output.

🚀 Pro-Tip: Pipe it into grep to instantly see if your service is actually bound to 0.0.0.0 or just locked to localhost.

Linux Tips & Tricks | © ngelinux.com | 7/25/2026