100% found this document useful (1 vote)
47 views52 pages

Computer Networks Lab Manual A23-24

Uploaded by

Satviki Budhia
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
100% found this document useful (1 vote)
47 views52 pages

Computer Networks Lab Manual A23-24

Uploaded by

Satviki Budhia
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/ 52

Lab Manual

DEPARTMENT OF COMPUTER SCIENCE


AND ENGINEERING

Lab Manual

Course: Computer Networks

SEM-V

A.Y. 2023-2024
Lab Manual
Vision
To evolve as a centre of excellence in Computer Science and Engineering to produce skilled
and proficient global professionals to build the society.

Mission
 To provide the conducive environment for establishing students in the global platform
of research and innovation.
 To educate students on cutting edge technologies with problem solving capabilities,
leadership and teamwork skills.
 To inculcate the professional values with lifelong learning through curricular and co-
curricular activities and create globally-aware disciplined citizens.
 To commence various initiatives for motivating students to work for the betterment of
society.

Program Outcomes
Engineering Graduates will be able to:

1. Engineering knowledge: Apply the knowledge of mathematics, science, engineering


fundamentals, and an engineering specialization to the solution of complex
engineering problems.

2. Problem analysis: Identify, formulate, review research literature, and analyze


complex engineering problems reaching substantiated conclusions using first
principles of mathematics, natural sciences, and engineering sciences.

3. Design/development of solutions: Design solutions for complex engineering


problems and design system components or processes that meet the specified needs
with appropriate consideration for the public health and safety, and the cultural,
societal, and environmental considerations.

4. Conduct investigations of complex problems: Use research-based knowledge and


research methods including design of experiments, analysis and interpretation of data,
and synthesis of the information to provide valid conclusions.

5. Modern tool usage: Create, select, and apply appropriate techniques, resources, and
modern engineering and IT tools including prediction and modeling to complex
engineering activities with an understanding of the limitations.
Lab Manual
6. The engineer and society: Apply reasoning informed by the contextual knowledge to
assess societal, health, safety, legal and cultural issues and the consequent
responsibilities relevant to the professional engineering practice.

7. Environment and sustainability: Understand the impact of the professional


engineering solutions in societal and environmental contexts, and demonstrate the
knowledge of, and need for sustainable development.

8. Ethics: Apply ethical principles and commit to professional ethics and responsibilities
and norms of the engineering practice.

9. Individual and team work: Function effectively as an individual, and as a member


or leader in diverse teams, and in multidisciplinary settings.

10. Communication: Communicate effectively on complex engineering activities with


the engineering community and with society at large, such as, being able to
comprehend and write effective reports and design documentation, make effective
presentations, and give and receive clear instructions.

11. Project management and finance: Demonstrate knowledge and understanding of the
engineering and management principles and apply these to one’s own work, as a
member and leader in a team, to manage projects and in multidisciplinary
environments.

12. Life-long learning: Recognize the need for, and have the preparation and ability to
engage in independent and life-long learning in the broadest context of technological
change.
Lab Manual
Course Outcome

Sr. No. Course Outcomes

1 Explain the networking devices.

2 Troubleshoot networking problems using various techniques.

3 Analyze packet capturing of various protocols by using Wireshark tool.

4 Simulate network optimization and traffic shaping algorithms.


Lab Manual
List of Experiments
Sr. No. Title of Experiment CO

1 Study of Basic elements of Computer Networking with details of CO1


Networking Devices.
a) Study various types of network components. CO1
2 b) Introduction to the network simulator tool, Cisco packet
tracer.
a) Study and Configure Bus, and Mesh Network Topologies in CO1
3 Cisco Packet.
b) Study and configure Network Topologies (Star, and Ring) in
Cisco packet tracer.
Study different types of networks and build LAN, WAN, and CO2
4 MAN using a Cisco packet tracer.
Setting a Basic Network with Server Configuration Using Packet CO2
5 Tracer.
6 Implementation and Study of Sliding Window Protocols (Go- CO3
Back-N and Selective Repeat.
7 Implement and analyse protocols: HTTP, TCP, and ICMP using CO3
Wireshark.
8 Implementation of implementation of distance vector routing and CO3
link state algorithms. .
9 Implementation of Congestion Control Algorithm (Leaky Bucket CO3
Algorithm).
10 URL split Experiment: Splitting a Uniform Resource Locator CO4
(URL) into Its Four Components.

Prepared by:

Faculty Name(s): Dr. Krithikaa Mohanarangam


Lab Manual
Practical 1

Title: Study of Basic elements of Computer Networking with details of Networking


Devices.

Objective: Students will learn and implement


 essential network troubleshooting commands.
 network connectivity tests.

Explanation:
1. Ping
This command is used to test network connectivity and measure round-trip time
(RTT) between devices. It helps verify if a device is reachable and assess network
latency.
2. ipconfig
Displays the IP configuration of network interfaces, including IP address, subnet
mask, default gateway, and DNS servers. It is useful for diagnosing IP-related issues.
3. tracert
Traces the route that packets take to reach a destination and provides information on
network hops and latency at each hop. It helps identify network routing issues.
4. nslookup
Performs DNS lookups to resolve domain names into IP addresses. It helps
troubleshoot DNS-related issues and verify DNS configurations.
5. netstat
Shows active network connections, listening ports, and network statistics. It can help
identify open ports, established connections, and network services running on a
system.
6. arp
Displays or modifies the Address Resolution Protocol (ARP) cache, which maps IP
addresses to MAC addresses. It is useful for troubleshooting connectivity problems at
the data-link layer.
7. route
Views or modifies the local IP routing table. It is helpful for diagnosing and
configuring routing issues in a network.

Procedure
1. Open Command Prompt: Press the Windows key, type "Command Prompt," and
select the app. Alternatively, press Windows key + R, type "cmd" in Run, and press
Enter.
2. Identify the issue: Determine the specific problem, like connectivity, DNS, or a slow
network.
3. Choose the relevant command: Select a command suited to the issue, e.g., "ping" for
connectivity problems.tracert
4. Enter the command: In the Command Prompt, type the command with
parameters/options, like "ping <IP address>", and press Enter.
5. Review output: Check responses, errors, or relevant information displayed.
6. Interpret results: Analyze output to understand network connection status or error
messages.
Lab Manual
7. Perform additional commands: If needed, run more commands for further information
or tests.
8. Take appropriate action: Based on the command results, resolve the network issue by
adjusting settings, resetting devices, or seeking assistance.

Input:

Conclusion: Thus these commands were implemented in the command prompt to check and
gather comprehensive network-related information, including connectivity, configuration,
route tracing, DNS resolution, active connections, ARP table, and routing table details.

Post Lab Questions:


1. Discuss a scenario where a combination of network troubleshooting commands was
necessary to resolve a complex network problem. Describe the problem and the
commands used.
2. How do network troubleshooting commands contribute to your overall understanding
of network diagnostics and problem-solving?

Practice Problem:
Can you think of any additional network troubleshooting commands or tools that
complement the ones mentioned? Explain their relevance in troubleshooting network
issues.

a) ipconfig /flushdns
Relevance: Clears the DNS resolver cache, helpful when dealing with DNS resolution
problems.
b) tracert google.com
Relevance: Tests connectivity to a specific port on a remote host, useful for
troubleshooting issues related to specific services.
c) pathping google.com
Relevance: Combines features of ping and tracert, providing a comprehensive
analysis of network latency and packet loss along a path.
d) netsh interface show interface
Relevance: A versatile command-line scripting utility for network-related
configuration, including firewall settings, interface configuration, and more.
e) Wireshark
Relevance: A powerful packet analyzer that allows for detailed inspection of network
traffic, aiding in identifying specific issues at the packet level.
f) netsh advfirewall show allprofiles
Relevance: Commands like ‘netsh advfirewall show allprofiles’ help in reviewing
firewall settings, ensuring proper communication across the network.
g) nmap -sP 192.168.1.0/24
Relevance: A network scanning tool that can be used to discover hosts and services on
a computer network, helpful for identifying potential security issues.
Lab Manual
Practical 2

Title: Study various types of network components. Introduction to the network simulator
tool, Cisco packet tracer

Objective: Students will learn and implement


 a basic simulated network environment using packet tracker, including cables,
connectors, hubs, switches, bridges, network interface cards (NIC), gates, and
firewalls.

Explanation:
Networking devices play a crucial role in facilitating communication and data transfer within
computer networks. These devices serve various purposes and functions to ensure the smooth
operation of networked systems.

Figure. (1) Components of Network Diagram

Network Interface Card (NIC)


A network interface card (NIC) is a hardware component without which a computer cannot
be connected over a network. It is a circuit board installed in a computer that provides a
dedicated network connection to the computer. It is also called network interface controller,
network adapter, or LAN adapter. There are 2 types of NIC: Internal and external: Internal
NC and External NC.

Figure. (2) Components of Network Diagram


Lab Manual
Switch
Switch is a computer networking device that connects network segments. The term
commonly refers to a network bridge that processes and routes data at the data link layer
(layer 2) of the OSI model. Switches that additionally process data at the network layer (layer
3 and above) are often referred to as Layer 3 switches or multilayer switches.

Figure. (3) Switch

Repeater
Repeaters are network devices operating at the physical layer of the OSI model that amplify
or regenerate an incoming signal before retransmitting it. They are incorporated in networks
to expand its coverage area. They are also known as signal boosters. Repeaters amplifies the
attenuated signal and then retransmit it. Digital repeaters can even reconstruct signals
distorted by transmission loss. So, repeaters are popularly incorporated to connect between
two LANs thus forming a large single LAN.

Figure. (4) Repeater

Router
A router is an electronic device that interconnects two or more computer networks, and
selectively interchanges packets of data between them. Each data packet contains address
information that a router can use to determine if the source and destination are on the same
network, or if the data packet must be transferred from one network to another. Where
multiple routers are used in a large collection of interconnected networks, the routers
exchange information about target system addresses, so that each router can build up a table
showing the preferred paths between any two systems on the interconnected networks.
Lab Manual

Figure. (5) Router

Network bridge
A network bridge is a device that divides a network into segments. Each segment represents a
separate collision domain, so the number of collisions on the network is reduced. Each
collision domain has its own separate bandwidth, so a bridge also improves the network
performance. A bridge works at the Data link layer (Layer 2) of the OSI model. It inspects
incoming traffic and decides whether to forward it or filter it. Each incoming Ethernet frame
is inspected for destination MAC address. If the bridge determines that the destination host is
on another segment of the network, it forwards the frame to that segment.

Figure. (6) Network bridge

Procedure
Cisco Packet Tracer is a network simulation and visualization tool developed by Cisco
Systems. It provides a virtual environment where users can design, configure, and
troubleshoot computer networks. Packet Tracer allows users to simulate network topologies,
network devices, and network connections, enabling them to gain hands-on experience with
networking concepts and technologies.

Steps to help you get started with Packet Tracer:


1. Download and Install: Visit the Cisco Networking Academy website or another
reliable source to download the latest version of the Cisco Packet Tracer. Install the
software on your computer following the provided instructions.
2. Launch Packet Tracer: Open the Packet Tracer application once it is installed on your
computer.
3. Create a New Project: In Packet Tracer, click on "File" in the top menu and select
"New" to create a new project. Give the project a name and specify a location to save
it.
Lab Manual
4. Explore the Interface: Familiarize yourself with the Packet Tracer interface. You will
see various panels and toolbars, including the device toolbar on the left, the
workspace area in the middle, and options on the top menu. Take a moment to
understand the purpose of each panel and toolbar.
5. Add Network Devices: Start building your network topology by adding devices from
the device toolbar. Click on a device icon (e.g., router, switch, PC) and then click on
the workspace area to place it. Repeat this step to add more devices as needed.
6. Connect Devices: Once you have placed devices on the workspace, use the
appropriate cable type from the device toolbar to establish connections between
devices. Click on a device's interface, then click on the corresponding interface of
another device to create a connection.
7. Configure Devices: Double-click on a device to open its configuration window.
Depending on the device type, you will see various settings and parameters that can
be configured, such as IP addresses, routing protocols, VLANs, and more. Experiment
with different configurations to learn how they impact network behavior.
8. Test and Troubleshoot: Once your network is configured, you can test its
functionality. Send traffic between devices, ping IP addresses, or use applications to
verify connectivity. If you encounter issues, troubleshoot the network by examining
device configurations, connections, and network settings.
9. Explore Additional Features: Packet Tracer offers additional features such as
simulation modes, traffic generators, and network analysis tools. Take some time to
explore these features and understand how they can enhance your learning experience.
Save and Share: After completing your work, save the project by clicking on "File"
and selecting "Save" or "Save As." You can also export the project for sharing with
others.

Figure (7) Cisco’s Packet Tracer

 The top row of icons represents the category list consisting of: [Networking Devices],
[End Devices], [Components], [Connections], [Miscellaneous], and [Multiuser].
Lab Manual
 Each category contains at least one sub-category group.

GUI and CLI Configuration in Packet Tracer

The Physical tab provides an interface for interacting with the device including powering it on or
off or installing different modules such as a wireless network interface card (NIC).

Figure (8) Physical tab in Cisco’s Packet Tracer

The Config tab is a learning tab in Packet Tracer. This tab provides a way to do basic
configurations. It will show the equivalent CLI commands that perform the same action if
someone was configuring using the CLI tab.
Lab Manual

Figure (9) Config tab in Cisco’s Packet Tracer

The CLI tab provides access to the CLI interface. Here, you can practice configuring the device
at the command line.

Figure (10) CLI tab in Cisco’s Packet Tracer


Lab Manual
For some of the end devices Packet Tracer provides a desktop interface that gives you access to
IP configuration, wireless configuration, a command prompt, a web browser, and much more.

Figure (11) Desktop interface in Cisco’s Packet Tracer

If you are configuring a server, the server has all of the functions of a host with the addition of
one more tab, the Services tab. This tab allows a server to be configured as a web server, a
DHCP server, a DNS server, or various other servers visible in the graphic.
Lab Manual

Figure (12) Services tab in Cisco’s Packet Tracer

Input:

Conclusion: Studied various network components, including an introduction to the Cisco


Packet Tracer tool.

Post Lab Questions:


1. How do you add a PC to the workspace in Cisco Packet Tracer, and what
configurations can you make to the PC?
2. How do you configure a default gateway on a PC in Cisco Packet Tracer, and why
is it necessary for devices to communicate with devices on different networks?
3. How do you use the "CLI" (Command Line Interface) to configure devices in
Cisco Packet Tracer, and what are some basic commands you can use?

Practice Problem:
Lab Manual
Implement a design for a small network to include two switches and two PCs as
shown below. Write down your observations on how a packet is transferred.
Answer
Implemented a design for a small network to include two switches and two PCs.

Figure (13) Network with two switches and PCs in Cisco’s Packet Tracer
Lab Manual
Practical 3 (a)

Title: Study and Configure Bus, and Mesh Network Topologies in Cisco Packet Tracer.

Objective: Students will learn and implement


 a network with bus and mesh topologies in Packet Tracer.

Explanation:
1) Bus Topology
 In this topology, all devices are connected to a single communication line, often
called a "bus."
 Each device shares the same communication medium and can transmit and receive
data.
 However, the entire network can be affected if there is a break or failure in the main
communication line.

Figure (14) Bus Network Topology


2) Mesh Topology:
 A mesh topology provides a direct point-to-point connection between every device in
the network.
 Each device has a dedicated connection to every other device, resulting in redundant
paths.
 This redundancy enhances fault tolerance and ensures that if one path fails, data can
still be transmitted through alternative routes.
 Mesh topologies can be fully connected (every device connected to every other
device) or partially connected (selected devices have direct connections).

Figure (15) Mesh Network Topology


Lab Manual
Procedure
a) Procedure to implement Bus topology in Packet Tracer
 Open Packet Tracer and create a new project.
 Drag and drop (n) switch icons onto the workspace to represent the switches.
 Drag and drop (n) computer icons onto the workspace to represent the PCs.
 Connect a PC to a switch (1 PC to 1 Switch) using copper straight-through cables.
Each PC should have its own dedicated copper straight-through cable connecting it to
the switch.
 Repeat step 4 for all other (n) PCs.
 Next, connect the switches together in a linear chain using copper crossover cables.
Connect the first switch to the second switch using a crossover cable, the second
switch to the third switch using another crossover cable, and so on.
 Verify that all (n) PCs are connected to their switch, and the switches are connected in
a linear chain using crossover cables, forming a bus topology.
 Configure IP addresses for the devices. Right-click on each device and select
"Configure" or "Desktop" to access the device's configuration options. Assign unique
IP addresses to each PC on the network. Make sure that the subnet masks are the same
for all devices.
 You have now created a bus topology using (n) switches and (n) PCs in Packet
Tracer.
 Observe how a packet is transferred from the source to the destination PCs in a bus
topology in Packet Tracer.

Verification
 Ping test. Select the "Desktop" view for one of the devices (e.g., a computer) by right-
clicking on it and selecting "Desktop." Open a command prompt or terminal window
on the device.
 Use the ping command to test connectivity between devices. ping one computer from
the other by using its IP address. Type the following command in the command
prompt or terminal window as shown in Figure.
 If the ping is successful, you should see replies indicating that the packets were sent
and received. This confirms that the bus topology is functioning properly.
 Repeat the ping test for all devices connected to the bus to ensure connectivity
between them.
OR

 Select a source device (e.g., PC 1) from which you want to send the packet. Select a
destination device (e.g., PC 2) from which you want to send the packet.
 Click and hold the PDU icon in the toolbar, then drag it from the toolbar to the source
PC.
 Release the mouse button to drop the PDU onto the source PC.
 Click and drag the PDU from the source PC to the destination PC on the bus
topology.
 Release the mouse button to drop the PDU onto the destination PC.
 Observe the behavior of the bus topology.

b) Procedure to implement Mesh topology in Packet Tracer


Lab Manual
 Open Packet Tracer and create a new blank project.
 Drag and drop four PCs from the "End Devices" section onto the workspace.
 Drag and drop four switches from the "Switches and Hubs" section onto the
workspace.
 Connect each PC to all four switches using Ethernet cables. To do this, follow these
steps for each PC: a. Click on a PC to select it. b. Click on an available Ethernet port
(represented by a small square) on the PC. c. Drag the cable to one of the switches
and release it on an available port. d. Repeat this process to connect the PC to all four
switches.
 Now, you need to connect the switches to each other to create the mesh topology.
Follow these steps for each switch: a. Click on a switch to select it. b. Click on an
available Ethernet port to select it. c. Drag the cable to another switch and release it
on an available port. d. Repeat this process for all switches, connecting each switch to
the other three switches.
 Once all the connections are made, you should have a mesh topology with four PCs
and four switches, and each PC connected to all four switches.
 Save your project.
 Now you can start configuring IP addresses on the PCs and test communication
between them. To configure IP addresses: a. Click on a PC to select it. b. Click on the
"Config" tab in the right-hand panel. c. Enter the IP address, subnet mask, and default
gateway for each PC. Make sure that each PC has a unique IP address within the same
subnet.
 After configuring the IP addresses, you can use the "Command Prompt" utility on
each PC to ping other PCs and test the connectivity in the mesh topology.
 Configure IP addresses for each PC. Double-Click on a PC to open the configuration
window. Set an appropriate IP address for each PC. Ensure that the IP addresses are
within the same subnet. You can use IP addresses like 192.168.0.1, 192.168.0.2,
192.168.0.3, and 192.168.0.4 with a subnet mask of 255.255.255.0.

Verification
 Test the connectivity between the PCs by opening the "Command Prompt" or
"Terminal" on each PC and pinging the IP addresses of the other PCs. For example,
from PC1, you can ping PC2 using the command "ping 192.168.0.2".
 Verify that all the PCs are able to communicate with each other successfully.

OR
 Select a source device (e.g., PC 1) from which you want to send the packet. Select a
destination device (e.g., PC 2) from which you want to send the packet.
 Click and hold the PDU icon in the toolbar, then drag it from the toolbar to the source
PC.
 Release the mouse button to drop the PDU onto the source PC.
 Click and drag the PDU from the source PC to the destination PC on the bus
topology.
 Release the mouse button to drop the PDU onto the destination PC.
 Observe the behavior of the Mesh topology.
Lab Manual
Conclusion: Implemented bus and mesh topologies in Cisco Packet Tracer.

Post Lab Questions:


1. In a bus topology with five computers, one of the computers is not able to
communicate with the others. Troubleshoot the issue using Packet Tracer and
identify the possible reasons for the problem.
2. Compare the fault tolerance capabilities of bus and mesh topologies in Packet
Tracer. Discuss which topology is more resilient to failures and explain the
reasons behind it.
3. Discuss the scalability of bus and mesh topologies. How do these topologies
handle an increasing number of devices? Explain the factors that may limit the
scalability of each topology.
Lab Manual
Practical 3 (b)

Title: Study and configure Star and Ring Network Topologies in Cisco packet tracer.

Objective: Students will learn and implement


 a network with star and ring topologies in Packet Tracer.

Explanation:
1) Star Topology
 In a star topology, each device is directly connected to a central hub or switch.
 All communication between devices goes through the central hub, which helps in
better fault isolation.
 If one device fails, it does not affect the rest of the network. This is one of the most
commonly used topologies in modern networks.

Figure (16) Star Network Topology


2) Ring Topology:
 In a ring topology, devices are connected in a closed loop, forming a ring-like
structure.
 Each device is connected to two neighboring devices, and data is transmitted in a
unidirectional manner around the ring.
 This topology provides better fault tolerance since the network can still function even
if one device fails.
 However, the failure of a central device or the break in the ring can disrupt the entire
network.
Lab Manual

Figure (17) Ring Network Topology

Procedure
a) Procedure to implement Star topology in Packet Tracer
 Open Packet Tracer and create a new project.
 Drag and drop a switch from the "Switches & Hubs" section of the device panel onto
the workspace.
 Drag and drop (n) PCs from the "End Devices" section of the device panel onto the
workspace.
 Connect each PC to the switch by selecting the copper straight-through cable from the
"Connections" section of the device panel. Click on a PC, then click on the switch to
establish the connection. Repeat this step for all (n) PCs.
 Double-Click on each PC to open the configuration window. Set an appropriate IP
address for each PC. Make sure that the IP addresses are within the same subnet, but
each address should have a unique host portion. For example, you can use the IP
addresses 172.16.0.1, 172.16.0.2, 172.16.0.3, 172.16.0.4, and 172.16.0.5 with a
subnet mask of 255.255.255.0.

Verification
 Test the connectivity between the PCs by opening the "Command Prompt" or
"Terminal" on each PC and pinging the IP addresses of the other PCs. For example,
from PC1, you can ping PC2 using the command "ping 172.16.0.2".
 Verify that all the PCs are able to communicate with each other successfully.
o OR
 Select a source device (e.g., PC 1) from which you want to send the packet. Select a
destination device (e.g., PC 2) from which you want to send the packet.
 Click and hold the PDU icon in the toolbar, then drag it from the toolbar to the source
PC.
 Release the mouse button to drop the PDU onto the source PC.
 Click and drag the PDU from the source PC to the destination PC on the star
topology.
 Release the mouse button to drop the PDU onto the destination PC.
Observe the behavior of the star topology and ensure that the packets flow in a
circular manner between the PCs.

b) Procedure to implement Ring topology in Packet Tracer

 Open Packet Tracer and select the "Empty Activity " under the New tab.
 Drag and drop (n) PCs and (n) switches from the “End Devices” and “Switches &
Hubs” sections, respectively, onto the workspace.
Lab Manual
 Connect each PC to a separate switch. Make sure to establish a direct link between
each PC and its respective switch.
 Connect the switches in a circular manner to form the ring topology. Each switch
should be connected to two neighboring switches.
 Right-Click on each PC, select "Configure," and assign a unique IP address to each
PC. Make sure they are in the same subnet.
 Connect the switches using cross cables in a round-robin manner. For example,
connect the Fast Ethernet interfaces between switches in the order of Switch1 →
Switch2 → Switch3 → Switch4 → Switch1.

Verification
 Ping test. Select the "Desktop" view for one of the devices (e.g., a computer) by right-
clicking on it and selecting "Desktop." Open a command prompt or terminal window
on the device.
 Use the ping command to test connectivity between devices. ping one computer from
the other by using its IP address. Type the following command in the command
prompt or terminal window as shown in Figure.
 If the ping is successful, you should see replies indicating that the packets were sent
and received. This confirms that the ring topology is functioning properly.
 Repeat the ping test for all devices connected to the ring to ensure connectivity
between them.
OR

 Select a source device (e.g., PC 1) from which you want to send the packet. Select a
destination device (e.g., PC 2) from which you want to send the packet.
 Click and hold the PDU icon in the toolbar, then drag it from the toolbar to the source
PC.
 Release the mouse button to drop the PDU onto the source PC.
 Click and drag the PDU from the source PC to the destination PC on the ring
topology.
 Release the mouse button to drop the PDU onto the destination PC.
 Observe the behavior of the ring topology and ensure that the packets flow in a
circular manner between the PCs.

Conclusion: Implemented Star and Ring topologies in Cisco Packet Tracer.

Post Lab Questions:


1. Discuss the scalability of star and ring topologies. How do these topologies handle
an increasing number of devices? Explain the factors that may limit the scalability
of each topology.
Lab Manual
Practical 4

Title: Study different types of networks and build LAN, WAN, and MAN using a Cisco
packet tracer.

Objective: Students will learn and implement


 build LAN, WAN, and MAN using Cisco Packet Tracer.

Explanation:
Networks play a vital role in modern networking by enabling communication and resource
sharing among devices. Various types of networks serve different purposes to meet the
diverse needs of users and organizations. The most prominent types of networks include
Local Area Networks (LANs), Wide Area Networks (WANs), Metropolitan Area Networks
(MANs), Storage Area Networks (SANs), Virtual Private Networks (VPNs), Wireless
Networks, and Cloud Networks.

Three most common types of networks:


 Local Area Network (LAN)
 Wide Area Network (WAN)
 Metropolitan Area Network (MAN)

LANs, WANs, and MANs


Network infrastructures vary greatly in terms of:
 Size of the area covered
 Number of users connected
 Number and types of services available
 Area of responsibility

Procedure
a) Procedure to implement LAN in Packet Tracer
 Open Cisco Packet Tracer and create a new project.
 Drag and drop 3 PCs, 1 switch, and 1 router from the device list onto the workspace.
 Connect each PC to the switch using Ethernet cables.
 Connect one of the switch's ports to the router's Ethernet interface (usually labeled
FastEthernet or GigabitEthernet) using an Ethernet cable.
 Right-click on each device, select "Configure," and set the IP address, subnet mask,
and default gateway accordingly.
 Router Configuration: Double-click on the router to open its configuration. Configure
FastEthernet0/0 or the appropriate interface connected to the LAN (Configure the
router interfaces with appropriate IP addresses (Default gateways of your
PCs/Laptops).

Verification
Lab Manual
• You can then ping or perform other network tests between the devices to verify the
connectivity within the LAN

b) Procedure to implement WAN in Packet Tracer


Following Steps Similar to the LAN Configuration:
 Add an additional LAN network to establish WAN connectivity.
 Place a new switch on the workspace.
 Configure the new LAN network using the same steps as mentioned for the LAN
configuration above.
 Connect PCs to the new switch and configure their IP addresses, subnet masks, and
default gateways.
 Connecting Routers for WAN Link:
 Add another router to the workspace.
 Connect the new router's interface to the new LAN network's switch using an Ethernet
cable.
Connecting the Routers:
 Drag and drop a cable to connect one of the interfaces on the second LAN router to
one of the interfaces on the first LAN router. First LAN Router Configuration:
Configure the interface connected to the second LAN router interface (Fast Ethernet
0/1). Second LAN Router Configuration: Configure the interface connected to the
first LAN router interface (Fast Ethernet 0/1).
First LAN Router Configuration:
 Double-click on the first LAN router to open its configuration.
 Click on "Config" and then select "Static" from the left panel.
 Click the "Add" button to configure a new static route.
 Enter the following details:
 Network Address
 Subnet Mask
 Next Hop (in our case, IP address of FE0/1) of the second LAN router)
 Click "OK" to add the static route.
 Exit the configuration for the first LAN router.
Second LAN Router Configuration:
 Double-click on the second LAN router to open its configuration.
 Click on "Config" and then select "Static" from the left panel.
 Enter the following details:
 Network Address
 Subnet Mask
 Next Hop (in our case, IP address of FE0/1 of the first LAN router)
 Click the "Add" button to configure a new static route.
 Exit the configuration for the second LAN router.

Verification
 You can then ping or perform other network tests between the devices to verify the
connectivity within the LAN

Conclusion: Implemented a simple LAN and WAN network.


Lab Manual
Post Lab Questions:
1. What are some challenges associated with managing and securing a WAN compared
to a LAN?
2. List the limitations or constraints that you faced of simulating WAN networks in
Packet Tracer?

Practice Problem:
Simulate a Metropolitan Area Network (MAN) using Cisco Packet Tracer.

Figure (18) Metropolitan Area Network (MAN)


Lab Manual
Practical 5

Title: Setting a Basic Network with Server Configuration Using Packet Tracer.

Objective: Students will learn to


 configure servers, allocate IPs, and manage essential services.

Explanation:
Every computer on a network is called a host or end device. Servers are computers that
provide information to end devices
 email servers
 web servers
 file server
Clients are computers that send requests to the servers to retrieve information:
 web page from a web server
 email from an email server

Figure (19) Metropolitan Area Network (MAN)

Server Type Description


Email The email server runs email server software. Clients
use client software to access email.

Web The web server runs web server software. Clients use
browser software to access web pages.
File The file server stores corporate and user files. The
client devices access these files.

Procedure
Design Your Network Topology: Use DNS, DHCP, and Web Servers.

Network 1 (N1):
3 PCs
1 Switch

Network 2(N2):
1 PC
1 Web Server
Lab Manual
1 DNS Server
1 DHCP Server
1 Switch
Router Configuration:
 Identify Router Ports.
 Determine which ports on the router connect to the switches from Network 1 and
Network 2. For example, let's assume:
 FastEthernet0/0 connects to Switch-N1 in Network 1.
 FastEthernet0/1 connects to Switch-N2 in Network 2.
 Select the router in the workspace.
 In the bottom-right corner of the Packet Tracer window, you should see a "Physical"
and "Config" tab. Click on the "Config" tab.
 In the "Config" tab, you will see a list of interfaces (FastEthernet0/0, FastEthernet0/1,
etc.). Click on "FastEthernet0/0" to configure the interface that connects to Switch-
N1.
 In the configuration pane for FastEthernet0/0, you can set the IP address, and subnet
mask, and enable the interface. For example:
 IP Address: 192.168.1.1
 Subnet Mask: 255.255.255.0
 Check the box to enable the interface.
 Click on "FastEthernet0/1" to configure the interface that connects to Switch-N2.
 In the configuration pane for FastEthernet0/1, set the IP address, and subnet mask,
and enable the interface. For example:
 IP Address: 192.168.2.1
 Subnet Mask: 255.255.255.0
 Check the box to enable the interface.

DNS Server Configuration:


 In the configuration pane for the server, click on the "Config" tab.
 Under the "Basic Configuration" section, locate the fields for "DNS Server" and
"Default Gateway."
 Enter the following values:
 DNS Server: 192.168.10.10
 Default Gateway: 192.168.10.7
 Repeat these steps for all three servers (Server-DNS, Server-DHCP, and Server-Web)
to configure the DNS server address (192.168.10.10) and default gateway
(192.168.10.7) on each of them.
 This configuration ensures that all three servers use the specified DNS server and
default gateway settings.
 In the configuration pane for the server, click on the "Services" tab.
 Create a new DNS record (usually an "A" or "Host" record) for the domain name you
want to assign to an IP address. For example:
 Domain Name: krithikaa.com
 IP Address: 192.168.1.3 (You can use one of the PC's addresses)
 Save the DNS record configuration.
 This should map the specified domain name (e.g., krithikaa.com) to the provided IP
address (e.g., 192.168.1.3) within the DNS server's configuration. Remember that the
Lab Manual
specific steps may vary slightly based on the version and interface of the Packet
Tracer you are using, but the general process should be similar.
 Open a command prompt or terminal window on the PC from which you want to ping
"krithikaa.com."
 Use the "ping" command followed by the domain name you configured (e.g.,
"krithikaa.com").
 The DNS server is correctly configured, it should resolve "krithikaa.com" to the
associated IP address and attempt to ping it. If the DNS server is not configured
correctly, you may get a "host not found" error.

DHCP Server Configuration:


 You should set up the DHCP server with the specified IP address (192.168.10.8) and
DNS server address (192.168.10.10). Access the DHCP server's configuration by
clicking on the server you want to configure (e.g., Server-DHCP).
 On the Desktop, click on the "ipconfig" tab.
 Configure the DHCP server's IP address and DNS server address:
• DHCP Server IP Address: 192.168.10.8
• Default gateway:192.168.10.7
• DNS Server: 192.168.10.10
 Save the DHCP server configuration.
 Access the DHCP server's configuration by clicking on the server you want to
configure (e.g., Server-DHCP).
 In the configuration pane for the server, click on the "Services" tab.
 Under the "Services" tab, look for DHCP configuration options. You should see an
option to create DHCP pools or scopes. Create two DHCP pools, one for each
network:
 Pool 1 for Network 1 (192.168.1.0):
• Pool Name: Network1Pool
• Start IP Address: 192.168.1.10 (or any starting IP address you prefer)
• Subnet Mask: 255.255.255.0
• Default Gateway: 192.168.1.1 (assuming this is the router's IP for Network 1)
• Number of Users: Specify the number of users you want to allocate addresses
for in this pool (e.g., 50).
 Pool 2 for Network 2 (192.168.2.0):
• Pool Name: Network2Pool
• Start IP Address: 192.168.2.10 (or any starting IP address you prefer)
• Subnet Mask: 255.255.255.0
• Default Gateway: 192.168.2.1 (assuming this is the router's IP for Network 2)
• Number of Users: Specify the number of users you want to allocate addresses
for in this pool (e.g., 30).
 Save the DHCP server configuration.
 By configuring two DHCP service pools with the specified parameters, you've
allocated address ranges for each network along with their respective default
gateways. These settings will allow the DHCP server to dynamically assign IP
addresses to devices in each network.
 Configure the router's FastEthernet0/0 interface to act as a DHCP relay for Network 1
by specifying the DHCP server's IP address as the helper address:
Lab Manual
• Click on the router in Packet Tracer to select it.
• Choose FastEthernet0/0 and then click on its “CLI" tab.
 Access the CLI configuration mode by typing the following command:
• Router(config)# interface FastEthernet0/0
• Router(config-if)# ip helper-address 192.168.19.8
 Click on a PC (e.g., PC-A1) for which you want to check the DHCP-assigned IP
address.
 In the PC's configuration pane, click on the "Desktop" tab.
 In the ip config bar, navigate to the DHCP settings or DHCP status section. This is
where you can check the DHCP information for connected devices.
 Here, you should see the PCs (e.g., PC-A1) listed with their assigned IP addresses.

Web Server Configuration:


 Look for an ip config option to configure the web server's IP address. Enter the
following settings:
• IP Address: 192.168.10.6
• Subnet Mask: Typically, this is set to 255.255.255.0 for a local network.
• DNS Server: 192.168.10.10
 Configure web server settings, by clicking on services and then http, Edit the index.
 Click on the DNS server device (e.g., Server-DNS) in Packet Tracer to select it.
 In the configuration pane for the DNS server, click on the "Services" tab.
 Click on the "DNS" service to access the DNS configuration.
 Look for an option to create DNS records or DNS entries. It may be labelled as "Add
DNS Record" or something similar. Click on it.
 In the DNS record creation window, configure the following:
• Domain Name: Enter the domain name you want to associate with the web
server (e.g., mywebsite.com).
• IP Address: Enter the web server's IP address, which is 192.168.10.6.
 Save or apply the DNS record configuration.
 Click on one of the PCs (e.g., PC-A1) in Packet Tracer to select it. In the
configuration pane for the PC, click on the "Desktop" tab.
 Open a web browser on the PC.
 In the web browser's address bar, type the domain name you configured earlier to
associate with the web server's IP address.
 For example, if you associated "kri.com" with the IP address 192.168.10.6, type
"kri.com" with the actual domain name you configured.
 Press Enter or click "Go" in the web browser. If the configuration is correct, the web
browser should attempt to connect to the web server, and you should see the output of
the web server's default page or any content you may have placed on the web server.
 This simulates accessing a website hosted on the web server (192.168.10.6) from one
of the PCs in your Packet Tracer simulation. The web browser should display the web
page served by the web server.\
Lab Manual
Output:

Figure (20) Server Configuration

Conclusion: Implemented Server Configuration in Cisco Packet Tracer.


Lab Manual
Practical 6

Title: Implementation and Study of Sliding Window Protocols (Go-Back-N and Selective
Repeat)

Objective: Students will learn and implement


 Go-Back-N and Selective Repeat protocols.

Explanation:
Go-Back-N Protocol
In this protocol, the frames are sent again if they are lost while being transmitted. The size of
the receiver buffer will be one, while the size of the sender buffer is predefined. The receiver
cancels the frame if it gets corrupted; when the sender's timer for an acknowledgment to be
received expires, the sender sends the same frame again without moving on with different
frames.

Figure (21) Go Back-N Protocol


Selective repeat Protocol
Selective repeat automatic repeat request works with the data link layer and uses the sliding
window method to send frames. Only the corrupted frame during transmission is sent again in
its execution, while the further requests get acknowledged. The window size in both the
sender and receiver is the same. This protocol helps in saving on bandwidth as compared
to Go Back-N ARQ, which processed the whole frames again without selectively choosing to
send the faulty frames.
Lab Manual

Figure (22) Selective repeat Protocol


Procedure
Implement Go-Back-N and Selective Repeat protocols using a programming language of
your choice.

Algorithm:
Go-Back-N Sender

Go-Back-N Receiver
Lab Manual

Conclusion: Thus, Implemented Sliding Window Protocols.

Post Lab Questions:


1. Frame an algorithm for the Selective Repeat protocol as done in the above-mentioned
manner for the Go-Back-N protocol.
2. Imagine a scenario where a Go-Back-N sender with a window size of 3 is communicating
with a Selective Repeat receiver with a window size of 4. If the sender has sent frames 1
to 6, and the receiver has acknowledged frames 1 to 3, what actions will both the sender
and receiver take?
Lab Manual
Practical 6

Title: Implement and analyse protocols: HTTP, TCP, and ICMP using Wireshark.

Objective: Students will learn and analyse


 HTTP, TCP, and ICMP using Wireshark..

Explanation:
 Wireshark (previously called Ethereal) is one of the most widely used network protocol
analyzers.
 It passively sniffs packets that are sent from or received by a designated network
interface, but never sends packets itself.
 It receives a copy of sent packets from or received by applications and protocols
executing on end systems (e.g., your computer).
 Wireshark also has a graphical front-end to display the packets it sniffs.

Figure (23) Network protocol analyzer structure

Figure 23 shows the structure of a network protocol analyzer. The right of the figure shows
the protocol stack and application layer (such as a web browser or an FTP client) that
normally run on your computer. The network protocol analyzer, shown within the dashed
rectangle, has two parts: packet capture and a packet analyzer. The packet capture library
receives a copy of every link-layer frame that is sent from or received by a designated
network interface. Recall that messages exchanged by upper-layer protocols such as HTTP,
FTP, TCP, UDP, DNS, or IP are eventually encapsulated in link-layer frames that are sent
over physical media such as an Ethernet cable. In the above Figure, the assumed physical
medium is an Ethernet, and so all upper layer protocols’ headers are eventually encapsulated
within an Ethernet frame. Capturing all link-layer frames thus gives you all messages sent
from or received by all protocols and applications executing on your computer.

Procedure
Lab Manual

Figure (24) Wireshark graphical user interface

Exploring HTTP
 Launch Wireshark: Open Wireshark on your computer. Depending on your operating
system, you may need administrative privileges to capture traffic.
 Start Capture: After selecting the desired interface, click the "Start" or "Capture" button.
Wireshark will begin capturing traffic on the chosen interface.
 While Wireshark is running, enter the URL:
http://gaia.cs.umass.edu/wireshark-labs/INTRO-wireshark-file1.html
and have that page displayed in your browser.
 The Ethernet frames containing these HTTP messages will be
captured by Wireshark.
 After your browser has displayed the INTRO-wireshark-file1.html page, stop Wireshark
packet capture by selecting stop in the Wireshark capture window.
 This will cause the Wireshark capture window to disappear and the main
Wireshark window to display all packets captured since you began packet capture.
 Type in “HTTP” (without the quotes, and in lower case – all protocol names are lower
case in Wireshark) into the display filter specification window at the top of the main
Wireshark window. Then select Apply (to the right of where you entered “http”).
 This will cause only HTTP message to be displayed in the packet-listing
window.
 HTTP GET message that is sent to the gaia.cs.umass.edu web server is contained
within a TCP segment, which is contained (encapsulated) in an IP datagram, which
is encapsulated in an Ethernet frame.
 Select the first HTTP message shown in the packet-listing window. This should be the
HTTP GET message that was sent from your computer to the
gaia.cs.umass.edu HTTP server.
Lab Manual
 When you select the HTTP GET message, the Ethernet frame, IP datagram, TCP
segment, and HTTP message header
Information will be displayed in the packet header window.
 By clicking the plus-and-minus boxes on the left side of the packet details window,
minimize the amount of Frame, Ethernet, Internet Protocol, and Transmission Control
Protocol information displayed. Maximize the amount of information displayed about the
HTTP protocol.
 In particular, the minimized amount of protocol information for all protocols except
HTTP, and the maximum amount of protocol information for HTTP in the packet-header
window.
 To know about the parameters, click on https://www.rose-
hulman.edu/class/csse/csse432/201230/Wireshark-Labs/Wireshark_HTTP.pdf

Exploring TCP
 First, filter the packets displayed in the Wireshark window by entering “tcp” (lowercase,
no quotes, and don’t forget to press return after entering!) into the display filter
specification window towards the top of the Wireshark window.
 Access a Web page like amazon, and then type tcp contains “amazon" in the filter.
 To know about the parameters, click on https://www.rose-
hulman.edu/class/csse/csse432/201230/Wireshark-Labs/Wireshark_TCP.pdf.

Exploring ICMP
 Start-up Wireshark and begin packet capture.
 Go to command and ping a webpage or IP address.
 In your trace, you should be able to see the series of ICMP Echo Requests (in the case of
Windows machines).
 You will be able to see the address that you pinged in the ICMP echo request.
To know about the parameters, click on https://www.rose-
hulman.edu/class/csse/csse432/201230/Wireshark-Labs/Wireshark_IP.pdf

Output:

HTTP
Lab Manual

Figure (25) HTTP protocol in Wireshark

TCP
Lab Manual

Figure (26) TCP protocol in Wireshark

ICMP
Lab Manual

Figure (27) ICMP protocol in Wireshark

Conclusion: Thus, analysed HTTP, TCP, and ICMP protocols using Wireshark.

Post Lab Questions:


1. Write down the parameters that you observe by filtering HTTP, TCP, and ICMP
protocols.
Lab Manual
Practical 8

Title: Implementation of distance vector routing and link state algorithms.

Objective: Students will learn and implement


 distance vector routing and link state algorithms.

Explanation:
Distance vector routing: This falls under the category of dynamic routing algorithms. These
algorithms function by having each route maintain a table that records the shortest known
distance to reach a destination and includes the corresponding link used to achieve this. These
tables are updated through information exchange with neighboring routers, and examples of
such algorithms include the "Bellman-Ford algorithm" and the "Ford-Fulkerson algorithm."
Link state routing: Link state routing is a method in which each router shares its
neighborhood’s knowledge with every other router in the internetwork. In this algorithm,
each router in the network understands the network topology and then makes a routing table
depending on this topology.

Procedure
9. Open Command Prompt: Press the Windows key, type "Command Prompt," and
select the app. Alternatively, press Windows key + R, type "cmd" in Run, and press
Enter.
10. Identify the issue: Determine the specific problem, like connectivity, DNS, or a slow
network.
11. Choose the relevant command: Select a command suited to the issue, e.g., "ping" for
connectivity problems.tracert
12. Enter the command: In the Command Prompt, type the command with
parameters/options, like "ping <IP address>", and press Enter.
13. Review output: Check responses, errors, or relevant information displayed.
14. Interpret results: Analyze output to understand network connection status or error
messages.
15. Perform additional commands: If needed, run more commands for further information
or tests.
16. Take appropriate action: Based on the command results, resolve the network issue by
adjusting settings, resetting devices, or seeking assistance.

Program:
Distance vector routing program:
Lab Manual
Lab Manual
Lab Manual
Lab Manual
Lab Manual

Link state routing


Lab Manual
Lab Manual

Conclusion: Implemented distance vector and link state routing algorithms.

Post Lab Questions:


1. What is a Routing algorithm?
2. What is the fundamental principle behind distance vector routing, and how do routers using
this protocol update their routing tables?
3. What is the link state algorithm? How is this algorithm used to compute routing tables in a
Link-State protocol like OSPF?
Lab Manual
Practical 9

Title: Implementation of Congestion Control Algorithm (Leaky Bucket Algorithm)

Objective: Students will learn and implement


 the Congestion Control Algorithm (Leaky Bucket Algorithm).

Explanation:
The approach to congestion management is called traffic shaping. One of the methods is the
leaky bucket algorithm. Each host is connected to the network by an interface containing a
leaky bucket, that is, a finite internal queue. If a packet arrives at the queue when it is full, the
packet is discarded. In other words, if one or more processes are already queued, the new
packet is unceremoniously discarded. This arrangement can be built into the hardware
interface or simulated by the host operating system. In fact, it is nothing other than a single
server queuing system with constant service time. The host is allowed to put one packet per
clock tick onto the network. This mechanism turns an uneven flow of packets from the user
process inside the host into an even flow of packets onto the network, smoothing outbursts
and greatly reducing the chances of congestion.

Figure (28) Leaky-bucket concept depiction

Traffic Shaping to Traffic Policing


1. Network monitors traffic flows continuously to ensure they meet their traffic contract.
2. The process of monitoring and enforcing the traffic flow is called policing.
3. When a packet violates the contract, the network can discard or tag the packet giving it
lower priority.
4. If congestion occurs, tagged packets are discarded first.
5. Leaky Bucket Algorithm is the most commonly used policing mechanism
• Bucket has specified leak rate for average contracted rate.
• The bucket has specified depth to accommodate variations in arrival rate.
Lab Manual
• The arriving packet is conforming if it does not result in overflow Leaky Bucket
algorithm can be used to police the arrival rate of a packet stream.

Algorithm:
1. The figure shows the leaky bucket algorithm that can be used to police the traffic flow.
2. At the arrival of the first packet, the content of the bucket is set to zero and the last
conforming time (LCT) is set to the arrival time of the first packet.
3. The depth of the bucket is L+I, where l depends on the traffic bustiness.
4. At the arrival of the kth packet, the auxiliary variable X records the difference between the
bucket content at the arrival of the last conforming packet and the inter-arrival time
between the last conforming packet and the kth packet.
5. If the auxiliary variable is greater than L, the packet is considered nonconforming,
otherwise the packet is conforming. The bucket content and the arrival time of the packet
are then updated.

Figure (29) Leaky-bucket algorithm

Conclusion: Thus implemented leaky bucket algorithm.

Post Lab Questions:


1. What is Congestion Control?
2. What are various Congestion control techniques?
3. What is Traffic Shaping & Policing?
4. Compare the Leaky Bucket and Token Bucket Algorithm.
Lab Manual
Practical 10

Title: URL split Experiment: Splitting a Uniform Resource Locator (URL) into Its Four
Components.

Objective: Students will learn


 to split a given URL into four components that are protocol, domain, port, and path.

Explanation:
A Universal Resource Locator (URL) is a unique web address, and it represents the location
of specific resources on the internet and has 4 components: The protocol (also referred to as
transfer protocol or scheme) in a URL determines how data is transferred between the host
and a web browser (or client), usually given as HTTP. The domain is the domain name and is
always present and is the registered identification “string” (or word/phrase). The port address
is not always mentioned or specified. The path refers to the exact location of a page, post,
file, or other asset.

Procedure
1. Take the input of the URL.
2. Check if the protocol is specified else print „NULL‟ or empty.
3. Then print the domain that is specified after the protocol.
4. Then check for the port which is after the colon and it is also either specified or
unspecified.
5. Finally check the path or the location.

Program:

url = input("Enter a URL: ")

# Initialize variables to store components


protocol = ""
host = ""
port = ""
path = ""
# Find the protocol (if any)
if "://" in url:
protocol, url = url.split("://", 1)
# Find the port (if specified)
if ":" in url:
host, port = url.split(":", 1)
else:
host = url
# Find the path (if any)
if "/" in host:
Lab Manual
host, path = host.split("/", 1)
# Display the components
print(f"Protocol: {protocol}")
print(f"Host/Domain: {host}")
print(f"Port: {port}")
print(f"Path: {path}")

Conclusion: The program successfully splits a URL string into its four components:
Protocol, Host/Domain, Port, and Path.

Post Lab Questions:


1. What is a URL splitter program, and what is its primary purpose?
2. Explain the basic components of a URL that a URL splitter program typically separates.
3. Describe the role of the path in a URL.
4. What is the significance of the "protocol" in a URL?

You might also like