Experiment - 4
Experiment - 4
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.
Instructions
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
-
[Title]
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 Error: Reference source not found for information on how to allow
ICMP traffic through the firewall using Windows.
d. Stop capturing data by clicking the Stop Capture icon.
-
[Title]
a. Click the first ICMP request PDU frames in the top section of Wireshark. Notice that the Source column has your
PC IP address, and the Destination column contains the IP address of the teammate PC that 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 the destination and source MAC addresses.
Questions:
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.
Review the captured data in Wireshark and examine the IP and MAC addresses of the three locations that you pinged.
List the destination IP and MAC addresses for all three locations in the space provided.
Questions:
-
[Title]
Reflection Question
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.
Part 1: Create a new inbound rule allowing ICMP traffic through the firewall.
a. Navigate to the Control Panel and click the System and Security option in the Category view.
b. In the System and Security window, click Windows Defender Firewall or Windows Firewall.
c. In the left pane of the Windows Defender Firewall or Windows Firewall window, click advanced settings.
d. On the Advanced Security window, click the Inbound Rules option on the left sidebar and then click New Rule…
on the right sidebar.
e. This launches the New Inbound Rule wizard. On the Rule Type screen, click the Custom radio button and click
next.
f. In the left pane, click the Protocol and Ports option and using the Protocol Type drop-down menu, select
ICMPv4, and then click next.
g. Verify that Any IP address for both the local and remote IP addresses are selected. Click Next to continue.
h. Select allow the connection. Click Next to continue.
i. By default, this rule applies to all the profiles. Click Next to continue.
-
[Title]
j. Name the rule with Allow ICMP Requests. Click Finish to continue. This new rule should allow your team
members to receive ping replies from your PC.
Background / Scenario
This lab requires you to determine the availability and status of the network interface cards (NICs) on the PC that you
use. Windows provides a number of ways to view and work with your NICs.
In this lab, you will access the NIC information of your PC and change the status of these cards.
Required Resources
1 PC (Windows with two NICs, wired and wireless, and a wireless connection)
Note: At the start of this lab, the wired Ethernet NIC in the PC was cabled to one of the integrated switch ports on a
wireless router and the Local Area Connection (wired) was enabled. The wireless NIC was disabled initially. If the wired
and wireless NICs are both enabled the PC will receive two different IP addresses and the wireless NIC will take
precedence.
Instructions
-
[Title]
Note: Virtual Private Network (VPN) adapters and other types of network connections may also be displayed in this
window.
What is the Service Set Identifier (SSID) for the wireless router of your connection?
Type your answers here.
Answers will vary.
What is the speed of your wireless connection?
Type your answers here.
Answers will vary.
e. Click Details to display the Network Connection Details window.
Questions:
Notice that the information displayed here is the same information that was displayed in the Network Connection
Details window in Step e.
g. Close the command window and the Network Connection Details window. This should return you back to the Wi-Fi
Status window. Click Wireless Properties.
Close a Windows Command Prompt.
-
[Title]
Windows IP Configuration
-
[Title]
Reflection Question
Why would you activate more than one NIC on a PC?
Type your answers here.
Answers may vary. Multiple NICs can be used if more than one path is needed for the PC. One example of this
would be if the PC is being used as a Proxy Server.
-
[Title]
Objectives
Part 1: Examine the Header Fields in an Ethernet II Frame
Part 2: Use Wireshark to Capture and Analyze Ethernet Frames
Background / Scenario
When upper layer protocols communicate with each other, data flows down the Open Systems Interconnection (OSI)
layers and is encapsulated into a Layer 2 frame. The frame composition is dependent on the media access type. For
example, if the upper layer protocols are TCP and IP and the media access is Ethernet, then the Layer 2 frame
encapsulation will be Ethernet II. This is typical for a LAN environment.
When learning about Layer 2 concepts, it is helpful to analyze frame header information. In the first part of this lab, you
will review the fields contained in an Ethernet II frame. In Part 2, you will use Wireshark to capture and analyze Ethernet
II frame header fields for local and remote traffic.
Required Resources
1 PC (Windows with internet access and with Wireshark installed)
Instructions
-
[Title]
<output omitted>
-
[Title]
Preamble Not shown in capture This field contains synchronizing bits, processed by the NIC
hardware.
Destination Address Broadcast (ff:ff:ff:ff:ff:ff)
Layer 2 addresses for the frame. Each address is 48 bits long, or
6 octets, expressed as 12 hexadecimal digits, 0-9,A-F.
A common format is 12:34:56:78:9A:BC.
The first six hex numbers indicate the manufacturer of the
Source Address Netgear_99:c5:72 network interface card (NIC), the last six hex numbers are the
(30:46:9a:99:c5:72) serial number of the NIC.
The destination address may be a broadcast, which contains all
ones, or a unicast. The source address is always unicast.
Frame Type 0x0806 For Ethernet II frames, this field contains a hexadecimal value
that is used to indicate the type of upper-layer protocol in the
data field. There are numerous upper-layer protocols supported
by Ethernet II. Two common frame types are these:
Value Description
0x0800 IPv4 Protocol
0x0806 Address Resolution Protocol (ARP)
Data ARP Contains the encapsulated upper-level protocol. The data field is
between 46 – 1,500 bytes.
-
[Title]
FCS Not shown in capture Frame Check Sequence, used by the NIC to identify errors during
transmission. The value is computed by the sending device,
encompassing frame addresses, type, and data field. It is verified
by the receiver.
-
[Title]
Step 4: From the command prompt window, ping the default gateway of your PC.
Open a Windows command prompt.
From the command window, ping the default gateway using the IP address that you recorded in Step 1.
Close Windows command prompt.
-
[Title]
In the first echo (ping) request frame, what are the source and destination MAC addresses?
Source:
Type your answers here.
This should be the MAC address of the PC.
Destination:
Type your answers here.
This should be the MAC address of the Default Gateway.
What are the source and destination IP addresses contained in the data field of the frame?
Source:
Type your answers here.
This is still the IP address of the PC.
Destination:
Type your answers here.
This is the address of the server at www.cisco.com.
Compare these addresses to the addresses you received in Step 6. The only address that changed is the destination IP
address. Why has the destination IP address changed, while the destination MAC address remained the same?
Type your answers here.
-
[Title]
Layer 2 frames never leave the LAN. When a ping is issued to a remote host, the source will use the default
gateway MAC address for the frame destination. The default gateway receives the packet, strips the Layer 2
frame information from the packet and then creates a new frame header with the MAC address of the next
hop. This process continues from router to router until the packet reaches its destination IP address.
Reflection Question
Wireshark does not display the preamble field of a frame header. What does the preamble contain?
Type your answers here.
The preamble field contains seven octets of alternating 1010 sequences, and one octet that signals the beginning of
the frame, 10101011.