[Approved by AICTE, Govt. of India & Affiliated to Dr.

APJ
GL BAJAJ
Institute of Technology & Management
Abdul Kalam Technical University, Lucknow, U.P., India]
Department of Applied Computational Science &
Greater Noida Engineering

Department of Applied Computational Science & Engineering

G. L. Bajaj Institute of Technology and Management

Greater Noida, Uttar Pradesh

Affiliated to Dr. A.P.J Abdul Kalam Technical University, Lucknow (UP)

COMPUTER NETWORKS LAB

KCS-653

SESSION:- 2023-2024
Semester - VI

SUBMITTED TO:- SUBMITTED BY:-

SHIVAM MAURYA
MS NEHA YADAV SATYAM KUMAR
(2101921530151)
(Asst. Professor) 2101921530141
 [Approved by AICTE, Govt. of India & Affiliated to Dr. APJ
GL BAJAJ
Institute of Technology & Management
Abdul Kalam Technical University, Lucknow, U.P., India]
Department of Applied Computational Science &
Greater Noida Engineering

INDEX
S. No. Experiments Date Signature

1 To learn handling and configuration of networking

hardware like RJ-45connector, CAT-6 cable, crimping
tool, etc.
2 Configuration of router, hub, switch etc. (using
simulators)
3 Running and using services/commands like ping,
traceroute, nslookup, ipconfig, Ipconfig-all, etc.

4 Network packet analysis using tools like Wireshark,

tcpdump, etc.
5 Network simulation using tools like Cisco Packet
Tracer, NetSim,OMNeT++, NS2, NS3, etc

6 Socket programming using UDP and TCP (e.g., simple

DNS, data & time client/server, echo client/server,
iterative & concurrent servers)
7 Configure and connect two PCs using Cross Over and
Straight forward wire Connection.

8 Configure a DNS server in along with existing network

using CiscoPacket Tracer.

9 Configure Routing Information Protocol (RIP) for an

autonomous network using Cisco Packet Tracer.

Configure an email server using cisco packet tracer.

10
 Experiment-1
Objective: To learn handling and configuration of networking hardware like RJ-45 connector,
CAT-6 cable and crimping tool etc.

Apparatus (Components): RJ-45 connector, Crimping Tool, Twisted pair Cable.

Brief Theory

RJ 45- Registered Jack 45 (RJ45) is a standard type of physical connector for network cables.
RJ45 connectors are most commonly seen with Ethernet cables and networks. Modern Ethernet
cables feature small plastic plugs on each end that are inserted into the RJ45 jacks of Ethernet
devices.

CAT-6 Cable- Category 6 Cable (Cat 6), is a standardized twisted pair cable for Ethernet and
other network physical layers.

Crimping Tool- Crimping Tool is a device used to conjoin two pieces of metal by deforming one
or both of them in a way that causes them to hold each other.

Procedure: To do these practical following steps should be done:

Step 1. Start by stripping off about 2 inches of the plastic jacket off the end of the cable. Be very
careful at this point, as to not nick or cut into the wires, which are inside. Doing so could alter
the characteristics of your cable, or even worse render is useless. Check the wires, one more time
for nicks or cuts. If there are any, just whack the whole end off, and start over.

Step 2. Spread the wires apart, but be sure to hold onto the base of the jacket with your other
hand. You do not want the wires to become untwisted down inside the jacket. Category 5 cable
must only have 1/2 of an inch of 'untwisted' wire at the end; otherwise it will be 'out of spec'. At
this point, you obviously have ALOT more than 1/2 of an inch of un-twisted wire.

Step 3. You have 2 end jacks, which must be installed on your cable. If you are using a pre-made
cable, with one of the ends whacked off, you only have one end to install - the crossed over end.
Below are two diagrams, which show how you need to arrange the cables for each type of cable
end. Decide at this point which end you are making and examine the associated picture below.
Diagrams for preparing Cross wired connection

Figure1.1: Crossover connection

Figure 1.2: Color coding sequence for RJ45 connectors at both ends in cross wired connection
Diagram for preparing straight through wired connection
 Figure1.3: Straight through wired connection

Figure 1.4: Color coding sequence for RJ45 connectors at both ends in straight through wired
connection
Result- Configuration of networking hardware like RJ-45 connector, CAT-6 cable, crimping
tool, etc. is learned.
 Experiment-2
Objective: Configuration of router, hub, switch etc. (using real device or simulators)

Apparatus: Cisco Packet Tracer

Procedure:
Configuration of Hub using Star Topology

Step 1:- Open Cisco packet Tracer Software and choose Generic Hub on workspace.

Figure 2.1: Generic Hub

Step 2:- Now choose end device as Generic. Connect end devices with Hub (Choose automatic
connection type).

Figure 1: End devices connected with Hub

Step 3 :- Now click on each end device and enter IP address such as 10.0.0.1 and label the
device with corresponding IP address using text tool available in cisco packet tracer.

Figure 2.2: IP configuration of devices

Step 4:- Now select Simple Message(PDU) from right side of window and click over sender

node and on receiver node.

Figure 2.3: Selection of PDU

Step 5: Now click on simulation and click on AutoPlay to see effect.

Figure 2.4: Simulation results

Configuration of Switch using Star Topology

Step 1:- Open Cisco packet Tracer Software and choose Generic Switch on workspace.

Figure 2.5:Generic Switch

Step 2 :- Now choose end device as Generic. Connect end devices with switch (Choose
automatic connection type.

Figure 2.6: Connection of end devices with Switch

Figure 2.7: IP configuration of end devices

 Figure 2.8:Topology diagram
Step 5: Now click on simulation and click on AutoPlay to see effect.

Configuration of Router

Figure 2.9:Router as connecting device

Modes of Router

1. User mode: Router>

2. Privilege Mode: Router#
3. Global Configuration Mode: Router (config)#
 4. Fast Ethernet Interface Mode: Router (Config-if)#
Basic Router Commands

1. User Mode to Privilege Mode: Router > enable

2. Privilege Mode to Global Configuration Mode: Router# config terminal

3. Global Configuration Mode to Fast Ethernet Interface Mode: Router (config)# interface
FastEthernet 0/0

4. Active and Synchronize IP with interface: Router(config-if) no shutdown

5. Exit from Mode : Router(Config-if)#Exit

Figure 2.10:Topology diagram for Router configuration

Step 1: Open Cisco Packet Tracer software and then click on Router and then over Generic, then
drag it over workspace.

Step 2: Design topology as shown in the diagram above.

Step 3: Now click on each end device and enter IP address such as 10.0.0.1 and label the device
with corresponding IP address using text tool available in cisco packet tracer. Be ensure that
router should connect two different networks.
 Figure 2.11:IP configuration in end devices
Step 4: Double click router and type router commands to configure router at interface fa0/0 and
fa0/1

Router>enable
Router#configure terminal
Router(config)#hostname R1
Router(config)#interface fastethernet 0/0
Router(config-if )# 10.0.0.1 255.0.0.0
Router(config-if )# no shut down

Figure 2.12: configuration in CLI mode

Step 5 :- Now select Simple Message from right side of window and click over sender node and
on receiver node.

Step 6 :- Now click on simulation and click on AutoPlay to see effect.

Result: Configuration of router, hub, switch is performed.

 Experiment-3
Objective: Study of basic network command and Network configuration commands.
Apparatus (Software): Command Prompt and Cisco Packet Tracer.

Procedure: In this experiment students must understand basic networking commands e.g.
ping, tracert etc.
All commands related to Network configuration which includes how to switch to privilege
mode and normal mode and how to configure router interface and how to save this
configuration to flash memory or permanent memory.
This commands includes
• Configuring the Router commands • General Commands to configure network • Privileged
Mode commands of a router • Router Processes & Statistics • IP Commands • Other IP
Command e.g. show ip route etc.
ping:
Verifies IP-level connectivity to another TCP/IP computer by sending Internet Control
Message Protocol (ICMP) Echo Request messages. The receipt of corresponding Echo Reply
messages is displayed, along with round-trip times. Ping is the primary TCP/IP command used
to troubleshoot connectivity, reachability, and name resolution.

You can use ping to test both the computer name and the IP address of the computer. If pinging
the IP address is successful, but pinging the computer name is not, you might have a name
resolution problem. In this case, ensure that the computer name you are specifying can be
resolved through the local Hosts file, by using Domain Name System (DNS) queries, or
through NetBIOS name resolution techniques.
Traceroute:
Determines the path taken to a destination by sending Internet Control Message Protocol
(ICMP) Echo Request messages to the destination with incrementally increasing Time to Live
(TTL) field values. The path displayed is the list of near-side router interfaces of the routers in
the path between a source host and a destination. The near-side interface is the interface of the
router that is closest to the sending host in the path. Used without parameters, tracert displays
help.
To trace the path to the host named www.google.co.in use following command
tracert www.google.co.in

Ipconfig:

This command can be used to set up a device's IPv4 address, subnet mask and default
gateway. These values are entered in following format Ipconfig Entering only ipconfig
returns IP address, subnet default gateway across all interfaces for selected device.
Nslookup (stands for “Name Server Lookup”) is a useful command for getting information
from DNS server. It is a network administration tool for querying the Domain Name System
(DNS) to obtain domain name or IP address mapping or any other specific DNS record. It is
also used to troubleshoot DNS related problems.
5. Ipconfig /all:
This command returns all the addresses but along with IP subnet default gateway of all interfaces, it
also returns server address along DHCP, DNS servers.
 Experiment-4

Objective: - Network packet analysis using tools like Wireshark, tcpdump, etc.

Apparatus (Software): Wireshark, tcpdump

TCPDUMP:

The fundamental tool of almost all network traffic collection is tcpdump. It is an open-source
application that comes installed on almost all Unix-like operating systems. Tcpdump is an
excellent collection tool and comes complete with a very complex filtering language. It’s
important to know how to filter the data at collection time in order to end up with a manageable
chunk of data to analyze. Capturing all data from a network device on even a moderately busy
network can create too much data to analyze easily.

In some rare cases, allowing tcpdump to output its capture directly to your screen may be
enough to find what you’re looking for. For example, in writing this article, I captured some
traffic and noticed that my machine was sending traffic to an IP I did not recognize. It turns out
that my machine was sending data to a Google IP address of 172.217.11.142. Since I did not
have any Google products running, nor Gmail open, I did not know why this was happening. I
examined my system and found this:

[ ~ ]$ ps -ef | grep google

user 1985 1881 0 10:16 ? 00:00:00 /opt/google/chrome/chrome --type=service
It seems that even when Chrome is not running in the foreground it remains running as a
service. I would not have necessarily noticed this without a packet analysis to tip me off. I re-
captured some more tcpdump data but this time told tcpdump to write the data to a file that I
opened in Wireshark (more on that later). Here’s that entry:

Tcpdump is a favorite tool among sysadmins because it is a command-line tool. This means
that it doesn’t require a full-blown desktop to run. It is unusual for production servers to provide
a desktop because of the resources that would take, so command-line tools are preferred. As
with many advanced tools, tcpdump has a very rich and arcane language that takes some time
to master. A few of the very basic commands involve selecting the network interface from
which to collect data, and writing that data to a file so it can be exported for analysis elsewhere.
The -i and -w switches are used for this.

# tcpdump -i eth0 -w tcpdump_packets

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
^C51 packets captured
This produces a capture file:

file tcpdump_packets
tcpdump_packets: tcpdump capture file (little-endian) - version 2.4 (Ethernet, capture length
262144)

The standard TCP capture file is a pcap file. It is not text so it can only be read by an analysis
program that knows how to read pcap files.

2. WinDump

Most useful open source tools are eventually cloned to other operating systems. When this
happens, the application is said to have been ported over. Windump is a port of tcpdump and
behaves in very similar ways.

One major difference between WinDump and tcpdump is that Windump needs the WinpCap
library installed prior to being able to run WinDump. Despite both WinDump and WinpCap
being provided by the same maintainer, they are separate downloads.

WinpCap is an actual library that needs to be installed. But, once it is installed, WinDump is
an .exe file that needs no installation so it can just run. That may be something to keep in mind
if you’re running a Windows network. You don’t necessarily need WinDump installed on every
machine since you can just copy it over as needed, but you will want WinpCap installed in
order to support WinDump.

As with tcpdump, WinDump can output network data to the screen for analysis, be filtered in
the same way, and also write data to a pcap file for analysis offsite.

7. Wireshark

wireshark is probably the next best-known tool in any sysadmin’s toolkit. It can not only
capture data, but also provides some advanced analysis tools. Adding to its appeal, Wireshark
is open source, and has been ported over to almost every server operating system that exists.
Starting life named Etheral, Wireshark now runs everywhere, including as a standalone
portable app.

If you’re analyzing traffic on a server with a desktop installed, Wireshark can do it all for you.
It can collect the data, and then analyze it all in one spot. However, desktops are not common
on servers, so in many cases, you’ll want to capture the network data remotely and then pull
the resulting pcap file into Wireshark.

At first launch, Wireshark allows you to either load an existing pcap file, or start capturing. If
you elect to capture network traffic, you can optionally specify filters to pare down the amount
of data Wireshark collects. Since its analysis tools are so good, it’s less important to ensure you
surgically identify the data at collection time with Wireshark. If you don’t specify a filter,
Wireshark will simply collect all network data that your selected interface observes.
One of the most useful tools Wireshark provides is the ability to follow a stream. It’s probably
most useful to think of a stream as an entire conversation. In the screenshot below we can see
a lot of data has been captured, but what I am most interested in is that Google IP. I can right-
click it and Follow the TCP Stream to see the entire conversation.

If you’ve captured traffic elsewhere, you can import the pcap file using Wireshark’s File ->
Open dialogue. The same filters and tools that can be used for natively captured network data
are available for imported files.
Result- Network packet analysis using tools like Wireshark, tcpdump, etc.is done and
understood.
 Experiment-5
Objective: Network simulation using tools like Cisco Packet Tracer, NetSim, OMNeT++,
NS2, NS3, etc.

Brief Theory:

Network simulation- In computer network research, network simulation is a technique

whereby a software program models the behavior of a network by calculating the interaction
between the different network entities.

Cisco Packet Tracer- Packet Tracer allows users to create simulated network topologies by
dragging and dropping routers, switches and various other types of network devices. A
physical connection between devices is represented by a 'cable' item. Cisco Systems claims
that Packet Tracer is useful for network experimentation.

Figure 5.1 Cisco Packet Tracer Enviroment

NetSim-NetSim is an end-to-end, full stack, packet level network simulator and emulator. It
provides network engineers with a technology development environment for protocol
modeling, network R&D and military communications.

A network simulator enables users to virtually create a network comprising of devices, links,
applications etc, and study the behavior and performance of the Network.
 Figure 5.2 NetSim Enviroment
Some example applications of network simulators are

 Protocol performance analysis

 Application modeling and analysis

 Network design and planning

 Research and development of new networking technologies

 Test and verification

The typical steps followed when simulating any network are:

Building the model – Create a network with devices, links, applications etc

Running the simulation - Run the discrete event simulation (DES) and log different
performance metrics

Visualizing the simulation - Use the packet animator to view the flow of packets

Analyzing the results - Examine output performance metrics such as throughput, delay, loss
etc. at multiple levels - network, link, queue, application etc.

Developing your own protocol / algorithm - Extend existing algorithms by modifying the
simulator’s source C code
OMNeT++ -OMNeT++ (Objective Modular Network Testbed in C++)is a modular,
component-based C++ simulation library and framework, primarily for building network
simulators.OMNeT++ itself is a simulation framework without models for network protocols
like IP or HTTP. The main computer network simulation models are available in several
external frameworks. The most commonly used one is INETwhich offers a variety of models
for all kind of network protocols and technologies like for IPv6, BGP etc. INET also offers a
set of mobility models to simulate the node movement in simulations. The INET models are
licensed under the LGPL or GPL.

Components

The main ingredients of OMNeT++ are:

 Simulation kernel library (C++)

 The NED topology description language
 Simulation IDE based on the Eclipse platform
 Interactive simulation runtime GUI (Qtenv)
 Command-line interface for simulation execution (Cmdenv)
 Utilities (makefile creation tool, etc.)
 Documentation, sample simulations, etc.

NS2- NS2 stands for Network Simulator Version 2. It is an open-source event-driven

simulator designed specifically for research in computer communication networks.Ns2 is an
event driven simulator, which is a open source simulator mainly used for academic research
in the areas of Computer Networks, MANETs, WSNs.NS-2 can be used to implement
network protocols such as TCP and UPD, traffic source behavior such as FTP, Telnet, Web,
CBR and VBR, router queue management mechanism such as Drop Tail, RED and CBQ,
routing algorithms and many more. In ns2, C++ is used for detailed protocol implementation
and Otcl is used for the setup.

Features of NS2

1. It is a discrete event simulator for networking research.

2. It provides substantial support to simulate bunch of protocols like TCP, FTP, UDP, https
and DSR.

3. It simulates wired and wireless network.

4. It is primarily Unix based.

5. Uses TCL as its scripting language.

6. Otcl: Object oriented support

7. Tclcl: C++ and otcl linkage

8. Discrete event scheduler

Basic Architecture

NS2 consists of two key languages: C++ and Object-oriented Tool Command Language
(OTcl). While the C++ defines the internal mechanism (i.e., a backend) of the simulation
objects, the OTcl sets up simulation by assembling and configuring the objects as well as
scheduling discrete events. The C++ and the OTcl are linked together using TclCL

NS3- Computer network simulation in the sense connection of two or more computer system
linked together for communication. Networking is the practice of interfacing two or more
computing devices with each other for the purpose of sharing data. Computer networks are
built with a combination of hardware and software.ns-3 is a discrete-event network simulator,
targeted primarily for research and educational use. ns-3 is free software, licensed under the
GNU GPLv2 license, and is publicly available for research, development, and use.

NS-3 is intended to provide better support than in NS-2 for the following items:

• Modularity of components
• Scalability of simulations
• Integration/reuse of externally developed code and software utilities
• Emulation
• Tracing and statistics
• Validation

Result- Network simulation is done using tools like Cisco Packet Tracer, NetSim, OMNeT++,
NS2, NS3, etc.
 Experiment-6
Objective:-Socket programming using UDP and TCP (e.g., simple DNS, data & time
client/server, echo client/server, iterative & concurrent servers).

Brief Theory-

Socket programming- Socket programming is a way of connecting two nodes on a network

to communicate with each other. One socket(node) listens on a particular port at an IP, while
other socket reaches out to the other to form a connection. Server forms the listener socket
while client reaches out to the server.

UDP-UDP (User Datagram Protocol) is an alternative communications protocol to

Transmission Control Protocol (TCP) used primarily for establishing low-latency and loss-
tolerating connections between applications on the internet.

Figure 6.1: Clients and servers, Sockets and Server Sockets

6.1. To implement date server and client using TCP sockets.

Procedure:
Server:
1. Create an array of hosts and its ip address in another array

2. Create a datagram socket and bind it to a port

3. Create a datagram packet to receive client request

4. Read the domain name from client to be resolved

5. Lookup the host array for the domain name

6. If found then retrieve corresponding address

7. Create a datagram packet and send ip address to client

8. Repeat steps 3-7 to resolve further requests from clients

9. Close the server socket

10. Stop

Client:

1. Create a datagram socket

2. Get domain name from user

3. Create a datagram packet and send domain name to the server

4. Create a datagram packet to receive server message

5. Read server's response

6. If ip address then display it else display "Domain does not exist"

7. Close the client socket

8. Stop

6.2 To implement echo server and client using TCP sockets.

Server:

1. Create a server socket.

2. Wait for client to be connected.

3. Read text from the client

4. Echo the text back to the client.

5. Repeat steps 4-5 until ‘bye’ or ‘null’ is read.

6. Close the I/O streams

7. Close the server socket

8. Stop

Client:
1. Create a socket and establish connection with the server

2. Get input from user.

3. If equal to bye or null, then go to step 7.

4. Send text to the server.

5. Display the text echoed by the server

6. Repeat steps 2-4

7. Close the I/O streams

8. Close the client socket

9. Stop

6.3 Write a program to send and receive message between Client and Server using TCP.

Class:

Server Socket:

This class implements server sockets. A server socket waits for requests to come in over the
network. It performs some operation based on that request, and then possibly returns a result
to the requester.

Pseudo-code(methods) Description
ServerSocket() Creates an unbound server socket

ServerSocket(int port) Creates a server socket, bound to specified

port
accept() Listens for a connection to be made to this
socket and accepts it.
getInetAddress() Returns the local address of this server
socket.
getLocalPart() Returns the port on which this socket is
listening.
close() Closes this socket close()

Table 6.1: Server end Pseudo Code Description

6.4 Write a program to send and receive message between Client and Server using
UDP.

Class:
Datagram Socket:

This class represents a socket for sending and receiving datagram packets. A datagram
socket is the sending or receiving point for a packet delivery service. Each packet sent or
received on a datagram socket is individually addressed and routed. Multiple packets sent
from one machine to another may be routed differently and may arrive in any order.

User Datagram Protocol (UDP) broadcasts always enabled on a Datagram Socket. In order to
receive broadcast packets a Datagram Socket should be bound to the wildcard address. In
some implementations, broadcast packets may also be received when a Datagram Socket is
bound to a more specific address.

Datagram Packet: Datagram packets are used to implement a connectionless packet

delivery service. Multiple packets sent from one machine to another might be routed
differently, and might arrive in any order. Packet delivery is not guaranteed.

Pseudo-code(methods) Description
DatagramSocket(int port) Constructs a datagram socket and binds it
to any available port on the local host
machine.
receive(DatagramPacket p) Receives a datagram packet from this
socket
send(DatagramPacket p) Sends a datagram packet from this socket
DatagramPacket(byte[] buf, int length) Constructs a Datagram Packet for
receiving packets of length.
DatagramPacket(byte[]buf,int,length, Constructs a datagram packet for sending
InetAddress address, int port) packets of length to the specified port on
the specified host.
getData() Returns the data buffer
Table 6.2: Psedo Code Discription

Result- Socket programming using UDP and TCP is done.

\

Experiment-7
Objective: Configure and connect two PCs using Crossover and Straight forward wire
connection.
Apparatus required (Software): Cisco packet Tracer

Flow Chart:

Select two end devices

Connect the end devices via appropriate wire (Cross over or

straight forward)

Assign IP address to both PCs

Browse command prompt and enter ping the other side PCs Ip
address

Check on the reply if it appears then ok.

Pc to Pc connection
established

Figure7.1: PC to PC Connection flow chart

Procedure:
Step1: Select two end devices (PC, laptop, etc)
Move the cursor to the left corner of environment window and select the option after
click on end device PC0 and PC1.

Step2: Connect the end devices via appropriate wire (Cross over or straight forward)
Take straight forward wire and connect switch with PCs through switch. Take cross
over wire to directly connect with other PC.
\

Figure 7.2 Straight Forward connection for 2 PCs

Figure 7.3 Cross over connection for 2 PCs

Step3: Assign IP address to both PCs

Give Ip address to both PCs after going on desktop on each.

Step4: Browse command prompt and enter ping the other side PCs Ip address
Go to command prompt of any one of PCs and then enter command Ping IP address
of other PCS.
Step5: Check on the reply if it appears then ok.

After entering ping if reply shows then connection successfully established.

\

Experiment-8
Objective: Configure a DNS server in along with existing network using Cisco Packet
Tracer.
Apparatus required (Software): Cisco packet Tracer

Flow Chart:

Select two end devices

Connect the end devices with server via intermediate switch

Take one more HTTP server and add one website on that.

Add domain name and map it with logical address on DNS

server.

Check on the web browser after entering the website domain

name inside URL.

DNS Configuration
Successful

Figure 8.1: Flow chart of DNS server configuration

Procedure:
Step1: Select two end devices (PC, laptop, etc)
Move the cursor to the left corner of environment window and select the option after
click on end device PC0 and PC1.

Step2: Connect the end devices with server via intermediate switch
Take straight forward wire and connect switch with PCs and Server through switch.
\

Step3: Take one more HTTP server and add one website on that.
Select HTTP server after assigning IP address move connect it with same switch and
network. After that go on services and add HTTP html pages of the website.

Step4: Add domain name and map it with logical address on DNS server.
On DNS server go to services and select DNS service add here domain name of
website and map it with IP address.

Step5: Check on the web browser after entering the website domain name inside URL.
Go and check on any one of the web browser and then if website is showing then it is
successful.

Figure 8.2 DNS server Configuration

Result: DNS server have been configured successfully.

\

Experiment-9
Objective : Configure Routing Information Protocol (RIP) for an autonomous network
using Cisco Packet Tracer.

Apparatus required (Software): Cisco packet Tracer

Flow Chart:

Take inputs and start with a topology

Configure the interfaces on different routers as in static

configuration

Enable Dynamic Routing (RIP)

Enter classful network address

Check the connection using other side network IP address

No Is reply coming from

other Side?

Yes

Configuration Successful

Figure. 9.1 Flow Chart for RIP configuration

\

Procedure: RIPv1 sends updates as broadcasts to address 255.255.255.255.

Step1: Configure the Router as per the network topology shown in figure

Figure. 9.2 Topology for RIP

Step 2: Configure the interfaces on R1, R2, and R3 as in static configuration.

Configure the interfaces on the R1, R2, and R3 routers with the IP addresses from the table
under the Topology Diagram.
Step 3: Configure Ethernet interfaces of PC1, PC2, and PC3
Configure the Ethernet interfaces of PC1, PC2, and PC3 with the IP addresses and default
gateways from under the Topology Diagram.
Step4: Enable dynamic routing
To enable a dynamic routing protocol, enter global configuration mode and use the Router
command. Enter router? at the global configuration prompt to a see a list of available routing
protocols on your router.
To enable RIP, enter the command router rip in global configuration mode.
R1(config)#router rip
Step 5: Enter classful network addresses
Once We are in routing configuration mode, enter the classful network address for each directly
connected network, using the network command with the following command:
R1(config-router)#network 192.168.4.0
R1(config-router)#network 192.168.5.0
Repeat the same step 4 & 5 for R2 & R3.
Step 6: Check the connection using other side network IP address
Once the network configured then go to any one PCs desktop and enters the other network
address. See the output on command prompt.
ping 192.168.5.0
Step 7: If the reply comes connection will be considered as successful otherwise repeat
the same and troubleshoot from step 3 onward.

Input: Ip addressing, right connection and configuration commands as per procedures.

\

Output: Double click PC1 move to desktop then command prompt give the command ping
192.168.5.2 in PC1 you will get reply from PC3.

Result: RIP configuration have been done successfully.

\

Experiment-10
Aim: Configure an email server using Cisco Packet Tracer.

Apparatus required (Software): Cisco packet Tracer

Flow Chart:

Select end devices

Connect the end devices with email server via intermediate

switch

Take one more server and add one website on that.

Register users (PCs) email address and Password on email

server.

Compose mail from any one user to another user over the
network

Check at receiver side if the same mail is appearing

Email Configuration
Successful

Figure 11.1: Flow chart of email server configuration

\

Procedure:
Step1: Select two end devices (PC, laptop, etc)
Move the cursor to the left corner of environment window and select the option after
click on end device PC0 and PC1.

Step2: Connect the end devices with email server via intermediate switch

Take straight forward wire and connect switch with PCs and Server through switch.

Step3: Take one more server and add one website on that.
Select server after assigning IP address move connect it with same switch and
network. After that go on services and add HTTP html pages of the website.

Step4: Register users (PCs) email address and Password on email server.
On email server go to services and select email service register here users ID
password.

Step5: Compose mail from any one user to another user over the network
Go and check on any one user side after composing an email for another user and then
Send it.
Step6: Check at receiver side if the same mail is appearing.
Go and check on receiving user side if same emails have been received then ok.

Figure 11.2 Email Server Configuration

Result: An email server has successfully configured.