12.1.9 Packet Tracer – Identify Packet Flow Answers

• Recommend

Packet Tracer – Identify Packet Flow (Answers Version)

Answers Note: Red font color or gray highlights indicate text that appears in the instructor copy only.

Objectives

In this activity, you will observe packet flow in a LAN and WAN topology. You will also observe how the packet flow path may change when there is a change in the network topology.

Part 1: Verify Connectivity

Part 2: Remote LAN Network Topology

Part 3: WAN Network Topology

Background / Scenario

Packet Tracer allows the design and creation of a simulated networking topology. In this activity, you are presented with a simplified topology to observe packet flow. You will explore how packets travel through the network using the simulation mode in Packet Tracer. You will also observe the changes in packet flow when there is a change in the network topology.

Required Resources

• Latest version of Packet Tracer installed

Instructions

Part 1:  Verifying Connectivity

In this part, you will verify that you can access the other networks from devices on the Home Network.

1. Click PC0. Select the Desktop tab and open the Web Browser.
2. In the URL field, enter www.cisco.pka and press Go. Be sure to use the .pka domain, not the .com domain. It should be successful. You can click Fast Forward Time to speed up the process.
3. Repeat this for www.web.pka. It should be successful.
4. Exit the web browser when finished.

Part 2:  Remote LAN Network Topology

In this part, you will use the simulation mode in Packet Tracer to observe how packets flow through a remote LAN network.

1. Switch to Simulation mode (Shift + S). Click Show All/None to clear all the selected event list filters.
2. Click Edit Filters. Select DNS under the IPv4 tab and HTTP under Misc tab.
3. Open a web browser on PC0. Enter www.web.pka and press Go.

Question:

Predict the packet path to resolve www.web.pka to an IP address. Record your prediction.

Type your answers here.

DNS packets: PC0 > Wireless Router0 > Cable Modem0 > Cloud0 > Router5 > East > Switch0 > Switch1 > Public DNS and reverse the path back to the originator PC0.

4. Click Capture / Forward until the webpage is displayed on PC0 to view the packet flow. Click View Previous Events when prompted by the Buffer Full dialog box.

Question:

After the IP address has been resolved, which path did HTTP packets travel to display the webpage? Record your observations.

Type your answers here.

DNS packets: PC0 > Wireless Router0 > Cable Modem0 > Cloud0 > Router5 > East > Switch0 > Switch1 > Switch2 > www.web.pka and reverse the path back to the originator PC0.

5. Switch to Real time mode (Shift + R). Click the X icon in the right tool panel to select the Delete tool. Remove the link between Switch0 and Switch 1 from the Public Network to simulate a broken link. After 30 seconds, the network will learn of the broken link. You can click Fast Forward to speed up the process.
6. Select the Arrow tool above the Delete tool to de-select Delete.
7. Switch to Simulation mode (Shift + S). Open a web browser in Tablet0 and navigate to www.web.pka. You can click Auto Capture/Play to have Packet Tracer forward the packets without your interaction. You can also move the Play Slider to the right to speed up the packet forwarding.

Question:

With a broken link in the LAN, how did the path change? Record your observation.

Type your answers here.

It went through Switch 0 > Switch2 > Switch1 to reach Public DNS server.

Part 3:  WAN Network Topology

Step 1:  PC0 to websites.

1. Remaining in Simulation mode, open a web browser on PC0. Enter www.cisco.pka and press Go.

Question:

Predict the packet path to resolve www.cisco.pka to an IP address. Record your prediction.

Type your answers here.

DNS packets: PC0 > Wireless Router0 > Cable Modem0 > Cloud0 > Router5 > East > Switch0 > Switch2 > Switch1 > Public DNS and reverse the path back to the originator PC0.

2. Click Capture / Forward until the webpage is displayed on PC0 to view the packet flow. Click View Previous Events when prompted by the Buffer Full dialog box.

Question:

After the IP address has been resolved, which path did HTTP packets travel to display the webpage? Record your observations.

Type your answers here.

DNS packets: PC0 > Wireless Router0 > Cable Modem0 > Cloud0 > Router5 > Router2> Router4 > West > Switch > www.cisco.pka and reverse the path back to the originator PC0.

3. Switch to Real time mode (Shift + R). Remove the link between Router4 and Router2 from the topology to simulate an inaccessible path. The routers are using Enhanced Interior Gateway Routing Protocol (EIGRP) to dynamically adjust routing tables to account for the deleted link.
4. Switch to Simulation mode (Shift + S). Open a web browser in Tablet0 and navigate to www.cisco.pka.

Question:

With a broken link in the WAN, how would the path change? Record your observation.

Type your answers here.

It will go through Router2 > Router1 or Router3 > Router4 to www.cisco.pka.

5. Switch to Real time mode (Shift + R).

Step 2:  PC1 to websites.

1. Click PC1 > Desktop and open a command prompt.
2. Enter tracert www.web.pka at the command.

PC> tracert www.web.pka

Tracing route to 209.165.202.132 over a maximum of 30 hops:

  1   1 ms      1 ms      0 ms      192.168.0.1

  2   0 ms      0 ms      4 ms      209.165.200.225

  3   2 ms      1 ms      0 ms      192.0.2.2

  4   2 ms      1 ms      2 ms      192.0.2.18

  5   2 ms      3 ms      2 ms      192.0.2.26

  6   6 ms      3 ms      2 ms      209.165.202.132

  7   10 ms     7 ms      11 ms     209.165.202.132

Trace complete.

3. Match the IP addresses in the tracert results to the devices in the topology. Hover over the routers in the topology to view the IP addresses of the interfaces on the routers. If the popup does not stay active long enough, you can access router IP addresses in the following manner: Click the router > CLI > press Enter. Now enter the command show ip interface brief to getting a listing of the interfaces and IP addresses.

Network address translation (NAT) is used to translate the private www.web.pka IP address of 192.168.2.254 to a routable IPv4 address of 209.165.202.132. In the tracert result, the first line of IPv4 address of 209.165.202.132 is for the G0/1 interface of East. The second line of IPv4 address of 209.165.202.132 displays the public IPv4 address of the web server.

4. Switch to Simulation mode (Shift + S). Open the web browser on PC1 and enter www.web.pka as the URL. Click Go.
5. Click Capture / Forward to load the web page.

Question:

Compare the tracert results to the simulation results for the HTTP packets. Record your observations.

Type your answers here.

The tracert and simulation results both show the same path to the web server.

• Recommend