0% found this document useful (0 votes)
5 views9 pages

Lab File

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
5 views9 pages

Lab File

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

List of Experiments.

S.No. Program Name

1 To study the Comparative Analysis of Network Simulators

Configure and implement a network using Packet Tracer.


2
a. Creating a First Network
b. Sending Simple Text Messages in Real time Mode
c. Establishing a Web Server Connection Using the PC’s Web Browser
LAB EXPERIMENT 1

OBJECTIVE: To study the Comparative Analysis of Network Simulators

BRIEF DESCRIPTION:

CISCO PACKET TRACER:-

1. The robust simulation tool used to visualize networks.


2. Packet Tracer provides valuable tips and best practices for using Cisco Packet Tracer.
3. Learn the basic operations of Packet Tracer: - File commands, visualization and configuration of
networking devices.
4. Simulate the interactions of data traveling through the network.
5. Learn to visualize the network in logical and physical modes.
6. Reinforce your understanding with extensive hands-on networking and IOT activities.
7. Get immediate feedback on your work through built-in quizzes and tests.
8. Connect with the global Cisco Networking Academy community.

System requirement
The following configuration is recommended by Cisco to successfully install and run Packet
Tracer 7.0:
1. Microsoft Windows (7 / 8.1 / 10) or Linux Ubuntu (14.04 64-bits)
2. At least Pentium 4 (2.5 GHz)
3. A minimum of 2GB RAM (4GB recommended)
4. 700 MB of storage space
5. A minimum screen resolution of 1024 x 768.

Summary
Packet Tracer is a cross-platform visual simulation tool designed by Cisco Systems that allows users to
create network topologies and imitate modern computer networks. The software allows users to simulate
the configuration of Cisco routers and switches using a simulated command line interface.
Packet Tracer is a cross-platform visual simulation tool designed by Cisco Systems that allows users to
create network topologies and imitate modern computer networks. The software allows users to simulate
the configuration of Cisco routers and switches using a simulated command line interface. Packet Tracer
makes use of a drag and drop user interface, allowing users to add and remove simulated network devices
as they see fit. The software is mainly focused towards Certified Cisco Network Associate Academy
students as an educational tool for helping them learn fundamental CCNA concepts.
NETWORK SIMULATOR-2(NS-2) and NETWORK SIMULATOR-3(NS-3):-

1. NS (from network simulator) is a name for a series of discrete event network simulators, specifically ns-
1, and ns-2.
2. All of them are discrete-event computer network simulators, primarily used in research and teaching.

System Requirements

1. Linux (x86 and x86_64): gcc/g++ versions 4.9 and above


2. Note: If you are using RHEL or Centos, you will likely need to install a more up-to-date compiler than
the default; search for how to enable 'software collections' or 'devtoolset' on these distributions. Other Linux
distributions typically have a suitable default compiler (at least version 4.9).
3. Mac OS Apple LLVM: version 8.0.0 and above (version 7.0.0 may work)
4. FreeBSD and Linux (x86_64): clang/LLVM version 3.9 and above (older versions down to 3.3 may
work)
5. The minimum Python version supported is 2.7 or greater (version 2), or version 3.4 or greater (version
3).
Summary
NETWORK SIMULATOR 3
ns-3 has been developed to provide an open, extensible network simulation platform, for networking
research and education.
In brief, ns-3 provides models of how packet data networks work and perform, and provides a simulation
engine for users to conduct simulation experiments.
Some of the reasons to use ns-3 include to perform studies that are more difficult or not possible to perform
with real systems, to study system behavior in a highly controlled, reproducible environment, and to learn
about how networks work.

NETWORK SIMULATOR 2
It is not possible to run a simulation in ns-2 purely from C++ (i.e., as a main () program without any OTcl).
Moreover, some components of ns-2 are written in C++ and others in OTcl.
In ns-3, the simulator is written entirely in C++, with optional Python bindings. Simulation scripts can
therefore be written in C++ or in Python.
New animators and visualizers are available and under current development. Since ns-
3 generate pcap packet trace files, other utilities can be used to analyze traces as well.
WIRESHARK:-

1. Wireshark is a network packet analyzer. A network packet analyzer will try to capture network packets
and tries to display that packet data as detailed as possible.
2. You could think of a network packet analyzer as a measuring device used to examine what’s going on
inside a network cable, just like a voltmeter is used by an electrician to examine what’s going on inside an
electric cable (but at a higher level, of course).
3. Wireshark is perhaps one of the best open source packet analyzers available today.

System Requirements
The amount of resources Wireshark needs depends on your environment and on the size of the capture file
you are analyzing. The values below should be fine for small to medium-sized capture files no more than a
few hundred MB. Larger capture files will require more memory and disk space. If Wireshark runs out of
memory it will crash.
1. Microsoft Windows
2. Unix/Linux

Summary
In late 1997 Gerald Combs needed a tool for tracking down network problems and wanted to learn more
about networking so he started writing Ethereal (the original name of the Wireshark project) as a way to
solve both problems.
In October, 1998 Guy Harris was looking for something better than TCP view so he started applying patches
and contributing dissectors to Ethereal.

The list of people who have contributed to the project has become very long since then, and almost all of
them started with a protocol that they needed that Wireshark or did not already handle. So they copied an
existing dissector and contributed the code back to the team.
In 2006 the project moved house and re-emerged under a new name: Wireshark.
In 2008, after ten years of development, Wireshark finally arrived at version 1.0. This release was the first
deemed complete, with the minimum features implemented. Its release coincided with the first Wireshark
Developer and User Conference, called Sharkfest.
In 2015 Wireshark 2.0 was released, which featured a new user interface.

OmNet++

1. OMNeT++ is an extensible, modular, component-based C++ simulation library and framework,


primarily for building network simulators.
2. "Network" is meant in a broader sense that includes wired and wireless communication networks, on-
chip networks, queueing networks, and so on.
3. Domain-specific functionality such as support for sensor networks, wireless ad-hoc networks, Internet
protocols, performance modeling, photonic networks, etc., is provided by model frameworks, developed as
independent projects. OMNeT++ offers an Eclipse- based IDE, a graphical runtime environment, and a host
of other tools.
4. There are extensions for real-time simulation, network emulation, database integration, SystemC
integration, and several other functions.
5. Although OMNeT++ is not a network simulator itself, it has gained widespread popularity as a network
simulation platform in the scientific community as well as in industrial settings, and building up a large
user community.
System Requirements

1. Simulation kernel library


2. NED topology description language
3. GUI for simulation execution, links into simulation executable (Tkenv)
4. Command-line user interface for simulation execution (Cmdenv)
5. Utilities (make file creation tool, etc.)
6. Documentation, sample simulations, etc.
7. OMNeT++ IDE based on the Eclipse platform
Summary
OverSim is an OMNeT++-based open-source simulation framework for overlay and peer-to-peer networks,
developed at the Institute of Telematics, Karlsruhe Institute of Technology, Germany.
The simulator contains several models for structured (e.g. Chord, Kademlia, Pastry) and unstructured (e.g.
GIA) peer-to-peer protocols. An example implementation of the framework is an implementation of a peer-
to-peer SIP communications network.

Research tool- OverSim provides a convenient platform for simulating large-scale complex overlay
protocols and applications. Though it can be overwhelming at first, you will realize its power when you
develop a better understanding of the tool.
LAB EXPERIMENT 2

OBJECTIVE: Configure and implement a network using Packet Tracer.


a. Creating a First Network
b. Sending Simple Text Messages in Real-time Mode
c. Establishing a Web Server Connection Using the PC’s Web Browser

BRIEF DESCRIPTION: The client–server model is a distributed application structure in computing that
partitions tasks or workloads between the providers of a resource or service, called servers, and service
requesters, called clients. Often clients and servers communicate over a computer network on separate
hardware, but both client and server may reside in the same system. A server is a host that is running one
or more server programs which share their resources with clients. A client does not share any of its
resources, but requests a server's content or service function. Clients therefore initiate communication
sessions with servers which await incoming requests.

STEPS FOR HANDLING NETWORK:


PROGRAM NO – (a)
1. Start creating a network by first selecting the End Devices. Add a Generic PC and a Generic Server to
the workspace.
2. Under Connections, select the Copper Straight-through cable (solid black line) and connect the devices
with it. The red lights on the link indicate that the connection is not working. Now, use the Delete tool to
remove the Copper Straight-through cable, and use a Copper Cross-over cable (dashed line) instead. The
lights should turn green at this point. If the mouse pointer is held over either devices, the link status will be
shown as “Up.” The network should look similar to this:

Click on the PC. While paying attention to the link lights, turn the power on, off, and on again. Follow the
same steps for the server. The link lights turn red when the device is off. This means that the link is down
or is not working. The link lights turn green when the device is turned back on.
4. Try all three ways to learn about the devices. First, mouse over the devices to see basic configuration
information about them. Second, click on each device with the Select tool to show the device configuration
window, which provides several ways to configure the device. Third, use the Inspect tool to view the tables
the network device will build as it learns about the network around it. In this example, open the ARP table.
Since the devices have not been configured yet, the ARP tables are empty. Always remember to close the
windows after viewing them or they will clutter the workspace.
5. Open the PC configuration window and change the settings using the Config tab. Change the display
name to Client and set the DNS server to 192.168.0.105. Under Interface, click FastEthernet and set the IP
address as 192.168.0.110. Packet Tracer automatically calculates other parameters. Make sure that the Port
Status box is checked. For future reference, note that other Ethernet interface settings, such as bandwidth,
duplex, MAC address, and subnet mask can be modified using this window.
6. Go to the Desktop Tab and click on IP Configuration. Notice that the IP address, subnet mask and DNS
server can be changed here as well.
7. Open the Server configuration window and go to the Config tab. Change the display name to Web Server.
Click FastEthernet and set the IP address as 192.168.0.105. Make sure that the Port Status is also on. Click
DNS and set the domain name as www.firstlab.com. Set the IP address as 192.168.0.105 and click Add.
Finally, check to make sure that the service for DNS is on.

8. Reposition the network devices by dragging them to a new location. Add a network description by using
the “i” button on the upper right corner. Then add some text labels within the Logical Workspace by using
the Place Note tool.
9. Load a background grid using the Set Tiled Background button.
10. Save your work using the File > Save As option and create a meaningful filename.
PROGRAM NO – (b)
Aim: Sending Simple Text Messages in Real-time Mode
Objective: This program illustrate the use of Real-time Mode of sending simple text message
Procedure:
1. Start by opening the file saved in the last section.
2. Notice that the file opens in Real-time Mode. Use the Add Simple PDU tool to send a simple one-time
ping message, called an echo request, to the server. The server responds with an echo reply because all
devices have properly configured IP address settings.
3. Scroll up and down the User Created Packet Window to see the different capabilities of this ping message,
including an indication that the ping was successful.
4. Toggle the PDU List Window to see a larger display of this message. One or more of these messages can
be saved as a scenario. Scenario 0 is displayed when starting. Label this first scenario with an “i” note.
Different scenarios allow the use of the same topology for experiments with different groupings of user
created packets.
5. Click New to create a new scenario. New scenarios will initially be blank.
6. Add two packets using the Simple PDU tool, a PDU from the PC to the Server and a different PDU from
the Server to the PC. Then add an “i” note describing the scenario, to complete Scenario 1. An example is
shown below:
Several scenarios can be saved with a single network. Alternate between Scenario 0 and 1.
8. Now, remove Scenario 0 using the Delete button.
9. Scenario 1 is now visible. Go to the last column in the User Created Packet Window and double-click
(delete) to remove a PDU.
10. Delete the whole scenario. Notice that the scenario list went back to the default Scenario 0.
PROGRAM NO – (c)
Aim: Establishing a Web Server Connection Using the PC’s Web Browser
Objective: To study the concept of receiving a web page from server, requested by a client.
Conceptual Background:
The primary function of a web server is to deliver web pages on the request of clients using the Hypertext
Transfer Protocol (HTTP). This means delivery of HTML documents and any additional content that may
be included by a document, such as images, style sheets and scripts.
A user agent, commonly a web browser or web crawler, initiates communication by making a request for a
specific resource using HTTP and the server responds with the content of that resource or an error message
if unable to do so. The resource is typically a real file on the server's secondary storage, but this is not
necessarily the case and depends on how the web server is implemented.
While the primary function is to serve content, a full implementation of HTTP also includes ways of
receiving content from clients. This feature is used for submitting web forms, including uploading of files.
Procedure:
1. Open the file saved from the previous section.

Click on the PC to view the configuration window.


3. Select the Desktop tab, and then click Web Browser. Type in www.firstlab.com as the URL and click
the Go button. The Packet Tracer welcome page, shown below, appears, indicating that the web connection
has been successfully established.
4. Clear the URL, type www and click Go. Since the address entered is not complete, a “Host Name
Unresolved” message appears.
5. Type 192.168.0.105 as the URL entry and click on Go. Notice that the Packet Tracer welcome page
appears again. This is because the Server IP address can also be used to establish a web connection.
6. Close the window and try the same steps in Simulation Mode. In this mode, the user controls time, so the
network can be viewed running at a slower pace, allowing observation of the paths packets take and
inspection of packets in detail.
7. Select the PC again and go to the Web Browser in the Desktop tab. Type www.firstlab.com as the URL
again and click Go. The welcome page should not appear right away.
8. Switch to the main interface of Packet Tracer without closing the PC configuration window. Notice that
a DNS packet is added to the event list.
9. Click Auto Capture/Play or repeatedly click the Capture/Forward button until the HTTP packet appears
on the PC. Go back to the PC configuration window. The Packet Tracer welcome page is now shown.
10. Close the PC configuration window.

You might also like