Lab 3 Instructions
.docx
keyboard_arrow_up
School
Liberty University *
*We aren’t endorsed by this school
Course
330
Subject
Information Systems
Date
Dec 6, 2023
Type
docx
Pages
6
Uploaded by MasterYakMaster431
Lab - Use 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 with internet access)
•
Additional PCs on a local-area network (LAN) will be used to reply to ping requests.
Using a packet sniffer such as Wireshark may be considered a breach of the security policy of the school. It is
recommended that permission be obtained before running Wireshark for this lab. If using a packet sniffer such
as Wireshark is an issue, the instructor may wish to assign the lab as homework or perform a walk-through
demonstration.
©
2013 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public
Page
1
of
6
www.netacad.com
Lab - Use Wireshark to View Network Traffic
Instructions Part 1: Capture and Analyze Local ICMP Data in Wireshark
In Part 1 of this lab, you will ping another PC on the LAN and capture ICMP requests and replies in
Wireshark. You will also look inside the frames captured for specific information. This analysis should help to
clarify how packet headers are used to transport data to their destination.
Step 1: Retrieve your PC interface addresses.
For this lab, you will need to retrieve your PC IP address and its network interface card (NIC) physical
address, also called the MAC address.
Open a Windows command prompt.
a. In a command prompt window, enter
ipconfig /all
, to the IP address of your PC interface, its description,
and its MAC (physical) address.
C:\Users\Student>
ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : DESKTOP-NB48BTC
Primary Dns Suffix
. . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix
. :
Description . . . . . . . . . . . : Intel(R) 82577LM Gigabit Network Connection
Physical Address. . . . . . . . . :00-26-B9-DD-00-91
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d809:d939:110f:1b7f%20(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.147(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
<output omitted>
b. 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.
24.131.15.176
Close a Windows Command Prompt.
Step 2: Start Wireshark and begin capturing data.
a.
Navigate to Wireshark. Double-click the desired interface to start the packet capture. Make sure the
desired interface has traffic.
b.
Information will start scrolling down the top section in Wireshark. The data lines will appear in different
colors based on protocol.
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 the
Apply
button (arrow sign) to view only ICMP (ping) PDUs.
©
2013 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public
Page
2
of
6
www.netacad.com
Lab - Use Wireshark to View Network Traffic
c.
This filter causes all data in the top window to disappear, but you are still capturing the traffic on the
interface. Navigate to a command prompt window and ping the IP address that you received from your
team member.
C:\>
ping 192.168.1.114
Pinging 192.168.1.114 with 32 bytes of data:
Reply from 192.168.1.114: bytes=32 time<1ms TTL=128
Reply from 192.168.1.114: bytes=32 time<1ms TTL=128
Reply from 192.168.1.114: bytes=32 time<1ms TTL=128
Reply from 192.168.1.114: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.114:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-
seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
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 the PC 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 firewall using Windows.
d. Stop capturing data by clicking the
Stop Capture
icon.
Step 3: Examine the captured data.
©
2013 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public
Page
3
of
6
www.netacad.com
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help