Course Home
CPSC 341 - Wireshark Traceroute Lab
Earl Rodd

Overview

We will examine how "traceroute" works. This lab can be done on a lab machine or your own machine. You do not need to print the trace. Just answer the questions on this handout and turn it in.

Note that the returned ICMP messages often contain the IP and UDP headers from the original request. This helps in matching them up.

Lab Instructions and questions

  1. Stop the browser to be sure we do not have stray traffic.

  2. Start Wireshark

  3. Do a traceroute to a DNS server at an ISP (4.2.2.2). Use these options: Windows: tracert -d 4.2.2.2 LINUX: traceroute -n -q1 4.2.2.2 Note: the "-d" or "-n" parameter tells traceroute to not do a reverse DNS lookup on all the IP addresses. Otherwise, our trace will be littered with DNS requests.
    Note: The q1 parameter (LINUX only) tells traceroute to send just one UDP packet to each hop rather than the default of 3. This makes the trace easier to work with. With Windows, you will see 3 packets to each router along the path.

  4. Stop Wireshark

  5. Examine all of the UDP packets from your host to 4.2.2.2.

  6. Answer these general questions:

  7. Questions about returned ICMP datagrams.

  8. Questions about the entire flow.