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

Stop letting your curl requests fail without knowing which interface they chose

🧩 The Challenge

Dealing with multihomed servers is a nightmare when you’re trying to debug an outbound API call that keeps hitting a black hole. You know it’s leaving the box, but you have no clue if it’s trying to exit through the VPN tunnel or your primary uplink.

💡 The Fix

Use curl’s interface flag to pin your request to a specific local IP or device. It forces the kernel to ignore the routing table’s usual whims and use the exact NIC you need to test.

curl --interface eth1 https://api.internal-service.com/health

⚙️ Why It Works

Setting this flag overrides the default routing logic by binding the socket directly to the address associated with your chosen interface. It’s the fastest way to confirm if a specific path actually has connectivity without changing global routes.

🚀 Pro-Tip: Combine this with -v to see the local address in the verbose output headers before the handshake even starts.

Linux Tips & Tricks | © ngelinux.com | 9/29/2026