MAHARAJA AGRASEN INSTITUTE OF TECHNOLOGY

VISION OF THE INSTITUTE

To nurture young minds in a learning environment of high academic value and imbibe spiritual
and ethical values with technological and management competence.

MISSION OF THE INSTITUTE

The Institute shall endeavor to incorporate the following basic missions in the teaching
methodology:
Engineering Hardware – Software Symbiosis
Practical exercises in all Engineering and Management disciplines shall be carried out by
Hardware equipment as well as the related software enabling deeper understanding of basic
concepts and encouraging inquisitive nature.

Life – Long Learning

The Institute strives to match technological advancements and encourage students to keep
updating their knowledge for enhancing their skills and inculcating their habit of continuous
learning.

Liberalization and Globalization

The Institute endeavors to enhance technical and management skills of students so that they are
intellectually capable and competent professionals with Industrial Aptitude to face the challenges
of globalization.

Diversification
The Engineering, Technology and Management disciplines have diverse fields of studies with
different attributes. The aim is to create a synergy of the above attributes by encouraging
analytical thinking.

Digitization of Learning Processes

The Institute provides seamless opportunities for innovative learning in all Engineering and
Management disciplines through digitization of learning processes using analysis, synthesis,
simulation, graphics, tutorials and related tools to create a platform for multi-disciplinary
approach.

Entrepreneurship
The Institute strives to develop potential Engineers and Managers by enhancing their skills and
research capabilities so that they become successful entrepreneurs and responsible citizens.
 MAHARAJA AGRASEN INSTITUTE OF TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

VISION OF THE DEPARTMENT

To establish a center of excellence promoting Information Technology related education and

research thus producing technocrats and entrepreneurs with ethical values.

MISSION OF THE DEPARTMENT

To provide an open, diverse and collaborative environment to achieve global technological

excellence producing world-class engineers to solve real-world problems fulfilling the needs of
the society.
 MAHARAJA AGRASEN INSTITUTE OF TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

PROGRAM OUTCOMES (POs)

PO1 Engineering knowledge: Apply the knowledge of mathematics, science,

engineering fundamentals, and an engineering specialization to the solution
of complex engineering
PO2 Problem analysis: Identify, formulate, review research literature, and
analyze complex engineering problems reaching substantiated conclusions
using first principles of
PO3 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.
PO4 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.
PO5 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.
PO6 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.
PO7 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.
PO8 Ethics: Apply ethical principles and commit to professional ethics and
responsibilities and norms of the engineering practice.
PO9 Individual and team work: Function effectively as an individual, and as a
 member or leader in diverse teams, and in multidisciplinary settings.
PO10 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.
PO11 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.
PO12 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.
 MAHARAJA AGRASEN INSTITUTE OF TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

PROGRAM EDUCATIONAL OBJECTIVES (PEOs)

PEO1 Our graduates will succeed in their career pursuits by applying their technical
skills for higher degrees.
PEO2 Our graduates will be able to devise innovative solutions for real-world problems
by applying Information Technology principles.
PEO3 Our graduates will exhibit high standards of professionalism, demonstrate strong
interpersonal and collaborative abilities with adherence to professional ethics.
PEO4 Our graduates will be able to use research opportunities, and thrive as successful
entrepreneurs.
 MAHARAJA AGRASEN INSTITUTE OF TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

PROGRAM SPECIFIC OUTCOMES (PSOs)

PSO1 Proficient at discerning suitable data structures and algorithms for

designing, executing, and validating efficient solutions for research-
oriented challenges.
PSO2 Attaining excellence in programming, technical projects and handling
technical challenges.
PSO3 Acquiring adequate knowledge in Information Technology for a successful
professional life, entrepreneurship and higher education.
 CO of the lab subject and its mapping with PO AND PSO

Course Outcomes (CO) to Programme Specific Outcomes (PSO) mapping (scale 1: low, 2: Medium, 3:
High)

PSO01 PSO02 PSO03

CO 1 3 2 2
CO 2 3 2 2
CO 3 3 2 2
CO 4 3 2 2
 EXPERIMENT – 1

Aim: Introduction to Networking Simulation Tools: Wireshark, Cisco Packet

Tracer

Theory:
 EXPERIMENT – 2

Aim: To understand the operation of TELNET by accessing the router in server room from a
PC in IT office.

Requirements
– 2 Nos

– 1 No
– 1 Nos
-5 LAN cable

Procedure

password; in command prompt of PC.

Theory:
 Router 0 PC0 PC1
IP Address : 192.168.0.1 IP Address : 192.168.0.2 IP Address : 192.168.0.3
Gate way : - Gate way : 192.168.0.1 Gate way : 192.168.0.2

Input Details for TELNET

ROUTER CLI:

Router#config
Configuring from terminal, memory, or network [terminal]?
Router(config)#line vty 0 4
Router(config-line)#password sai123
Router(config-line)#login local
Router(config-line)#exit
Router(config)#username sai privilege 4 password sai123
Router(config)#exit

OUTPUT:
PINGING FROM PC0 TO SERVER USING TELENET:
C:\>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
C:\>telnet 192.168.0.1
Trying 192.168.0.1 ...Open
User Access Verification
Username: sai
Password: <type the password---sai123(invisible)>
Router#show ip route(now router can be accessed from pc0)
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
192.168.0.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.0.0/24 is directly connected, GigabitEthernet0/0
L 192.168.0.1/32 is directly connected, GigabitEthernet0/0
Router#
Result:
Thus, verified the operation of TELNET and accessed the router from Pcs.
 VIVA QUESTIONS

What are common uses for Telnet?

Telnet can be used to test or troubleshoot remote web or mail servers, as well as for
remote access to MUDs (multi-user dungeon games) and trusted internal networks.

How does Telnet work?

Telnet provides users with a bidirectional interactive text-oriented communication system
utilizing a virtual terminal connection over 8 byte. User data is interspersed in-band with telnet
control information over the transmission control protocol (TCP). Often, Telnet was used on a
terminal to execute functions remotely.
The user connects to the server by using the Telnet protocol, which means entering Telnet
into a command prompt by following this syntax: telnet hostname port. The user then executes
commands on the server by using specific Telnet commands into the Telnet prompt. To end a
session and log off, the user ends a Telnet command with Telnet.

Is Telnet secure?
Because it was developed before the mainstream adaptation of the internet, Telnet on its
own does not employ any form of encryption, making it outdated in terms of modern security. It
has largely been overlapped by Secure Shell (SSH) protocol, at least on the public internet, but
for instances where Telnet is still in use, there are a few methods for securing your
communications
 EXPERIMENT – 3

Aim: Implementation of IP Addressing Scheme and Subnetting in Small Networks using Cisco
Packet Tracer

Theory:
Understanding IP Addressing:

IP Address Basics:

● An IP address is a unique numerical label assigned to each device on a network.

● It is used for identification and communication within a network.
● IP addresses are divided into two main types: IPv4 and IPv6.
IPv4 Addressing:
● IPv4 is the most widely used IP version.
● It uses a 32-bit address represented in four decimal octets (e.g., 192.168.1.1).
● IPv4 addresses are divided into classes (A, B, C, D, E) and further categorized into public
and private IP addresses.

IP Addressing Scheme:

Choosing an IP Address Range:

● In our scenario, we select a private IPv4 address range to build our small network:
192.168.0.0/24.
● Private IP address ranges are reserved for internal network use and are not routable on the
public internet.
Allocating IP Addresses:

● We allocate specific IP addresses to network devices like routers, switches, and PCs.
● For example, the router is assigned 192.168.0.1, and switches follow with consecutive
addresses.

Subnetting:

What is Subnetting?

● Subnetting is the process of dividing a larger IP network into smaller, more manageable
sub-networks or subnets.
● It helps optimize IP address allocation, enhances network security, and reduces broadcast
traffic.
Implementing Subnetting:

● We implement subnetting within our network by dividing our 192.168.0.0/24 range into
four smaller subnets.
● Each subnet is assigned a unique subnet mask based on its size.

Subnet Examples:

● Subnet 1 (Marketing): 192.168.0.0/27

● Subnet 2 (Sales): 192.168.0.32/27
● Subnet 3 (IT): 192.168.0.64/27
● Subnet 4 (Guest): 192.168.0.96/27

Cisco Packet Tracer Implementation:

Using Cisco Packet Tracer:

● Cisco Packet Tracer is a network simulation tool that allows us to create virtual network
environments.
● It enables us to configure routers, switches, and end-user devices, providing a practical
learning platform.

Network Topology Design:

 ● We design a network topology with routers as gateways, switches for local connectivity,
and PCs as end-user devices.
● This topology reflects a simplified small office or home office (SOHO) environment.

Device Configuration:

● Within Packet Tracer, we configure devices with their assigned IP addresses, subnet
masks, and default gateways.
● We ensure that each device has a unique IP address within its subnet.

Subnetting in Cisco Packet Tracer can be done using the built-in tools and commands available
in Cisco devices. Here are the basic steps of how to subnet in Cisco Packet Tracer:

1. Create Your Network Topology:

- Open Cisco Packet Tracer and create a network topology by adding routers, switches, and end
devices as needed.

2. Access Router Command Line Interface (CLI):

- Double-click on a router to open its CLI.

3. Configure the Router:

- Enter privileged exec mode by typing enable and then enter global configuration mode by
typing configure terminal or simply conf t.

4. Define IP Address on an Interface:

- To assign an IP address to a router interface, use the following command:

interface <interface_type><interface_number>
ip address <ip_address> <subnet_mask>

Example:
 interface GigabitEthernet0/0
ip address 192.168.1.1 255.255.255.0

5. Subnetting:
- To perform subnetting, you can use the ip subnet-zero command to enable subnetting on the
router (though this is not necessary in modern networks).
- You can then create additional subnets by configuring other interfaces with different IP
addresses and subnet masks.

6. Save Configuration:
- After making changes, save the router's configuration by typing end and then write memory
or simply wr.

7. Exit Router Configuration Mode:

- Type exit to exit from configuration mode, and then exit again to return to privileged exec
mode.

8. Verify Configuration:
- You can verify your subnetting configuration by using commands like show ip interface brief
and show running-config.

Conclusion:
In conclusion, mastering IP addressing and subnetting is pivotal for effective network
management. Using Cisco Packet Tracer, we've demonstrated the practical implementation of
these concepts in a small network environment. This knowledge is essential for network
professionals to design and manage networks efficiently and securely.
 EXPERIMENT – 4

Aim: To implement Static Routing Using Cisco Packet Tracer

Theory:
How to configure a simple static routing in packet tracer using a simple topology with two
routers
Steps:
Step 1:First Create a topology like this,you will get a red light first this is configured topology

Step 2: Configure ip address to routers go to global configuration mode in R1 and R2 configure

connected interfaces

In Router 1

Interface Fastethernet0/0 in global configuration mode

R1(config)#interface fastethernet 0/0
R1(config-if)#ip address 10.0.0.1 255.0.0.0
R1(config-if)#no shutdown
R1(config-if)#exit

Interface Serial 2/0

R1(config)#interface serial 2/0

R1(config-if)#ip address 20.0.0.1 255.0.0.0
R1(config-if)#clock rate 64000
R1(config-if)#encapsulation ppp
R1(config-if)#no shutdown
R1(config-if)#exit

In Router 2
Interface Fastethernet 0/0

R2(config)#interface fastethernet 0/0

R2(config-if)#ip address 30.0.0.1 255.0.0.0
R2(config-if)#no shutdown
R2(config-if)#exit
Interface Serial 2/0

R2(config)#interface serial 2/0

R2(config-if)#ip address 20.0.0.2 255.0.0.0
R2(config-if)#encapsulation ppp
R2(config-if)#no shutdown
R2(config-if)#exit

Step 3 : Assign ip address for both Pc's with appropriate ip and subnetmask and default gateway

Step 4: Now configure both router with static route

By default Routers Know only directed connected networks here Router 1 know only 10.0.0.0
and 20.0.0.0 it doesn't know the 30.0.0.0 like this R2 doesn't know about 10.0.0.0.So We are
going to add Static route to this both router
R1(config)#ip route Destination Network| Destination N/W Subnet Mask |Next Hop Address
In Router R1,Just give this command, In this case Destination is 30.0.0.0 and its subnet mask is
255.0.0.0 next hop address is 20.0.0.2

R1(config)#ip route 30.0.0.0 255.0.0.0 20.0.0.2

In Router R2

R2(config)#ip route 10.0.0.0 255.0.0.0 20.0.0.1

Now both routers know all networks, check by ping ip address of host
Step 5: Double click PC move to desktop then command prompt give the command ping
30.0.0.10 in PC 0 you will get reply from 30.0.0.10 like this
 EXPERIMENT NO. 5

AIM : Configure DHCP Server in the Network using packet tracer software.

Theory:
STEPS :

1. Launch Packet Tracer: Open the Packet Tracer software on your computer.
2. Create the Network Topology: Set up the network topology by adding the necessary
devices such as routers, switches, and PCs. Connect them appropriately using Ethernet
cables.
3. Configure IP addresses: Assign IP addresses to each device in the network manually or
using a static IP address assignment. Add and Configure DHCP Server: Select a router or
a dedicated server device in the network where you want to configure the DHCP server.
Right-click on the device and select "Config" to enter the device's configuration mode.
4. Access Global Configuration Mode: In the device configuration mode, enter the global
configuration mode by typing the command "enable" and then "configure terminal" to
access the router's or server's global configuration settings.
5. Enable DHCP Service: Type the command "service dhcp" to enable the DHCP service
on the device.
6. Configure DHCP Pool: Define a DHCP pool by typing the command "ip dhcp pool
[pool name]" and press Enter. Replace [pool name] with a name of your choice for the
pool.
7. Set IP Address Range: Specify the range of IP addresses that the DHCP server can
assign to devices in the network. Use the command "network [network address] [subnet
mask]" to define the network address and subnet mask for the pool. For example,
"network 192.168.1.0 255.255.255.0".
8. Configure Default Gateway: Set the default gateway for the devices in the network by
using the command "default-router [gateway IP address]". Specify the IP address of the
default gateway or router that provides access to other networks.
9. Set DNS Server: Specify the DNS (Domain Name System) server address that will be
provided to the devices by using the command "dns-server [DNS server IP address]".
Enter the IP address of the DNS server that devices should use for name resolution.
10. Set Lease Duration: Define the lease duration for IP addresses assigned by the DHCP
server using the command "lease [duration]". Specify the desired duration in hours, days,
or other time units. For example, "lease 24".
11. Exit Configuration Mode: Once you have completed the DHCP server configuration,
exit the device configuration mode by typing the command "exit" until you return to the
user mode.
12. Save Configuration: Save the configuration changes by typing the command "copy
running-config startup-config" to ensure that the configuration is persistent even after
restarting the network simulation.
13. Test DHCP Configuration: Start the simulation in Packet Tracer and verify that the
DHCP server is functioning correctly by checking if the devices connected to the network
are assigned IP addresses automatically.
 EXPERIMENT – 6

Aim : To implement the DNS, Email Services in the Network using Cisco Packet
Tracer.

Theory:
Steps :
1. Build the network topology:
2. Configure IP addresses on the PCs, DNS Server and the Mail Server.
Mail Server IP address: 192.168.1.2/24
PC0 IP address: 192.168.1.3/24
PC1 IP address: 192.168.1.4/24
DNS server IP address: 192.168.1.5/24
3. Now configure mail clients on the PCs and mail service on the generic server.
4. Configure the mail clients
Click on PC0. Go to its Desktop tab, and click on Email. Configure the email client by
filling in the user, server and login information. Be sure to Save.
5. Configure the email server.
6. To do this, click on the server, then click the Services tab, and pick the email server from
the menu.
7. Provide the Domain name of the server then click on Set to set it. In this example, We‘ve
used the name ‗mail.com‘.
8. Proceed and add users and provide their passwords. We have two email clients(users)
with usernames ‗client1‘ and ‗client2‘ with a common password ‗adminkim‗
9. After entering a username and password, click on Add(+) to add the user to the server.
You can optionally remove a user by clicking on Remove (-). You can change a user‘s
password by clicking on change password.

10. We set a domain name for the email server. For that reason, we should have a DNS
server that will resolve this domain name (plus other domain names if there were) to an
IP address.

11. Configure a DNS server.

Click DNS server, click Services tab, then pick DNS. Turn the service ON. Set name-
address pairs and add them to the server. You can view the DNS entry below.
12. Lastly test the email service. Go to PC0 email client, compose an email and send its to
PC1 email address ([email protected]).
13. See whether the email from PC0 is received on PC1. On the email client of PC1, click on
Receive. The email from PC0 will be well received on PC1.
 EXPERIMENT – 7

AIM: To implement the dynamic routing protocols: RIP, IGRP using cisco packet
tracer.

Requirements
Windows pc – 2 Nos
CISCO Packet Tracer Software (Student Version)
8 port switch – 2 No
Router – 2 Nos
Cat-5 LAN cable

Procedure
Open the CISCO Packet tracer software
Drag and drop 5 pcs using End Device Icons on the left corner
Select 8 port switch from switch icon list in the left bottom corner
Select Routers and Give the IP address for serial ports of router and apply clock rate as
per the table.
Make the connections using Straight through Ethernet cables
Ping between PCs and observe the transfer of data packets in real and simulation mode.
Theory:
Input Details for RIP

PC0 - IP Address : 192.168.1.2 Gate way : 192.168.1.1

PC1- IP Address : 192.168.2.2 Gate way : 192.168.2.1
Router 0- Fast Ethernet 0/0 IP Address: 192.168.1.1
Serial 2/0 : 10.0.0.1
Router 1- Fast Ethernet 0/0 IP Address : 192.168.2.1
Serial 2/0 : 10.0.0.2

OUTPUT:

RIP (PINGING FROM PC0 TO PC1):

C:\>ping 192.168.2.2
Pinging 192.168.2.2 with 32 bytes of data:
Reply from 192.168.2.2: bytes=32 time=11ms TTL=126 Reply from
192.168.2.2: bytes=32 time=12ms TTL=126

Reply from 192.168.2.2: bytes=32 time=13ms TTL=126

Reply from 192.168.2.2: bytes=32 time=11ms TTL=126

Ping statistics for 192.168.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate
round trip times in milli-seconds: Minimum = 11ms, Maximum =
13ms, Average = 11ms

Result:
Thus, understand the concept and operation of RIP and pinged from PC in are networks
to PC to another network.
 Experiment: 8
AIM : To construct multiple router networks and understand the operation of
EIGRP Protocol

Requirements
– 4 Nos

– 2 No
– 3 Nos
-5 LAN cable

Procedure

8 port switch from switch icon list in the left bottom corner

rate as per the input table.

-IT Peripheral to all routers, type CLI‘s for all routers
e connections using Straight through Ethernet cables
Theory:
Input Details for EIGRP
PC0 PC1 PC2 PC3
IP Address : IP Address: IP Address: IP Address:
192.168.10.2 192.168.10.3 192.168.30.2 192.168.30.3
Gate way : Gate way : Gate way : Gate way :
192.168.10.1 192.168.10.1 192.168.30.1 192.168.30.1

Router 0 Router 1
fa 0/0 IP Address: 192.168.10.1 fa 0/0 IP Address : 192.168.30.1
Serial 0/0/0 : 192.168.20.1 @ 6400 clock rate Serial 0/0/0 : 192.168.20.2

ROUTER0 CLI:
Router(config)#router eigrp 10
Router(config-router)#network 192.168.10.0 255.255.255.0
Router(config-router)#network 192.168.20.0 255.255.255.0
Router(config-router)#exit
ROUTER1 CLI:
Router(config)#router eigrp 10
Router(config-router)#network 192.168.20.0 255.255.255.0
%DUAL-5-NBRCHANGE: IP-EIGRP 10: Neighbor 192.168.20.1 (Serial0/1/0) is up: new
adjacency
Router(config-router)#network 192.168.30.0 255.255.255.0
Router(config-router)#exit

OUTPUT:

ROUTER0:
Router#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
C 192.168.10.0/24 is directly connected, FastEthernet0/0
C 192.168.20.0/24 is directly connected, Serial0/3/0
D 192.168.30.0/24 [90/20514560] via 192.168.20.2, 00:04:51, Serial0/3/0
ROUTER1:
D 192.168.10.0/24 [90/20514560] via 192.168.20.1, 00:05:35, Serial0/1/0
C 192.168.20.0/24 is directly connected, Serial0/1/0
C 192.168.30.0/24 is directly connected, FastEthernet0/0

Result:
Thus, understand the concept and operation of EIGRP and obtained the routing table
and observe transfer data packets in real and simulation time.
 VIVA QUESTIONS

Why EIGRP is called hybrid protocol?

EIGRP is also called hybrid protocol because its metric is not just plain HOP
COUNT (max-255, included in pure distance vector protocol) rather includes the
links bandwidth, delay, reliability and Load parameter into the calculation. Thats
why called Advanced or Hybrid protocol.

What are the different packets or message in EIGRP?

There are Six packets in EIGRP, 1-Hello , 2-Update, 3-Query, 4-Reply, 5-
Acknoladgment, 6.Request

What are different route types in EIGRP?

There are three different types of routes in EIGRP:
—Routes that are originated within the Autonomous System (AS).
—Routes that are summarized in the router (for example,
internal paths that have been summarized).
—Routes that are redistributed to EIGRP.
 EXPERIMENT – 09

AIM: To implement the Network Address Resolution (NAT) using Cisco Packet
Tracer.

Theory:
In the figure above, PCA with an IP address of 172.31.1.2 wants to reach the webserver, but
because PCA‘s address is not routable, it cannot access the webserver directly.

Instead, the NAT-enabled router translates the PC‘s private address of 172.31.1.2 to a public
address of 200.100.100.2, which is routable over the internet.

From the server‘s perspective, it sees this address as the source address. Suppose the server
wants to send data to the PC, it will use the same source address as its destination address.

When the data reaches the NAT-enabled router, the public address is then translated back to its
original private address, and the data is forwarded back to the PC.

Types of NAT

Network address translation can be classified into three types.

They are:

1. Static Network Translation (Static NAT)

2. Dynamic Network Address Translation (Dynamic NAT)
3. Port Address Translation (PAT)

Static NAT

Static NAT creates a one-to-one mapping between private and public addresses.

Static NAT is usually configured by a network administrator, and this configuration remains
constant.

In the figure above, PCA and PCB wants to reach PCC, which is a remote network.

But because both are configured with private addresses, they can not access PCC directly.

To access PCC, a NAT-enabled router is configured with static NAT, that maps their private
addresses to public addresses using one-to-one relationship, thus allowing them to communicate
with PCC.

Therefore, static NAT is useful for a device that needs a dedicated address, such as a web server.
But, it requires an equal number of public addresses for users using them simulataneously.
Dynamic NAT

Similar to static NAT, the dynamic NAT gives a one-to-one mapping between private and public
addresses. But, the mapping is done dynamically.

Dynamic NAT makes a pool of public addresses and assigns them to private addresses on a first-
come-first-served (FCFS) basis to determine which private addresses ought to be translated.

In the figure above, an organization is assigned to four different public addresses, but the
organization can have more than four internal devices that require access to the internet.

To resolve this problem, the network administrator decides to configure dynamic NAT to allow
these devices to access the internet.

If all the internal devices have been assigned to all the available global addresses, then the device
requesting for a public address will have to wait until one is made available.

Port Address Translation (PAT)

Dynamic NAT is more commonly used by organizations, to connect their devices to the internet.
If their network is large, it requires a huge set of registered public addresses. Thus, it completely
defeats NAT‘s goal.

Dynamic NAT reduces this problem to some degree. However, if a large percentage of internal
hosts need access to the internet then, we must use Port Address Translation, also called NAT
overload.

To understand how PAT works, it is important to recall how the host uses the Transmission
Control Protocol (TCP), User Datagram Protocol (UDP) and port numbers to transmit data.

To learn more about TCP and UDP, it is highly recommeded to go over this article before
continuing to read.

With these protocols, PAT can map multiple private addresses to one or more public addresses
by ensuring that devices use different TCP and UDP port numbers for each session.
NAT configuration

In the first half of this article, we learned briefly about NAT and the different types of NAT.

In the second part, we will cover how to implement static NAT, dynamic NAT, and PAT on a
Cisco router.

Static NAT

Steps to configure static NAT

Static NAT can be configured using the following two steps.

They are:

1. Creating a mapping between the private internal address and public global address using
the ip nat inside source static [private-address] [public-address] global configuration
command.
2. After the mapping is made, the interfaces taking part in the NAT translation are
configured as either inside or outside with respect to NAT.

The router interface associated within the LAN is assigned the inside interface using the ip nat
inside interface mode command.

Similarly, the router interface associated with the internet is assigned the outside interface using
the ip nat inside interface mode command.

In the figure above, the Gigabit 0/0 (g0/0) interface is the inside interface because it is connected
to the LAN. In contrast, the S0/0/0 interface is configured as the outside interface because it is
connected to the internet.

Configuring static NAT

To configure a static NAT between the private address 172.31.1.2 and public
address 200.100.100.2:

● Map the server‘s private address 172.31.1.2 to the public routable

address 200.100.100.2 using the command ip nat inside source static 172.31.1.2
200.100.100.2.
● Enter the ―interface serial s0/0/0/‖ command and identify the interface as the outside
interface using the command ip nat outside.
 ● Enter the ―interface gigabitethernet g0/0‖ command and identify it as the inside interface
relative to NAT using the ip nat inside command.

Dynamic NAT

Steps to configure dynamic NAT

Dynamic NAT still requires that both the inside and the outside interfaces be configured.

For allocation, it uses an access control list (ACL) to specify which private addresses are subject
to translation and a NAT pool of registered IP addresses.

1. Create an ACL using the access-list 1 permit address wildcard mask command.
2. Create a NAT pool using the ip nat pool [name] [first-address] [last-address] [netmask]
[subnet mask] global configuration command.

This pool will contain the public addresses for the translation. Because, ISP assigns the public
addresses contiguous to the organizations.

The first address is the least in the given address range. And, the last address is the highest
address of that range.

The netmask identifies the network to which of these addresses belong to, using the ip nat inside
source list [access-list] [number] pool [name] command to bind the ACL and the NAT Pool
created.

In this case, the ACL number is 1, and the NAT POOL is LAN.

NOTE: Different ACL numbers and pool names can be created and used, but ACL 1 and pool
name LAN will be used throughout this tutorial for simplicity.
 1. Use the ip nat inside interface command to enable the inside interface for NAT
translation
2. Use the ip nat outside interface command to enable the outside interface for NAT
translation.

Configuring dynamic NAT

An organization is assigned with two public addresses: 200.100.100.1 and 200.100.100.2. It

wants to allow its internal hosts, in the private network 172.31.1.0 and 255.255.255.0 to reach
the internet using dynamic NAT.

To configure the dynamic NAT for the network topology above:

● Create an access list that will specify the private addresses that are allowed to be
translated using the access-list 1 permit 172.31.1.0 0.0.0.255.
● Creates a pool that will contain the public addresses to be utilized for translation using
the ip nat pool LAN 200.100.100.1 200.100.100.1 netmask 255.255.255.0.
● Bind the access list and the pool together using the ip inside source list 1 pool LAN. This
allows for the dynamic translation of the private addresses and the public addresses in a
NAT pool named LAN.
● Enter the interface serial 0/0/0/ command and identify it as an outside interface using
the ip nat outside command.
● Enter the interface gigabitethernet g0/0 command and identify it as the inside interface
using the ip nat inside command.
PAT with multiple addresses

If an organization is to be assigned more than one public address by an Internet Service Provider
(ISP), then configuring PAT looks exactly like a dynamic NAT, except that the ip nat inside
source list--- pool command in step 3, with an overload keyword added at the end.

Steps to configure PAT with multiple public addresses

1. Create an ACL using the access-list 1 permit [address][ wildcard mask].

2. Create a NAT pool using the ip nat pool [name] [first-address] [last-address] [netmask]
[subnet mask] global configuration command. This pool will contain the public addresses
to be used for the translation.
3. The ip nat inside source list [ACL] [number] pool [name] overload The full command
is ip nat inside source list 1 pool LAN overload.
4. Use the ip nat inside interface command to enable the inside interface for NAT
translation
5. Use the ip nat outside interface command to enable the outside interface for NAT
translation.

Configuring PAT with multiple public addresses

An organization is assigned to two public addressees: 200.100.100.1 and 00.100.100.2, and it

wants to allow its internal hosts, in the private network 172.31.1.0 - 255.255.255.0 to reach the
internet using PAT.

To configure PAT for the network topology above, the following steps are applied:

1. Create an ace list that will specify which private addresses are allowed to be translated
using the access-list 1 permit 172.31.1.0 0.0.0.255
2. ip nat pool LAN 200.100.100.1 200.100.100.1 [netmask] 255.255.255.0 creates a pool
that contains the public addresses to be used for translation.
3. Bind the access list and the pool together using the ip inside source list 1 pool LAN
overload. This allows for the dynamic mapping of the private addresses and the public
address in the NAT pool named LAN. The overload keyword used here is the only
configuration difference between PAT and dynamic NAT.
4. Enter the interface serial 0/0/0/ to identify the interface as the outside interface using
the ip nat outside command.
5. Enter gigabitethernet g0/0 using the interface gigabitethernet g0/0 command and identify
it as the inside interface relative to NAT with the ip nat inside command.
Steps to configure PAT with a single address

If an organization is assigned a single public address by an ISP. Then, PAT can be configured
with a little changes when compared to PAT with multiple addresses.

In this situation, a NAT pool is not created, but an outside interface used for the translation is
used in place of the NAT pool as mentioned in step 3 above.

1. Create an ACL using the access-list 1 permit [address] [wildcard mask].

2. PAT is enabled using the ip nat inside source list [ACL] [number] interface [interface-
type/number] overload. The interface used for this is an outside interface, and it‘s
configured as the single public address assigned to the organization by an ISP.
3. Use the ip nat inside interface command to enable the inside interface for Nat translation.
4. Use the ip nat outside interface command to enable the outside interface for NAT
translation.

Configuring PAT with one public address

An organization is assigned one public address 200.100.100.1, and it wants to allow its internal
hosts in the private network 172.31.1.0 - 255.255.255.0 to reach the internet using PAT.

To configure PAT for the topology above, the following steps will be applied:

1. Create an ace list that will specify which private addresses are allowed to be translated,
using the access-list 1 permit 172.31.1.0 0.0.0.255 command.
2. Bind the access list and the outside interface together using the ip inside source list 1
interface s0/0/0 overload.
3. Enter the interface serial 0/0/0/ command to identify it as an outside interface relative to
NAT using the: ip nat outside command.
 4. Enter the interface gigabitethernet g0/0 command and identify it as an inside interface
relative to NAT using the ip nat inside command.

The figure above shows the configuration of PAT using one public address on a Cisco router.
 EXPERIMENT – 10

AIM: Conducting A Network Capture and Monitoring With Wireshark Tool

Theory:
FEATURE:
● Available for UNIX and Windows.
● Capture live packet data from a network interface.
● Display packets with very detailed protocol information.
● Open and Save packet data captured.
● Import and Export packet data from and to a lot of other capture programs.
● Filter packets on many criteria.
● Search for packets on many criteria.
● Colorize packet display based on filters.
● Create various statistics.

CAPTURING PACKETS
After downloading and installing Wireshark, you can launch it and click the name of an interface
under Interface List to start capturing packets on that interface. Wireshark, formerly known as
Ethereal, is an amazing Network Monitoring tool. It helps you to capture the data packets being
sent/received by your network interface and analyze it.
For example, if you want to capture traffic on the wireless network, click your wireless interface.
You can configure advanced features by clicking Capture Options, but this isn‘t necessary for
now.
Before capturing packets, configure Wireshark to interface with an 802.11 client device;
otherwise, you‘ll get an alert ―No capture interface selected!‖ when starting a packet capture. To
select an interface, click the Capture menu, choose Options, and select the appropriate interface.
To start the packet capturing process, click the Capture menu and choose Start. Wireshark will
continue capturing and displaying packets until the capture buffer fills up. The buffer is 1 Mbytes
by default. This size is generally good enough, but to change it click the Capture menu, choose
Options, and adjust the Buffer size value accordingly. When you‘re done capturing packets, click
the Capture menu and choose Stop.
Alternatively, you can set the capture run length (in packets or minutes), and the capture will
automatically stop when that length has been met. You‘ll be prompted to save the capture for
later viewing.
The packet capture will display the details of each packet as they were transmitted over the
wireless LAN. Figure 2 is a screenshot of a sample packet capture window. The top panel of the
window identifies each packet‘s source and destination nodes, protocol implemented, and
information about each packet. You can select a specific packet to display more details. The
middle panel displays information about this packet, and you can choose a specific field of the
packet and the contents of that field are displayed in hex and ASCII format in the bottom panel.
As a result, you‘re able to analyze the flow and view each field (including data field payloads) of
all packets.

II. FILTERING PACKETS

Once you have opened the wireshark, you have to first select a particular network interface of
your machine. In most of the cases the machine is connected to only one network interface but in
case
there are multiple, then select the interface on which you want to monitor the traffic. From the
menu, click on ‘Capture –> Interfaces’, which will display the following screen.

I. SOURCE IP FILTER
A source filter can be applied to restrict the packet view in wireshark to only those packets that
have source IP as mentioned in the filter. The filter applied in the example below is: ip.src ==
192.168.1.1

II. DESTINATION IP FILTER

A destination filter can be applied to restrict the packet view in wireshark to only those packets
that have destination IP as mentioned in the filter. For example: ip.dst == 192.168.1.1

III. FILTER BY PROTOCOL

Its very easy to apply filter for a particular protocol. Just write the name of that protocol in the
filter tab and hit enter. In the example below we tried to filter the results for http protocol using
this filter: http
USING OR CONDITION IN FILTER
This filter helps filtering the packets that match either one or the other condition. Suppose, there
may arise a requirement to see packets that either have protocol ‗http‘ or ‗arp‘. In that case one
cannot apply separate filters. So there exists the ‗||‘ filter expression that OR two conditions to
display packets matching any or both the conditions. In the example below, to filter the http or
arp packets using this filter: http||arp

IV. APPLYING AND CONDITION IN FILTER

This filter helps filtering packet that match exactly with multiple conditions. Suppose there is a
requirement to filter only those packets that are HTTP packets and have source ip as
‘192.168.1.4′. For Exam:. http&&ip.src==192.168.1.4

V. FILTER BY PORT NUMBER

This can be done by using the filter ‗tcp.port eq [port-no]‗. Forexample: tcp.port eq 80

VI. MATCH PACKETS CONTAINING A PARTICULAR SEQUENCE

The filter syntax used in this is: ‗[prot] contains [byte sequence]‗. tcp contains 01:01:04

VII. REJECT PACKETS BASED ON SOURCE OR DESTINATION

Filter here is ‗ip.src != [src_addr]‗ or ‗ip.dst != [dst_add]‗. ip.dst != 192.168.1.1
In the capture menu it‘s showing Source IP-address, Destination IP-address, Protocol
Information about packet and some packet information. Its lots of data. Now you need to be find
out the data
your work like i want to see the HTTP packets passing from my network. So in the Filter menu i
need to be writing HTTP or click on the Filter option to find out the Filter option.
It will show more awesome information about particular packet
III. INSPECTING PACKETS
Click a packet to select it and you can dig down to view its details.

Wireshark Inspecting Packets

You can also create filters from here — just right-click one of the details and use the Apply as
Filter submenu to create a filter based on it.
Apply as filter Wireshark is an extremely powerful tool, Professionals use it to debug network
protocol implementations, examine security problems and inspect network protocol internals

IV. PROTOCOL HIERARCHY

Wireshark can provide a statistical breakdown of the contents of a packet capture. The protocol
hierarchy shows a dissection per OSI layer of the displayed data. Click on Statistics>Protocol
Hierarchy. After processing the capture file you‘ll be presented with a chart outlining the
protocol statistics.

Protocol Statistics
Graph Analysis

V. IO GRAPHS AND THROUGHPUT GRAPH

The I/O graph will show you the throughput of all traffic in the trace file, in both directions.
Basic graphics can be obtained under the "IO graphs" section. Multiple graphics can be added in
the same window on a per display filter base. In our example below, we chose to draw two
graphs depending on a "tcp" and "http" display filter. Statistic=> menu=>IO Graph.
IO Graph
The TCP Stream Throughput graph will show only the throughput from one TCP stream, in
onedirection, based on the selected packet. From the Statistics menu, navigate to TCP
StreamGraph |Throughput Graph

TCP Stream Graph | Throughput Graph

 EXPERMENT 11

Aim: To construct a Wireless LAN and make the PC‘s communicate wirelessly

Requirements
• Windows pc – 2 Nos
• CISCO Packet Tracer Software ( Student Version)
• 8 port switch – 1 No
• Cat-5 LAN cable

Theory:
Procedure
• Open the CISCO Packet tracer software
• Drag and drop 2 Laptop pcs using End Device Icons on the left corner
• Select Access point and server from wireless devices
• Select laptop-> physical-> OFF laptop-> remove LAN Module & replace WPC 300N
Wireless module -> ON Laptop
• Observe the wireless connections between access point and laptops
• Give IP address of the PCs as per table, ping between PCs and observe the transfer of
data packets in real and simulation mode.

WLAN OUTPUT WINDOW:(PINGING FROM laptop 1- laptop 0)

C:\>ping 169.254.129.204

Pinging 169.254.129.204 with 32 bytes of data:

Reply from 169.254.129.204: bytes=32 time=30ms TTL=128
Reply from 169.254.129.204: bytes=32 time=16ms TTL=128
Reply from 169.254.129.204: bytes=32 time=15ms TTL=128
Reply from 169.254.129.204: bytes=32 time=13ms TTL=128
Ping statistics for 169.254.129.204:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 30ms, Average = 18ms

Result:
Thus, constructed a WLAN and made the Laptops communicate wirelessly.
 EXPERMENT 12

Aim: To understand the operation of SSH by accessing the routers remotely by

PCs

Requirements
• Windows pc – 2 Nos
• CISCO Packet Tracer Software ( Student Version)
• 8 port switch – 1 No
• Router – 1 Nos
• Cat-5 LAN cable

Theory:
Procedure
• Open the CISCO Packet tracer software
• Drag and drop 1 pc and 1 laptop using End Device Icons on the left corner.
• Select 8 port switch from switch icon list in the left bottom corner
• Select Routers and Give the IP address for serial ports of router
• Type CLI‘s for the router
• Make and verify the SSH operation by pinging in the command prompt of PC
• Ping between PCs and observe the transfer of data packets in real and simulation mode

Router 0 PC0 PC1

IP Address : 192.168.1.1 IP Address : 192.168.1.2 IP Address : 192.168.1.3
Gate way : - Gate way : 192.168.1.1 Gate way : 192.168.1.1
Input Details for SSH

ROUTER CLI:

Router#config
Configuring from terminal, memory, or network [terminal]?
Enter configuration commands, one per line. End with
CNTL/Z. Router(config)#line vty 0 4
Router(config-line)#password sai123
Router(config-line)#login
local Router(config-line)#exit
Router(config)#username saimukhesh privilege 4 password sai123
Router(config)#hostname r1
r1(config)#ip domain-name cisco
r1(config)#line vty 0 4
r1(config-line)#transport input
ssh r1(config-line)#exit
r1(config)#crypto key generate
rsa
The name for the keys will be: r1.cisco
Choose the size of the key modulus in the range of 360 to 2048 for your
General Purpose Keys. Choosing a key modulus greater than 512 may
take a few minutes.
How many bits in the modulus [512]: 1024
% Generating 1024 bit RSA keys, keys will be non-exportable...[OK]

0r1(config)#
*Mar 1 0:3:53.842: %SSH-5-ENABLED: SSH 1.99 has been enabled
r1(config)#

OUTPUT:
PINGING FROM PC1 TO SERVER USING SSH:
Packet Tracer PC Command Line 1.0 C:\>ping
192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time<1ms TTL=255
Reply from 192.168.1.1: bytes=32 time<1ms TTL=255
Reply from 192.168.1.1: bytes=32 time<1ms TTL=255
Reply from 192.168.1.1: bytes=32 time<1ms TTL=255

Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: Minimum =
0ms, Maximum = 0ms, Average = 0ms

C:\>ssh -l saimukhesh 192.168.1.1

Open
Password: <sai123>
r1#
(now router can be accessed from pc1)

Result: Thus, verified the operation of SSH and accessed the router from a remote Pcs.