Scribd
Upload
10 views6 pages

Exps

Uploaded by

Badri Robotics
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
10 views6 pages

Exps

Uploaded by

Badri Robotics
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

EXPERIMENT 8

AIM – Installation and Demonstration of Wireshark


Step 1: Download Wireshark
1. Go to the official Wireshark download page.
2. Choose the version compatible with your operating system (Windows,
macOS, Linux).

Step 2: Install Wireshark


Run the .exe installer.
Accept the license agreement.
Choose components to install. Make sure the WinPcap or Npcap option is
selected for packet capturing.Complete the installation

Step 3: Launch Wireshark

1. Open Wireshark from your application menu.


2. The main interface will display available network interfaces.
3. Select a network interface to capture traffic (e.g., Wi-Fi or Ethernet).
4. Click the blue shark fin button (Start Capturing).

Step 5: Analyzing Traffic


1. As packets are captured, they appear in real time with details about
protocols, source, and destination.
2. Click on a packet to view detailed information.

Result : The application was installed succesfully


EXPERIMENT 9
AIM - Practical demonstration of https using Wireshark
Procedure -
Step 1: Set Up Wireshark for Capture
1. Open Wireshark and select the network interface you want to monitor
(e.g., Wi-Fi).
2. Click the blue shark fin button to start capturing packets.
Step 2: Generate HTTPS Traffic
1. Open a web browser.
2. Visit an HTTPS-enabled website (e.g., https://www.google.com).
3. Perform actions like searching or navigating to different pages.
Step 3: Stop Capturing Packets
1. After generating sufficient traffic, return to Wireshark.
2. Click the red square button to stop the capture.
Step 4: Analyze HTTPS Traffic
1. In Wiresark's filter bar, type: tls

Step 5: Observe Key Exchanges and Encryption


1. TLS Handshake:
o Locate packets indicating "Client Hello" and "Server Hello."
These packets are part of the TLS handshake where encryption
settings and keys are negotiated.
2. Encrypted Application Data:
o Post-handshake, all data is encrypted. You will see packets labeled
as "Encrypted Application Data".
Step 6: Understanding HTTPS in Wireshark
1. Unencrypted Metadata:
o Even though the payload is encrypted, you can still see metadata
such as:
▪ Source IP and Port.
▪ Destination IP and Port (e.g., 443).
▪ Server Name Indication (SNI), which shows the domain being
accessed.

Result : The experiment demonstrates the secure communication established


using HTTPS. While the packet payload remains encrypted, Wireshark allows
for analysis of the TLS handshake and metadata. This confirms the effective
implementation of security protocols in HTTPS.
EXPERIMENT 10
AIM - Practical demonstration of ICMP using Wireshark
Procedure -
Step 1: Set Up Wireshark for Packet Capture
1. Launch Wireshark.
2. Select the appropriate network interface (e.g., Wi-Fi or Ethernet).
3. Click the blue shark fin button to start capturing packets.
Step 2: Generate ICMP Traffic
1. Open a terminal or command prompt on your system.
2. Use the ping command to send ICMP packets to a target host, such as:
Bash ping 8.8.8.8
Step 3: Stop Packet Capture
1. Go back to Wireshark.
2. Click the red square button to stop capturing.
Step 4: Apply ICMP Filter in Wireshark
In the filter bar at the top, type: icmp

Step 5: Analyze ICMP Traffic


1. Echo Request and Reply:
o Look for ICMP packets labeled Echo (ping) Request and Echo
(ping) Reply in the "Info" column.
o These packets show the source and destination IP addresses, and
their sequence numbers.
2. Packet Details:
o Click on a packet to view detailed information.
o The "Packet Details" pane will show ICMP-specific fields, such as:
▪ Type: 8 (Echo Request) or 0 (Echo Reply).
▪ Code: Usually 0 for these types.
▪ Checksum: Verifies the integrity of the ICMP message.
▪ Sequence Number: Tracks request-reply pairs
.

Step 6: Insights from ICMP Traffic


1. Latency:
o The time difference between the Echo Request and Reply packets
gives the round-trip time (RTT).
o Useful for diagnosing network delays.
2. Connectivity Issues:
o If no Echo Replies are received, it indicates the target may be
unreachable, blocked, or not responding to ICMP.
3. TTL Field:
o The "Time to Live" (TTL) field shows how many hops the packet can
take before being dropped.

Result: Wireshark successfully captured and displayed ICMP traffic, including


Echo Requests and Replies. ICMP is critical for network diagnostics, and the
observed RTT provides insights into network latency and connectivity.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy