GURU GOBIND SINGH INDRAPRASTHA UNIVERSITY
SUBJECT : COMPUTER NETWORKS
SUBJECT CODE : CIC-355
COURSE : BTECH
BRANCH : CSE
SEMESTER : 5TH
BATCH : 2023-27
SUBMITTED TO: [Link] SUBMITTED BY: DEVANSH SINGH
RAWAT
ENROLLMENT NO.: 00589902723
INDEX
Date of Teacher’s Sign
S. No. Practicals Practical
1. Introduction to Networking
Simulation Tools: Wireshark, Cisco
Packet Tracer.
2. To understand the operation of
TELNET by accessing the router in
server room from a PC in IT office.
3. To implement an IP Addressing
Scheme and Subnetting in small
networks using Cisco Packet Tracer.
4. To implement the static routing using
Cisco Packet Tracer.
5. To implement the DHCP onto the
Network Topology using Cisco
Packet Tracer.
6. To implement the DNS, Email
Services in the Network using Cisco
Packet Tracer.
7. To implement the Dynamic Routing
Protocols: RIP, IGRP using Cisco
Packet Tracer.
To construct multiple router
8. networks and implement the EIGRP
Protocol.
9. To implement the Network Address
Resolution (NAT) using Cisco
Packet Tracer.
10. Conducting a Network Capture and
Monitoring with Wireshark
Simulation Tool.
PRACTICAL-1
AIM- Introduction to Networking Simulation Tools: Wireshark, Cisco Packet Tracer.
Networking simulation tools allow students to simulate, visualize, and analyze network behavior in a
controlled environment. They’re crucial for learning protocols, packet structures, and network
configurations without needing expensive hardware.
Wireshark: Protocol Analyzer
• Purpose: Captures and analyzes network traffic in real-time.
• Key Features:
o Packet inspection: View headers and payloads of TCP/IP, HTTP, DNS, etc. o
Filtering capabilities: Apply filters to isolate specific traffic (e.g., [Link] ==
[Link]).
o Protocol decoding: Understand how protocols behave and interact.
• Use Case o Analyze packet flow during a TCP handshake. o Study ARP requests and ICMP
messages.
o Debug network issues in lab setups.
Cisco Packet Tracer: Network Simulator
• Purpose: Simulates network topologies and device configurations.
• Key Features:
o Drag-and-drop interface: Add routers, switches, PCs, and IoT devices. o Command
Line Interface (CLI): Configure devices using Cisco IOS commands.
o Simulation mode: Step through packet flow and device behavior.
• Use Case o Design LAN/WAN topologies. o Implement IP addressing and subnetting. o
Configure routing protocols like RIP, OSPF.
o Simulate Telnet, FTP, DHCP, and NAT operations.
Feature Wireshark Cisco Packet Tracer
Purpose Packet analysis (real networks) Network design & simulation
Type Packet sniffer Network simulator
Use Case Analyzing traffic, Learning configuration,
troubleshooting network setup
Data Source Captures real-time network Simulated virtual devices
data
User Network administrators, Students, network learners
researchers
PRACTICAL-2
AIM- To understand the operation of TELNET by accessing the router in server room from a PC in
IT office.
TELNET (TELecommunication NETwork) is a network protocol used to provide remote access to
devices over a TCP/IP network. It allows users to log into another device (like a router) and execute
commands as if they were physically present.
Scenario Setup
• Client: PC in the IT office
• Server: Router in the server room
• Protocol: TELNET (uses TCP port 23)
Step-by-Step Operation
1. Enable TELNET on the Router:
Access the router's CLI (via console cable or existing network).
Run:
2. Assign IP Address to Router:
Ensure the router has a reachable IP address:
3. Verify Connectivity:
From the PC, ping the router:
4. Initiate TELNET Session:
On the PC (Command Prompt or Terminal):
5. Remote Access Achieved:
You now have CLI access to the router remotely.
Run commands like:
Simulation in Cisco Packet Tracer
You can simulate this setup in Cisco Packet Tracer:
• Place a PC and a Router.
• Connect them via switch or directly.
• Configure IPs and enable TELNET as above. Use the PC’s Command Prompt to initiate
TELNET.
TELNET transmits data in plain text, including passwords. For secure environments, SSH (Secure
Shell) is preferred.
PRACTICAL-3
AIM- To implement an IP Addressing Scheme and Subnetting in small networks using Cisco Packet
Tracer.
Step 1: Understand the Network Requirements Let’s
assume:
• Total Devices: 10 PCs, 2 switches, 1 router
• Departments: Admin (5 PCs), Accounts (5 PCs)
• Goal: Assign IPs using subnetting to separate departments logically
Step 2: Choose a Base Network and Subnet
• Base Network: [Link]/24 (Class C)
• Subnetting Goal: 2 subnets (Admin, Accounts)
Subnet Calculation:
/24 → /25
gives:
o Subnet 1: [Link] – [Link] (Admin) o
Subnet 2: [Link] – [Link] (Accounts)
• Each subnet supports 126 usable hosts
Step 3: Configure in Cisco Packet Tracer
1. Add Devices 1 Router
• 2 Switches
• 10 PCs (5 per department)
2. Connect Devices
• Use copper straight-through cables to connect:
o PCs to Switches
o Switches to Router (via different interfaces)
3. Assign IP Addresses
Device IP Address Subnet Mask Department
PC0–PC4 [Link]–5 [Link] Admin
PC5–PC9 [Link]–133 [Link] Accounts
Router Fa0/0 [Link] [Link] Admin
Router Fa0/1 [Link] [Link] Accounts
4. Configure PCs
On each PC:
o Set IP address and subnet mask
o Set default gateway to router interface IP
5. Configure Router Interfaces
Step 4: Test Connectivity
• Use ping from one PC to another in the same and different subnet. Use
tracert to verify routing path.
Benefits:
• Reinforces subnetting logic
• Demonstrates IP planning and isolation
• Prepares for CCNA-level labs
PRACTICAL-4
AIM- To implement the static routing using Cisco Packet Tracer.
Static routing involves manually configuring routes on routers to define how packets should travel
between networks. Unlike dynamic routing, it doesn’t adapt automatically to changes.
Network Scenario Let’s
assume:
• 3 Routers: R1, R2, R3 3 Networks:
o Network A: [Link]/24 (connected to R1) o
Network B: [Link]/24 (connected to R2) o
Network C: [Link]/24 (connected to R3) Routers
are connected via serial links:
• R1 ↔ R2
• R2 ↔ R3
Step-by-Step Configuration
1. Assign IPs to Interfaces
Example for R1:
Repeat similar steps for R2 and R3 with appropriate IPs.
2. Configure Static Routes
On R1:
On R2:
On R3:
3. Test Connectivity
• Use ping from a PC in Network A to a PC in Network C.
• Use tracert to verify the path.
Benefits of Static Routing
• Control: Full manual control over routing paths.
• Simplicity: Ideal for small networks.
• Performance: No overhead from routing protocols.
PRACTICAL-5
AIM- To implement the DHCP onto the Network Topology using Cisco Packet Tracer.
DHCP allows network devices to automatically receive IP configuration (IP address, subnet mask,
default gateway, DNS) from a central server, reducing manual setup and errors.
Network Scenario
Let’s assume:
• 1 Router
• 1 Switch
• 4 PCs
• DHCP service enabled on the router
Step-by-Step Configuration
1. Add Devices
• 1 Router (e.g., 2811)
• 1 Switch
• 4 PCs
2. Connect Devices
• Use copper straight-through cables:
o PCs → Switch
o Switch → Router (Fa0/0)
3. Configure Router as DHCP Server
4. Configure PCs to Use DHCP
• On each PC:
o Go to Desktop > IP Configuration o Select DHCP
5. Verify DHCP Assignment
• Each PC should receive an IP like [Link], [Link], etc. Use ipconfig on
PC’s command prompt to verify.
• Use ping to test connectivity to the router.
Benefits:
• Demonstrates automated IP assignment
• Reduces manual configuration errors
• Prepares for enterprise-level networking
PRACTICAL-6
AIM- To implement the DNS, Email Services in the Network using Cisco Packet Tracer.
Network Topology Overview
• 1 Server (DNS + Email)
• 1 Router
• 1 Switch
• 2 PCs (Client1 and Client2)
Step-by-Step DNS Configuration
1. Add Devices
• Place a Server, Router, Switch, and 2 PCs.
2. Connect Devices
• Use copper straight-through cables to connect:
o PCs and Server to Switch
o Switch to Router
3. Assign IP Addresses
Device IP Address Subnet Mask
Server [Link] [Link]
PC1 [Link] [Link]
PC2 [Link] [Link]
Router [Link] [Link]
4. Configure DNS on Server Click Server → Services tab → DNS Turn DNS Service
ON Add domain entries:
5. Configure PCs to Use DNS On each PC:
o Desktop → IP Configuration o
Set DNS Server to [Link]
Step-by-Step Email
Configuration
1. Configure Email Service on Server
Server → Services tab → Email
Turn SMTP and POP3 ON Add
users:
o user1@[Link] with password pass1 o
user2@[Link] with password pass2
2. Configure Email Clients on PCs
PC1:
o Desktop → Email o Email: user1@[Link] o
Incoming: [Link] (POP3) o Outgoing: [Link] (SMTP) o
Username: user1, Password: pass1 PC2:
o Same steps with user2@[Link]
3. Test Email Communication
• Send email from PC1 to PC2
• Check inbox on PC2
Verification
• Use ping to test connectivity.
• Use Email tab to send and receive messages.
• Use Web Browser tab to test DNS resolution (e.g., [Link]
Benefits
• Simulates enterprise services like DNS and Email
• Reinforces client-server architecture
• Prepares for CCNA and system admin roles
PRACTICAL-7
AIM- To implement the Dynamic Routing Protocols: RIP, IGRP using Cisco Packet Tracer.
RIP: Routing Information Protocol
IGRP: Interior Gateway Routing Protocol
Network Scenario
• 3 Routers: R1, R2, R3 3 Networks:
o Network A: [Link]/24 (R1) o
Network B: [Link]/24 (R2) o
Network C: [Link]/24 (R3) Routers
are connected via serial links:
• R1 ↔ R2 ([Link]/30)
• R2 ↔ R3 ([Link]/30)
Step-by-Step: RIP Configuration
1. Assign IPs to Interfaces
Example for R1:
Repeat for R2 and R3 with appropriate IPs.
2. Enable RIP on All Routers
On R1:
On R2:
On R3:
Step-by-Step: IGRP Configuration
IGRP uses Autonomous System (AS) numbers. All routers must use the same AS. On
R1:
On R2:
On R3:
Verification
• Use show ip route to view learned routes.
• Use ping and tracert to test end-to-end connectivity.
Benefits
• Demonstrates automatic route learning
• Reinforces classful routing behavior
• Prepares for CCNA and dynamic routing labs
PRACTICAL-8
AIM- To construct multiple router networks and implement the EIGRP Protocol.
EIGRP is a Cisco proprietary dynamic routing protocol that combines the best features of
distancevector and link-state protocols. It uses metrics like bandwidth and delay to determine the
best path and supports classless routing, VLSM, and fast convergence.
Network Scenario
3 Routers: R1, R2, R3
3 Networks:
o Network A: [Link]/24
(R1) o Network B: [Link]/24
(R2) o Network C: [Link]/24
(R3) Inter-router Links:
o R1 ↔ R2: [Link]/30 o
R2 ↔ R3: [Link]/30
Step-by-Step Configuration
1. Assign IP Addresses to Interfaces
Example for R1:
Repeat for R2 and R3 with appropriate IPs:
• R2: [Link], [Link], [Link]
• R3: [Link], [Link]
2. Enable EIGRP on All Routers
Use the same Autonomous System (AS) number, e.g., 100. On
R1:
On R2:
On R3:
3. Verify Routing
• Use show ip route to confirm EIGRP-learned routes.
• Use ping and tracert from one network to another to test connectivity.
Benefits
• Demonstrates automatic route learning with EIGRP
• Reinforces classless routing and VLSM
• Prepares for CCNA and advanced routing labs
PRACTICAL-9
AIM- To implement the Network Address Resolution (NAT) using Cisco Packet Tracer.
NAT allows devices in a private network (e.g., 192.168.x.x) to access external networks (e.g., the
internet) using a single public IP address. It hides internal IPs and conserves global IP space.
Network Scenario
• Router (NAT-enabled)
• Switch
• 2 PCs (inside LAN)
• Server or Cloud (simulating internet)
IP Plan
Device IP Address Subnet Mask Role
PC1 [Link] [Link] Inside LAN
PC2 [Link] [Link] Inside LAN
Router Fa0/0 [Link] [Link] Inside
Router Fa0/1 [Link] [Link] Outside
Server [Link] [Link] Public Host
Step-by-Step NAT Configuration
1. Configure Interfaces
2. Configure Access List
3. Configure NAT Translation
Configure PCs
• Set IPs manually:
o PC1: [Link], Gateway: [Link] o
PC2: [Link], Gateway: [Link]
Verification
• Use ping [Link] from PC1 or PC2. On router, use:
Benefits
• Demonstrates IP masking and conservation
• Reinforces inside vs outside interface roles
• Prepares for CCNA and real-world firewall/NAT setups
PRACTICAL-10
AIM- Conducting a Network Capture and Monitoring with Wireshark Simulation Tool.
Wireshark is a powerful packet analyzer used to capture, inspect, and analyze network traffic in real
time. It helps you understand how protocols work, troubleshoot issues, and monitor network
behavior.
Lab Setup Requirements
Wireshark installed on your PC or VM (not available inside Cisco Packet Tracer).
Two or more devices communicating over a network (e.g., PC ↔ Router, PC ↔ Server).
Internet access or simulated traffic (e.g., ping, HTTP, FTP).
Step-by-Step: Capturing Packets with Wireshark
1. Launch Wireshark
• Open Wireshark and select the active network interface (e.g., Ethernet, Wi-Fi).
2. Start Capture
• Click Start Capturing Packets (shark fin icon).
• Wireshark begins recording all traffic on the selected interface.
3. Generate Network Traffic
• Open a browser and visit a website (e.g., [Link] Or use ping, tracert, or ftp
from Command Prompt.
4. Apply Filters
• Use filters to isolate traffic:
o icmp → for ping o http → for web
traffic o [Link] == [Link]
→ for specific IP o [Link] == 80 →
for HTTP
5. Analyze Packets
• Click on a packet to view:
o Frame details (timestamp, size) o
Ethernet header o IP header
o TCP/UDP layer
o Application layer (HTTP, DNS, etc.)
6. Stop and Save Capture
• Click the red square to stop.
• Save the capture as .pcap for later analysis.
Example Use Cases
• Ping a router and observe ICMP Echo Request/Reply.
• Open a website and inspect HTTP GET/Response.
• Capture DNS queries when resolving domain names.
• Monitor TCP 3-way handshake during connection setup.
Benefits
• Visualizes protocol behavior (TCP, UDP, ICMP, DNS, HTTP)
• Reinforces OSI model understanding
• Aids in troubleshooting and security analysis