How to Troubleshoot Network Connectivity in Linux? (ping & traceroute)

First use ping to check the connectivity: If localhost succeeds, the local stack is normal. If the gateway fails, check the physical connection or routing. If the external IP fails, check the DNS. Then use traceroute to locate the interrupted node. The timeout point is the fault point.

Start with ping to check basic reachability — if it fails, the issue is likely local or along the path. Then use traceroute to identify exactly where packets stop flowing.

Check Local Network Stack with ping

Run ping -c 4 127.0.0.1 to verify your system's network stack is working. If this fails, the problem is internal — check if networking services are running or if firewall rules are blocking loopback traffic.

• If localhost ping works but ping -c 4 8.8.8.8 fails, your machine isn't reaching the gateway or beyond — check physical connection, IP configuration ( ip a ), and default route ( ip r )
• If external ping works but domain names don't resolve, the issue is DNS — test with nslookup google.com or dig google.com

Trace the Path with traceroute

Use traceroute google.com (or mtr google.com for real-time insight) to see each hop from your machine to the destination. Look for timeouts (“* * *”) — that indicates where the path breaks.

• Timeouts at hop 1 usually mean your local gateway isn't responding — check router power, cables, or Wi-Fi signal
• Timeouts starting at hop 2 or 3 often point to ISP-side issues or misconfigured intermediate routers
• If all hops respond until the final destination, the target host may be blocking ICMP (common for security) — try curl -I http://example.com instead

Interpret Common ping & traceroute Outputs

"Destination Host Unreachable" means a local router or interface can't forward the packet — often due to missing route or interface down. "Network is unreachable" suggests no default route exists or interface is down.

• ping: unknown host example.com → DNS failure, not network failure
• “Request timeout” after several hops in traceroute → packet loss or filtering at that hop
• Consistent high latency (>100ms) on one hop → possible congestion or poor routing

Quick Diagnostic Flow

Follow this order before diving deeper:

• Ping localhost → confirms local stack
• Ping your default gateway (eg, ping 192.168.1.1 ) → confirms LAN connectivity
• Ping public IP (eg, ping 8.8.8.8 ) → checks Internet reachability
• Ping domain name → tests DNS resolution
• Run traceroute only if step 3 fails or behaves inconsistently

Basically, ping tells you *if* something is reachable — traceroute tells you *where* it stops. Combine them, and you'll narrow most connectivity problems fast.

The above is the detailed content of How to Troubleshoot Network Connectivity in Linux? (ping & traceroute). For more information, please follow other related articles on the PHP Chinese website!