Traceroute Test

Nerd Cafe

Step 1: Understanding traceroute (Linux/macOS) & tracert (Windows)

  • Purpose:

    • Helps track the path a packet takes from source to destination.

    • Identifies where network delays or failures occur.

  • Commands:

    • Windows: tracert [destination IP]

    • Linux/macOS: traceroute [destination IP]

Step 2: Network Setup with Static Routes

Assuming static routing is already configured, verify your routes:

Topology

Router R1:

  • This route tells R1 that to reach 192.168.3.0/24, forward packets to R2 (10.0.0.2).

Router R2:

  • First route: To reach 192.168.3.0/24, forward packets to R3 (10.0.1.2).

  • Second route: To reach 192.168.1.0/24, forward packets to R1 (10.0.0.1).

Router R3:

  • This route tells R3 that to reach 192.168.1.0/24, forward packets to R2 (10.0.1.1).

Step 3: Running tracert from PC1 to PC3

  • Each hop represents a router in the network.

  • The times in ms (milliseconds) show response delays.

Step 4: Troubleshooting with tracert

If tracert does not work or times out:

  • Verify Static Routes for R1:

  • Verify Static Routes for R2:

  • Verify Static Routes for R3:

  • Check connectivity using ping:

Keywords

Traceroute, Tracert, Static Routing, Network Troubleshooting, ICMP, Hop Count, Packet Path, Latency, Ping, Route Verification, Show IP Route, Show IP Interface Brief, Router Configuration, Network Delay, Packet Switching, Routing Table, Network Connectivity, Path Analysis, Command Prompt, Terminal, نتورک پلاس

Last updated