Practical:-5

Title: Setting up a Peer-to-Peer Network using Packet Tracer

Objective: To create and configure a peer-to-peer network using Packet Tracer

and demonstrate basic networking concepts including IP addressing,
connectivity testing, and file sharing.

Equipment Used:
 Cisco Packet Tracer software
 Two PCs (End Devices)

Topology Design:
 Two PCs connected directly to each other

Diagram:

Step-by-Step Procedure:

1. Topology Setup:
 Open Packet Tracer and create a new empty workspace.
 Drag and drop two PCs from the 'End Devices' section onto
the workspace.
 Connect the two PCs using an Ethernet cable.

2. IP Address Configuration:
 Select PC 1 and click on the 'Config' tab in the bottom pane.
 Enter the following IP configuration:
o IP Address: 192.168.1.1
o Subnet Mask: 255.255.255.0
o Default Gateway: (leave blank for P2P)
 Repeat the above steps for PC 2 with IP address 192.168.1.2.

3. Connectivity Testing:
 Open the command prompt on PC 1 and ping PC 2 using the
command ping 192.168.1.2.
 Verify successful ping replies.
 Repeat the ping test from PC 2 to PC 1.

4. File Sharing Configuration:

 On PC 1, create a folder and share it with full permissions.
 Access the shared folder properties and note down the sharing settings.
 On PC 2, navigate to 'Network' or 'My Network Places' and locate PC 1.
 Access the shared folder and attempt to copy a file to/from PC 1.

5. Network Documentation:
 Document the IP addresses, subnet masks, and default gateway
settings for both PCs.
 Include screenshots of the network topology, IP configurations,
and successful ping tests.
 Document the file sharing settings and provide screenshots of the
shared folder access.

6. Troubleshooting:
 Intentionally misconfigure IP settings and troubleshoot
connectivity issues.
 Document the troubleshooting steps taken and the resolution of
the issues.
 Practical:-6

Title: Implementation of Star Topology with Hub and Switch

Objective:
To understand the implementation of a star network topology using both a
hub and a switch, and to compare their functionalities and performance.
Equipment Required:
1. Ethernet cables
2. Computer devices (laptops/desktops)
3. Hub
4. Switch
5. Power sources
Diagram:

Procedure:
1. Understanding Star Topology:
  Briefly introduce the concept of a star network topology where
each device is connected to a central hub or switch.
2. Setting Up the Hardware:
 Place the hub and switch in a central location.
 Connect each computer device to the hub and the switch using
Ethernet cables. Ensure proper connections and cable management.
3. Configuring the Hub:
 Connect one end of an Ethernet cable to the uplink port of the hub.
 Connect the other end of the cable to one of the regular ports on
the switch.
 Power on the hub.
 Verify the connection status of devices by checking the LED indicators
on the hub.
4. Configuring the Switch:
 Connect one end of an Ethernet cable to any regular port on the switch.
 Connect the other end of the cable to a computer device.
 Repeat the above steps for all computer devices, ensuring each
is connected to the switch.
 Power on the switch.
 Verify the connection status of devices by checking the LED indicators
on the switch.
5. Testing Connectivity:
 Test the connectivity between all devices connected to the hub
and switch.
 Ensure that each device can communicate with the others without
any issues.
 Use ping commands or network diagnostic tools to verify connectivity.
6. Observations and Comparison:
 Observe the performance of the network in terms of speed
and reliability.
 Compare the performance of the hub and switch setups.
 Note any differences in terms of data transmission, collision handling
(for hubs), and overall network efficiency.
7. Documentation:
 Document the entire setup process along with observations
and comparisons.
 Include diagrams, if possible, illustrating the connections and
network topology.
 Summarize the advantages and disadvantages of using a hub versus
a switch in a star network topology.
Conclusion:
Conclude the practical file by summarizing the key findings, highlighting the
importance of selecting the appropriate network hardware based on the
requirements of the network, and the advantages of using a switch over a hub
in modern network setups.
 Practical:-7

Title: Interconnecting Switch and Hub for Network Communication

Objective:
To establish communication between devices connected to a switch and a hub
within a network setup, and to understand the interaction between these
networking devices.
Equipment Required:
 Ethernet cables
 Computer devices (laptops/desktops)
 Hub
 Switch
 Power sources
Diagram:

Procedure:
1. Understanding Network Components:
 Briefly introduce the functionalities of a switch and a hub in a
network environment.
 Explain the difference between how a switch forwards data
packets based on MAC addresses and how a hub broadcasts data
to all connected devices.

2. Setting Up the Hardware:

 Place the hub and switch in a central location.
 Connect the switch and hub together using an Ethernet cable. Use
a standard port on the switch and a regular port on the hub.
 Ensure all computer devices are connected to either the switch or
the hub using Ethernet cables.

3. Configuring Devices:
 Assign IP addresses to each device connected to the network. Ensure
that devices connected to both the switch and the hub are in the same
IP subnet.
 Set up default gateways and DNS servers for each device to
enable internet connectivity if required.
4. Testing Connectivity:
 Test the connectivity between devices connected to the switch and
the hub.
 Verify that devices connected to the switch can communicate
with devices connected to the hub and vice versa.
 Use ping commands or network diagnostic tools to test connectivity
and latency.

5. Monitoring Traffic:
 Use network monitoring tools or software to observe the traffic
flow between devices connected to the switch and the hub.
 Analyze how data packets are forwarded by the switch and
how broadcasts are handled by the hub.

6. Observations and Analysis:

 Observe the differences in communication between devices
connected to the switch and the hub.
 Note any latency issues or performance differences between the
two setups.
  Analyze the impact of network collisions on the hub and how the
switch mitigates such collisions.

7. Documentation:
 Document the entire setup process along with observations and analysis.
 Include diagrams illustrating the network topology and
connections between the switch and the hub.
 Summarize the advantages and disadvantages of using a switch-
hub combination in a network environment.
Conclusion:
Conclude the practical file by summarizing the key findings, emphasizing the
importance of understanding the functionalities of networking devices, and the
significance of efficient data transmission in a network setup. Additionally,
discuss the role of switches in improving network performance compared to
hubs.
 Practical:-8
Title: Practical Guide to Network Command Execution and Testing
Objective:
The objective of this practical guide is to explore and execute various
network commands for configuring, testing, and troubleshooting network
connectivity and issues.
Equipment Required:
 Computer devices (Windows and Linux)
 Network infrastructure (routers, switches, hubs)
 Ethernet cables
 Network monitoring tools (optional)
Procedure:
1. Introduction to Network Commands:
 Provide a brief overview of network commands and their significance
in managing network operations.
 Testing Network Connectivity:

2. Ping Command:
 Execute ping <hostname or IP address> to test connectivity to a
target device.
 Discuss options such as -t for continuous pinging and -c <count>
to specify the number of echo requests.

3. Traceroute/Tracepath Command:
 Use tracert <hostname or IP address> in Windows or traceroute
<hostname or IP address> in Linux to trace the route to a destination.

4. Viewing Network Configuration:

 Windows:
 Use ipconfig /all to view detailed network interface information.
 Linux:
 Execute ifconfig -a to display network interface configurations.
 Utilize ip addr show to view IP addresses assigned to network interfaces.
 5. Configuring Network Settings:
 Windows:
 Use netsh command to modify network settings such as IP
address, subnet mask, and default gateway.
 Linux:
 Edit network configuration files like /etc/network/interfaces or
use commands like ifconfig or ip to configure network settings.

6. Monitoring Network Traffic:

 Wireshark (Windows/Linux):
 Utilize Wireshark to capture and analyze network traffic in real-time.
 Netstat Command:
 Execute netstat -ano in Windows or netstat -tunap in Linux to display
active network connections, listening ports, and associated
processes.

7. Troubleshooting Network Issues:

 Address Resolution Protocol (ARP):
 Use arp -a in both Windows and Linux to view the ARP cache
and associated MAC addresses.
 DNS Resolution:
 Execute nslookup <hostname> or dig <hostname> to perform
DNS lookups and resolve domain names to IP addresses.

Documenting Results:
 Document each command execution, including the purpose, syntax,
and sample output.
 Include screenshots or outputs of command executions for clarity
and reference.
Conclusion:
Conclude by summarizing the importance of network commands in managing
and troubleshooting networks effectively. Emphasize the practical applications
of these commands in diagnosing issues, optimizing network performance, and
ensuring seamless communication within a network environment. Encourage
further exploration and practice with these commands for a better
understanding of network operations.
 Table Of Content:-

S.NO Practical Name Date Signature

1. Study of RJ45 and CAT cabling and

connection using Grimpling tool

2. Write a program to perform

Bitstuffing

3. Write a program to find out the

Hamming code

4. Write a program to implement

CRC mechanism

5. Create a peer to peer network

using packet tracert

6. Create a Star topology using

switch and hub

7. Create a communication b/w

switch and hub

8. Write all network based

command running or testing
of network command