Lab4-Using Wireshark To View Network Traffic
Lab4-Using Wireshark To View Network Traffic
Topology
Objectives
Part 1: Capture and Analyze Local ICMP Data in Wireshark
Part 2: Capture and Analyze Remote ICMP Data in Wireshark
Background / Scenario
Wireshark is a software protocol analyzer, or "packet sniffer" application, used for network troubleshooting,
analysis, software and protocol development, and education. As data streams travel back and forth over the
network, the sniffer "captures" each protocol data unit (PDU) and can decode and analyze its content
according to the appropriate RFC or other specifications.
Wireshark is a useful tool for anyone working with networks and can be used with most labs in the CCNA
courses for data analysis and troubleshooting. In this lab, you will use Wireshark to capture ICMP data packet
IP addresses and Ethernet frame MAC addresses.
Required Resources
1 PC (Windows 7, 8, or 10with internet access)
Additional PCs on a local-area network (LAN) will be used to reply to ping requests.
c. Ask a team member or team members for their PC IP address and provide your PC IP address to them.
Do not provide them with your MAC address at this time.
b. After Wireshark starts, click the capture interface to be used.Because we are using the wired Ethernet
connection on the PC, make sure the Ethernet option is on the top of the list.
You can manage the capture interface by clicking Capture and Options:
c. A list of interfaces will display. Make sure the capture interface is checked under Promiscuous.
Note: We can further manage the interfaces on the PC by clicking Manage Interfaces.Verify that the
description matches what you noted in Step 1b. Close theManage Interfaces window after verifying the
correct interface.
d. After you have checked the correct interface,click Start to start the data capture.
Note: You can also start the data capture by clicking the Wireshark icon in the main interface.
Information will start scrolling down the top section in Wireshark. The data lines will appear in different
colors based on protocol.
e. This information can scroll by very quickly depending on what communication is taking place between
your PC and the LAN. We can apply a filter to make it easier to view and work with the data that is being
captured by Wireshark. For this lab, we are only interested in displaying ICMP (ping) PDUs. Type icmp in
the Filter box at the top of Wireshark and press Enter or click on the Apply button(arrow sign) to view
only ICMP (ping) PDUs.
f. This filter causes all data in the top window to disappear, but you are still capturing the traffic on the
interface. Bring up the command prompt window that you opened earlier and ping the IP address that you
received from your team member.
Notice that you start seeing data appear in the top window of Wireshark again.
Note: If the PC of your team member does not reply to your pings, this may be because thePC firewall of
the team member is blocking these requests. Please see Appendix A: Allowing ICMP Traffic Through
a Firewall for information on how to allow ICMP traffic through the firewallusing Windows 7.
g. Stop capturing data by clicking theStop Capture icon.
a. Click the firstICMP request PDU frames in the top section of Wireshark. Notice that the Source column
has your PC IP address, and the Destinationcolumn contains the IP address of the teammate PCthat
you pinged.
b. With this PDU frame still selected in the top section, navigate to the middle section. Click the plus sign to
the left of the Ethernet II row to view thedestination and source MAC addresses.
Does the source MAC address match your PC interface (shown in Step 1.b)? ______ Yes
Does the destination MAC address in Wireshark match your team member MAC address?
_____ Yes
How is the MAC address of the pinged PC obtained by your PC?
___________________________________________________________________________________
The MAC address is obtained through an ARP request.
Note: In the preceding example of a captured ICMP request, ICMP data is encapsulated inside an IPv4
packet PDU (IPv4 header) which is then encapsulated in an Ethernet II frame PDU (Ethernet II header)
for transmission on the LAN.
b. A window prompts you to save the previously captured data before starting another capture. It is not
necessary to save this data. Click Continue without Saving.
c. With the capture active, ping the following three website URLs:
1) www.yahoo.com
2) www.cisco.com
3) www.google.com
Note: When you ping the URLs listed, notice that the Domain Name Server (DNS) translates the URL to
an IP address. Note the IP address received for each URL.
d. You can stop capturing data by clicking the Stop Capture icon.
Step 2: Examining and analyzing the data from the remote hosts.
a. Review the captured data in Wireshark and examine the IP and MAC addresses of the three locations
that you pinged.List the destinationIP and MAC addresses for all three locations in the space provided.
1stLocation: IP: _____._____._____._____ MAC: ____:____:____:____:____:____
2nd Location: IP: _____._____._____._____ MAC: ____:____:____:____:____:____
rd
3 Location: IP: _____._____._____._____ MAC: ____:____:____:____:____:____
IP addresses: 98.139.180.180, 23.13.155.188, 216.58.194.100 (these IP addresses may vary)
MAC address: This will be the same for all three locations. It is the physical address of the default-
gateway LAN interface of the router.
b. What is significant about this information?
____________________________________________________________________________________
The MAC addresses for all three locations are the same.
c. How does this information differ from the local ping information you received in Part 1?
____________________________________________________________________________________
____________________________________________________________________________________
Aping to a local host returnstheMAC address of the PC NIC. A ping to a remote host returns the MAC
address of thedefaultgateway LAN interface.
Reflection
Why does Wireshark show the actual MAC address of the local hosts, but not the actual MAC address for the
remote hosts?
_______________________________________________________________________________________
_______________________________________________________________________________________
MAC addresses for remote hosts are not known on the local network, so the MAC address of the default-
gateway is used. After the packet reaches the default-gateway router, the Layer 2 information is stripped from
the packet and a new Layer 2 header is attached with the destination MAC address of the next hop router.
Step 1: Create a new inbound rule allowing ICMP traffic through the firewall.
d. From the Control Panel, click the System and Securityoption.
f. In the left pane of the Windows Firewall window, click Advanced settings.
g. On the Advanced Security window, choose the Inbound Rules option on the left sidebar and then click
New Rule… on the right sidebar.
h. This launches the New Inbound Rulewizard. On the Rule Type screen, click the Custom radio button
and click Next
i. In the left pane, click the Protocol and Ports option and using the Protocol Type drop-down menu,
select ICMPv4, and then click Next.
j. In the left pane, click the Name option and in the Name field, type Allow ICMP Requests. Click Finish.
This new rule should allow your team members to receive ping replies from your PC.
b. To disable the rule, click the Disable Rule option. When you choose this option, you will see this option
change to Enable Rule. You can toggle back and forth between Disable Rule and Enable Rule; the
status of the rule also shows in the Enabled column of the Inbound Rules list.
c. To permanently delete the ICMP rule, click Delete. If you choose this option, you must re-create the rule
again to allow ICMP replies.