EXPERIMENT-10

PACKET SNIFFING AND WIRESHARK

Wireshark

i. Packet Capture Using Wire shark

ii. Starting Wire shark
iii. Viewing Captured Traffic
iv. Analysis and Statistics & Filters

Introduction
Wireshark is a free open- source network protocol analyzer. It is used for network troubleshooting and
communication protocol analysis. Wireshark captures network packets in real time and display them in human-
readable format. It provides many advanced features including live capture and offline analysis, three-pane
packet browser, coloring rules for analysis. This document uses Wireshark for the experiments, and it covers
Wireshark installation, packet capturing, and protocol analysis.

Background

TCP/IP Network Stack

Figure 2: Encapsulation of Data in the TCP/IP Network Stack

- Application Layer: The application layer includes the protocols used by most applications for providing user
services. Examples of application layer protocols are Hypertext Transfer Protocol (HTTP), Secure Shell (SSH),
File Transfer Protocol (FTP), and Simple Mail Transfer Protocol (SMTP).
- Transport Layer: The transport layer establishes process-to-process connectivity, and it provides end-to-end
services that are independent of underlying user data. To implement the process-to-process communication, the
protocol introduces a concept of port. The examples of transport layer protocols are Transport Control Protocol
 (TCP) and User Datagram Protocol (UDP). The TCP provides flow- control, connection establishment, and
reliable transmission of data, while the UDP is a connectionless transmission model.
- Internet Layer: The Internet layer is responsible for sending packets to across networks. It has two functions: 1)
Host identification by using IP addressing system (IPv4 and IPv6); and 2) packets routing from source to
destination. The examples of Internet layer protocols are Internet Protocol (IP), Internet Control Message
Protocol (ICMP), and Address Resolution Protocol (ARP).
- Link Layer: The link layer defines the networking methods within the scope of the local network link. It is used
to move the packets between two hosts on the same link.A common example of link layer protocols is Ethernet.

Packet Sniffer

Packet sniffer is a basic tool for observing network packet exchanges in a computer. As the name suggests, a
packet sniffer captures (“sniffs”) packets being sent/received from/by your computer; it will also typically store
and/or display the contents of the various protocol fields in these captured packets. A packet sniffer itself is
passive. It observes messages being sent and received by applications and protocols running on your computer,
but never sends packets itself.
Figure shows the structure of a packet sniffer. At the right of Figure are the protocols (in this case,
Internet protocols) and applications (such as a web browser or ftp client) that normally run on your computer.
The packet sniffer, shown within the dashed rectangle in Figure is an addition to the usual software in your
computer, and consists of two parts. The packet capture library receives a copy of every link-layer frame that is
sent from or received by your computer. Messages exchanged by higher layer protocols such as HTTP, FTP,
TCP, UDP, DNS, or IP all are eventually encapsulated in link-layer frames that are transmitted over physical
media such as an Ethernet cable. In Figure 1, the assumed physical media is an Ethernet, and so all upper-layer
protocols are eventually encapsulated within an Ethernet frame. Capturing all link-layer frames thus gives you
access to all messages sent/received from/by all protocols and applications executing in your computer.
The second component of a packet sniffer is the packet analyzer, which displays the contents of all fields
within a protocol message. In order to do so, the packet analyzer must “understand” the structure of all
messages exchanged by protocols. For example, suppose we are interested in displaying the various fields in
messages exchanged by the HTTP protocol in Figure. The packet analyzer understands the format of Ethernet
frames, and so can identify the IP datagram within an Ethernet frame. It also understands the IP datagram
format, so that it can extract the TCP segment within the IP datagram. Finally, it understands the TCP segment
structure, so it can extract the HTTP message contained in the TCP segment. Finally, it understands the HTTP
protocol and so, for example, knows that the first bytes of an HTTP message will contain the string “GET,”
“POST,” or “HEAD”.
 Figure: Packet Sniffer Structure

We will be using the Wireshark packet sniffer [http://www.wireshark.org/] for these labs, allowing us to
display the contents of messages being sent/received from/by protocols at different levels of the protocol stack.
(Technically speaking, Wireshark is a packet analyzer that uses a packet capture library in your computer).
Wireshark is a free network protocol analyzer that runs on Windows, Linux/Unix, and Mac computers.

Getting Wireshark
Wireshark can be downloaded from here:
https://www.wireshark.org/download.html

Figure 4: Download Page of Wireshark

Starting Wireshark

When you run the Wireshark program, the Wireshark graphic user interface will be shown as Figure 5.
Currently, the program is not capturing the packets.
 Figure 5: Initial Graphic User Interface of Wireshark
Then, you need to choose an interface. If you are running the Wireshark on your laptop, you need to select WiFi
interface. If you are at a desktop, you need to select the Ethernet interface being used. Note that there could be
multiple interfaces. In general, you can select any interface but that does not mean that traffic will flow through
that interface. The network interfaces (i.e., the physical connections) that your computer has to the network are
shown. The attached Figure 6 was taken from my computer.
After you select the interface, you can click start to capture the packets as shown in Figure 7.

Figure 6: Capture Interfaces in Wireshark

 Figure 7: Capturing Packets in Wireshark

Figure 8: Wireshark Graphical User Interface on Microsoft Windows

The Wireshark interface has five major components:

The command menus are standard pulldown menus located at the top of the window. Of interest to us
now is the File and Capture menus. The File menu allows you to save captured packet data or open a file
containing previously captured packet data, and exit the Wireshark application. The Capture menu allows you
to begin packet capture.
 The packet-listing window displays a one-line summary for each packet captured, including the packet
number (assigned by Wireshark; this is not a packet number contained in any protocol’s header), the time at
which the packet was captured, the packet’s source and destination addresses, the protocol type, and protocol-
specific information contained in the packet. The packet listing can be sorted according to any of these
categories by clicking on a column name. The protocol type field lists the highest- level protocol that sent or
received this packet, i.e., the protocol that is the source or ultimate sink for this packet.
The packet-header details window provides details about the packet selected (highlighted) in the
packet-listing window. (To select a packet in the packet-listing window, place the cursor over the packet’s one-
line summary in the packet-listing window and click with the left mouse button.). These details include
information about the Ethernet frame and IP datagram that contains this packet. The amount of Ethernet and IP-
layer detail displayed can be expanded or minimized by clicking on the right- pointing or down-pointing
arrowhead to the left of the Ethernet frame or IP datagram line in the packet details window. If the packet has
been carried over TCP or UDP, TCP or UDP details will also be displayed, which can similarly be expanded or
minimized. Finally, details about the highest-level protocol that sent or received this packet are also provided.
The packet-contents window displays the entire contents of the captured frame, in both ASCII and
hexadecimal format.
Towards the top of the Wireshark graphical user interface, is the packet display filter field, into which a
protocol name or other information can be entered in order to filter the information displayed in the packet-
listing window (and hence the packet-header and packet-contents windows). In the example below, we’ll use
the packet-display filter field to have Wireshark hide (not display) packets except those that correspond to
HTTP messages.

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. For example, if you want to capture traffic on the
wireless network, click your wireless interface.

Test Run
Do the following steps:
1.Start up the Wireshark program (select an interface and press start to capture packets).
2.Start up your favorite browser (Mozilla Firefox).
3.In your browser, go to Wayne State homepage by typing www.wayne.edu.
4.After your browser has displayed the http://www.wayne.edu page, stop Wireshark packet capture by
selecting stop in the Wireshark capture window. This will cause the Wireshark capture window to disappear
and the main Wireshark window to display all packets captured since you began packet capture see image
below:
5.Color Coding: You’ll probably see packets highlighted in green, blue, and black. Wireshark uses colors to
help you identify the types of traffic at a glance. By default, green is TCP traffic, dark blue is DNS traffic,
light blue is UDP traffic, and black identifies TCP packets with problems — for example, they could have
been delivered out-of-order.
6.You now have live packet data that contains all protocol messages exchanged between your computer and
other network entities! However, as you will notice the HTTP messages are not clearly shown because there
are many other packets included in the packet capture. Even though the only action you took was to open

your browser, there are many other programs in your computer that communicate via the network in the
background. To filter the connections to the ones we want to focus on, we have to use the filtering
functionality of Wireshark by typing “http” in the filtering field as shown below:
 Notice that we now view only the packets that are of protocol HTTP. However, we also still do not have the
exact communication we want to focus on because using HTTP as a filter is not descriptive enough to allow us
to find our connection to http://www.wayne.edu. We need to be more precise if we want to capture the correct
set of packets.
7. To further filter packets in Wireshark, we need to use a more precise filter. By setting the
http.host==www.wayne.edu, we are restricting the view to packets that have as an http host the
www.wayne.edu website. Notice that we need two equal signs to perform the match “==” not just one. See the

screenshot below:
1. Now, we can try another protocol. Let’s use Domain Name System (DNS) protocol as an example here.
2. Let’s try now to find out what are those packets contain by following one of the conversations (also called
network flows), select one of the packets and press the right mouse button (if you are on a Mac use the
command button and click), you should see something similar to the screen below:

Click on Follow UDP Stream, and then you will see following screen.
3. If we close this window and change the filter back to “http.host==www.wayne.edu” and then follow a

packet from the list of packets that match that filter, we should get the something similar to the following
screens. Note that we click on Follow TCP Stream this time.

EXPERIMENT-11
How to run Nmap scan
HOW TO RUN A SIMPLE NMAP SCAN
1. Download the Nmap installer. This can be found for free from the developer’s website. It is highly
recommended that you download directly from the developer to avoid any potential viruses or fake files.
Downloading the Nmap installer includes Zenmap, the graphical interface for Nmap which makes it easy for
newcomers to perform scans without having to learn command lines.
 The Zenmap program is available for Windows, Linux, and Mac OS X. You can find the installation files
for all operating systems on the Nmap website.
2. Install Nmap. Run the installer once it is finished downloading. You will be asked which components you
would like to install. In order to get the full benefit of Nmap, keep all of these checked. Nmap will not install
any adware or spyware.
3. Run the “Nmap – Zenmap” GUI program. If you left your settings at default during installation, you
should be able to see an icon for it on your desktop. If not, look in your Start menu. Opening Zenmap will start
the program.
4. Enter in the target for your scan. The Zenmap program makes scanning a fairly simple process. The first
step to running a scan is choosing your target. You can enter a domain (example.com), an IP address
(127.0.0.1), a network (192.168.1.0/24), or a combination of those.
 Depending on the intensity and target of your scan, running an Nmap scan may be against the terms of your
internet service provider, and may land you in hot water. Always check your local laws and your ISP
contract before performing Nmap scans on targets other than your own network.
5. Choose your Profile. Profiles are preset groupings of modifiers that change what is scanned. The profiles
allow you to quickly select different types of scans without having to type in the modifiers on the command
line. Choose the profile that best fits your needs:
 Intense scan - A comprehensive scan. Contains Operating System (OS) detection, version detection, script
scanning, traceroute, and has aggressive scan timing. This is considered an intrusive scan.
 Ping scan - This scan simply detects if the targets are online, it does not scan any ports.
 Quick scan - This is quicker than a regular scan due to aggressive timing and only scanning select ports.
 Regular scan - This is the standard Nmap scan without any modifiers. It will return ping and return open
ports on the target.
6. Click Scan to start scanning. The active results of the scan will be displayed in the Nmap Output tab. The
time the scan takes will depend on the scan profile you chose, the physical distance to the target, and the target’s
network configuration.
7. Read your results. Once the scan is finished, you’ll see the message “Nmap done” at the bottom of the
Nmap Output tab. You can now check your results, depending on the type of scan you performed. All of the
results will be listed in the main Nmap Output tab, but you can use the other tabs to get a better look at specific
data.
 Ports/Hosts - This tab will show the results of your port scan, including the services for those ports.
 Topology - This shows the traceroute for the scan you performed. You can see how many hops your data
goes through to reach the target.
 Host Details - This shows a summary of your target learned through scans, such as the number of ports, IP
addresses, hostnames, operating systems, and more.
 Scans - This tab stores the commands of your previously-run scans. This allows you to quickly re-scan
with a specific set of parameters.
 EXPERIEMENT: 12
Operating System Detection using Nmap
OPERATING SYSTEM DETECTION USING NMAP

Syntax: nmap –O IPADDRESS

Ex: nmap –O 192.168.0.86

 EXPERIMENT NO: 13
NAME OF THE EXPERIMENT: NS2 Simulator
 AIM: Do the following using NS2 Simulator
i. NS2 Simulator-Introduction
ii. Simulate to Find the Number of Packets Dropped
iii. Simulate to Find the Number of Packets Dropped by TCP/UDP
iv. Simulate to Find the Number of Packets Dropped due to Congestion
v. Simulate to Compare Data Rate& Throughput.
vi. Simulate to Plot Congestion for Different Source/Destination
vii. Simulate to Determine the Performance with respect to Transmission of Packets

Description:

NS2 Simulator-Introduction
1. NS2 stands for Network Simulator Version
2. It is an open-source event-driven simulator designedspecifically for research in computer
communication networks.

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. Uses TCL as its scripting language.

Network simulation is an important tool in developing, testing and evaluating network protocols.
Simulation can be used without the target physical hardware, making it economical and practical for
almost any scale of network topology and setup.

GETTING STARTED
Setting up the environment
A user using the NCTUns in single machine mode, needs to do the following steps before
he/she starts the GUI program:
1. Set up environment variables:
Before the user can run up the dispatcher, coordinator, or NCTUns GUI programhe/she must set up
the NCTUNSHOME environment variable.
2. Start up the dispatcher on terminal 1.
3. Start up the coordinator on terminal 2.
4. Start up the nctunsclient on terminal 3.
After the above steps are followed, the starting screen of NCTUns disappears and the user is
presented with the working window as shown below:
 i) Simulate a three node point to point network with a duplex link between them. Set the queue
size and vary the bandwidth and find the number of packets dropped.

Step1: Drawing topology

1. Select/click the HOST icon onthe toolbar and click the left mouse button on the editor,to place a
HOST1 on the editor.
Repeat the above procedure and place another host “HOST2” on the editor.
2. Select/click the HUB icon on the toolbar and click the left mouse button on the editor,to place HUB1
on the editor.
3. Click on the LINK icon on the toolbar and connect HOST1 to HUB1 and HUB1 to HOST2
4. Click on the “E” icon on the toolbar to save the current topology
e.g: file1.tpl
(Look for the ******.tpl extension.)
NOTE: Changes cannot / (should not) be done after selecting the “E” icon.

Step2: Configuration
1. Double click the left mouse button while cursor is on HOST1 to open the HOST window.
2. Select Add button on the HOST window to invoke the command window and provide the following
command in the command textbox.
stg –u 1024 100 1.0.1.2
3. Click OK button on the command window to exit and once again click on the OK button on the
HOST window to exit.
4. Double click the left mouse button while cursor is on HOST2 to open the HOST window.
 5. Select Add button on the HOST window to invoke the command window and provide the following
command in the command textbox.
rtg –u –w log1
6. Click OK button on the command window toexit.
7. Click NODE EDITOR Button on the HOST window and select the MAC tab fromthe modal window
that pops up.
8. Select LOG STATISTICS and select checkboxes for Number of Drop Packetand Number of
Collisions in the MAC window
9. Click OK button on the MAC window to exit and once again click on the OK buttonon the HOST
window to exit.
Note: To set QUEUEsize
1. Double click the left mouse button while cursor is on HOST2 to open the HOST window.
2. Click NODE EDITOR Button on the HOST window and select the FIFO tab from the modal
window that pops up.
3. Change Queue size (Default 50).
4. Click OK button on the FIFO window to exit and once again click on the OK buttonon the HOST
window to exit.
5.
Step3: Simulate
i. Click “R” icon on the tool bar
ii. Select Simulation in the menu bar and click/ select RUN in the dropdownlist to execute the
simulation.
iii. venTo start playback select “►” icon located at the bottom right corner ofthe editor.
iv. To view results, Open up new TERMINAL window, move to file1.results folder and open collision
and drop log files in separate TERMINAL window.
v.
Changing configurationsChange1
1. Open the above file,
2. Do not change the topology or any other configuration,
3. Select E icon on thetoolbar
4. Reduce the bandwidth at link2 by double clicking the left mouse button while cursor ison link2
.(Change bandwidth on both tabs Uplink/Downlink)
5. Repeat Step3 (Simulate)
Change 2
1. Open the above file.
2. Remove HUB and replace it with SWITCH.
3. Do not change anything in theconfiguration
4. Repeat Step3(Simulate)

ii) Simulate a four node point to point network and connect the link as follows Apply a
TCP agent between n0 to n3 and apply a UDP agent between n1 and n3.Apply relevant
applications over TCP and UDP agents changing the parameters and determine the number of
packets sent by two agents.
 Step1: Drawing topology
1. Select/click the HOST icon on the toolbar and click the left mouse button on the editor,to place a
host on the editor.
Repeat the above procedure and place two other hosts “HOST2” and“HOST3” on the editor.
2. Select/click the HUB (or SWITCH) icon on the toolbar and click the left mouse button on the editor,
to place a HUB (or SWITCH) on theeditor.
3. Click on the LINK icon on the toolbar and connect HOST1 to HUB, HOST2 to HUB andHUB to
HOST3
4. Click on the “E” icon on the toolbar to save the current topology e.g: file2.tpl (Look for the
******.tpl extension.)
NOTE: Changes cannot / (should not) be done after selecting the “E” icon.

Step2: Configuration
1. Double click the left mouse button while cursor is on HOST1 to open the HOST window.
2. Change simulation time from 0 to 20 for HOST1
3. Select Add button on the HOST1 window to invoke the command window and provide the following
command in the command textbox.
ttcp –t –u –s –p 8000 1.0.1.3
4. Click OK button onthe command window to exit
5. Click NODE EDITOR Button on the HOST window and select the MAC tab from the modal
window that pops up.
6. Select LOG STATISTICS and select checkbox for output throughput in the MAC window
7. Click OK button on the MAC window to exit and once again click on the OK button on
the HOST window to exit.
8. Double click the left mouse button while cursor is on HOST2 to open the HOST window.
9. Change simulation time from 21 to 40 for HOST2
10. Select Add button on the HOST2 window to invoke the command window and provide the following
command in the command textbox.

stg –u 1024 100 1.0.1.3

11. Click OK button on the command window to exit
12. Click NODE EDITOR Button on the HOST window and select the MAC tab from themodal window
that pops up.
13. Select LOG STATISTICS and select checkbox for output throughput in the MAC window
 14. Click OK button on the MAC window to exit and once again click on the OK button on the HOST
window to exit.
15. Double click the left mouse button while cursor is on HOST3 to open the HOSTwindow.
16. Change simulation time from 0 to 20 for HOST3
17. Select Add button on the HOST window to invoke the command window and provide the following
command in the command textbox.
ttcp –r –u –s –p 8000
18. Click OK button on the command window to exit.
19. Change simulation time from21 to 40 for HOST3
20. Also add the following command on HOST3 rtg –u–
w log1
21. Click NODE EDITOR Button on the HOST window and select the MAC tab from themodal window
that pops up.
22. Select LOG STATISTICS and select checkbox for input and outputthroughput in the MAC window
23. Click OK button on the MAC window to exit and once again click on the OK button on the HOST
window to exit.

Step3: Simulate
i. Click “R” icon on the tool bar
ii. Select Simulation in the menu bar and click/ select RUN in the dropdownlist to execute the
simulation.
iii. To start playback select “►” icon located at the bottom right corner of theeditor.
iv. To view results, Open up new TERMINAL window, move to file2.results folder and open input and
output throughput log files in separate TERMINAL window.

iii) Simulate the transmission of ping messages over a network topology consisting of 6
nodes and find the number of packets dropped due to congestion.

Step1: Drawing topology

1. Select/click the SUBNET icon on the toolbar and click the left mouse button on the editor, to place a
SUBNET on the editor.
2. A pop up window appears requesting the number of nodes and radius for the subnet
Set number of nodes=6; Set radius of subnet >150

3. Click on the “E” icon on the toolbar to save the current topology e.g: file4.tpl (Look for the
 ******.tpl extension.)
NOTE: Changes cannot / (should not) be done after selecting the “E” icon.

Step2: Configuration
1. Make 5 HOST as sender and make 1 HOST as receiver and give the commands with particular port
number
2. Sender Commands
Sender 1 : stcp –p 21 –l 1024 1.0.1.1
Sender 2 : stcp –p 22 –l 1024 1.0.1.1
Sender 3 : stcp –p 23 –l 1024 1.0.1.1
Sender 4 : stcp –p 24 –l 1024 1.0.1.1
Sender 5 : stcp –p 25 –l 1024 1.0.1.1
Receiver Commands
rtcp –p 21 –l 1024
rtcp –p 22 –l 1024
rtcp –p 23 –l 1024
rtcp –p 24 –l 1024
rtcp –p 25 –l 1024
3. For each sender HOST select the Out through put, Collision and Droppackets.
4. For receiver HOST select the In throught put, Collision and Drop packets.
5.
Step3: Simulate
i. Click “R” icon on the tool bar
ii. Select Simulation in the menu bar and click/ select RUN in the dropdown list to execute the
simulation.
iii. During simulation, double click the mouse button on any sender HOST, the HOST window pops
up, select / click on command console button located atthe bottom.
iv. A terminal window appears, type ping IP address of a receiver HOST in the subnet atthe command
prompt.
v. To view results, Open up new TERMINAL window, move to file4.results folder andopen drop and
collision log files in separate TERMINAL window.
vi.
iv) Simulate an ETHERNET LAN using n nodes (6-10), change error rate and data rate
and compare throughput.
 Step1: Drawing topology
1. Select/click the HOST icon on the toolbar and click the left mouse button on the editor, to place
HOST1 on the editor.
i. Repeat the above procedure and place 5 other hosts “HOST2”, “HOST3”, “HOST4”, “HOST5”, and
“HOST6”on the editor.
2. Select/click the HUB icon on the toolbar and click the left mouse button on the editor, to place
HUB1 on the editor.
Repeat the above procedure and place another host “HUB2” on the editor
3. Click on the LINK icon on the toolbar and connect HOST1, HOST2 and HOST3 to HUB1, HOST4,
HOST5 and HOST6toHUB2.
4. Select/click the SWITCH icon on the toolbar and click the left mouse button on the editor, to place
SWITCH1 on theeditor.
5. Click on the LINK icon on the toolbar and connect HUB1 to SWITCH1 and HUB2 to SWITCH1.
6. Click on the “E” icon on the toolbar to save the currenttopology
e.g: file5.tpl
(Look for the ******.tpl extension.)

NOTE: Changes cannot / (should not) be done after selecting the “E” icon.

Step2: Configuration
1. Double click the left mouse button while cursor is on HOST1to open theHOST window.
2. Select Add button on the HOST window to invoke the command window and provide the following
command in the command textbox.
ttcp –t –u –s –p 8001 1.0.1.4 (Split time from 0 to 10)
3. Change error rate and data rate in the physical layer and selectOut throughput in MAC layer
4. Click OK button on the command window to exit and once againclick on the OK button on the
HOST window to exit.
5. Repeat this step at HOST 2 and HOST3 by changing port number& IP address of receiver. Change
error rate and data rate.
ttcp –t –u –s –p 8002 1.0.1.5 (Split time from 11 to 20)
ttcp –t –u –s –p 8003 1.0.1.6 (Split time from 21 to 30)
5. Double click the left mouse button while cursor is on HOST4to open theHOST window.
6. Select Add button on the HOST window to invoke the commandwindow and provide the following
command in the command textbox.
ttcp –r –u –s –p 8001(Split time from 0 to 10)
7. Change error rate and data rate in the physical layer and selectIN throughput in MAC layer
8. Repeat this step at HOST 5 and HOST6, but use different commands. Change error rate and data
rate.
ttcp –r –u –s –p 8002(Split time from 11 to 20)ttcp –r –u –s –p 8003(Split time from 21 to 30)

Step3: Simulate
i. Click “R” icon on the tool bar
ii. Select Simulation in the menu bar and click/ select RUN in the dropdown list to execute the
 simulation.
iii. To start playback select “►” icon located at the bottom right corner of the editor. To view results,
Open up new TERMINAL window, move to file5.results folder and open output throughput log
files in separate TERMINAL window.

V)Simulate an ETHERNET LAN using n nodes and set multiple traffic nodes and plot
congestion window for different source/destination.

Step1: Drawing topology

7. Select/click the HOST icon on the toolbar and click the left mouse button on the editor, to place
HOST1 on the editor.
i. Repeat the above procedure and place 3 other hosts “HOST2”, “HOST3”, “HOST4”, “HOST5”, and
“HOST6”on the editor.
8. Select/click the HUB icon on the toolbar and click the left mouse button on the editor, to place
HUB1 on the editor.
Repeat the above procedure and place another host “HUB2” on the editor
9. Click on the LINK icon on the toolbar and connect HOST1, HOST2 and HOST3 to HUB1, HOST4,
HOST5 and HOST6 to HUB2.
 10. Select/click the SWITCH icon on the toolbar and click the left mousebutton on the editor, to place
SWITCH1 the editor.
11. Click on the LINK icon on the toolbar and connect HUB1 to SWITCH1 and HUB2 to SWITCH1.
Click on the “E” icon on the toolbar to save the current topology e.g:
file7.tpl (Look for the ******.tpl extension.)
NOTE: Changes cannot / (should not) be done after selectingthe “E” icon.

Step2: Configuration

1. Double click the left mouse button while cursor is on HOST1 to open the HOST window.
2. Select Add button on the HOST window to invoke the command window and provide the following
command in the command textbox.
ttcp –t –u –s –p 8001 1.0.1.4
3. Click OK button on the command window to exit and once againclick on the OK button on the
HOST window to exit.
4. Repeat this step at HOST 2 and HOST3 by changing port number & IP address of receiver. Change
error rate and data rate.
ttcp –t –u –s –p 8002 1.0.1.5
ttcp –t –u –s –p 8003 1.0.1.6
5. Select Outthroughput, Collision & Drop in MAC layer for allsenders
6. Double click the left mouse button while cursor is on HOST4 to open the HOST window.
7. Select Add button on the HOST window to invoke the command window and provide the following
command in the command textbox.
ttcp –r –u –s –p 8001
8. Repeat this step at HOST 5 and HOST6, but use differentcommands. Change error rate and data rate.
ttcp –r –u –s –p 8002ttcp –r –u –s –p 8003
9. select Inthroughput, Collision & Drop in MAC layer for all receivers

Step3: Simulate
i. Click “R” icon on the toolbar
Select Simulation in the menu bar and click/ select RUN in the dropdown list to execute the
simulation.
i. To start playback select “►” icon located at the bottom right corner oftheeditor.
iv. To plot congestion window select Tools in the menu bar and select
PLOT GRAPH in the drop down list.
v. In the Graph window, select File->OPEN, move to file7.results folder and the drop and collision log
file.
vi. To open another Graph window, Select File->New tab on the drop down list to open up to a
maximum of 6 windows
vii. To view results, Open up new TERMINAL window, move to file7.results folder and open input and
output throughput log files in separate TERMINAL window.

v) Simulate simple BSS and with transmitting nodes in wireless LAN by simulation and
determine the performance with respect to transmission of packets.
 Step1: Drawing topology
1. Select/click the HOST icon on the toolbar and click the left mouse button onthe editor, to place
HOST1 on the editor.
2. Select/click the ROUTER icon on the toolbar and click the left mouse buttonon the editor, to place
ROUTER1 on the editor.
3. Select/click the WIRELESS ACCESS POINT(802.11b) icon on the toolbar and click the left mouse
button on the editor, to place ACCESS POINT 1 ontheeditor.
Repeat this procedure and place ACCESS POINT 2 on the editor.
4. Select/click the MOBILE NODE (infrastructure mode) icon on the toolbar and click the left mouse
button on the editor, to place MOBILE NODE 1 onthe editor. Repeat this procedure and place
MOBILE NODE 2, MOBILE NODE3 and MOBILE NODE 4 on the editor.
5. Click on the LINK icon on the toolbar and connect ACCESS POINT1 to ROUTER1 and ACCESS
POINT2 to ROUTER1
6. Click on the “Create a moving path” icon on the toolbar and draw movingpath across MOBILE
NODE 1 and 2, Repeat for MOBILE NODE 3and 4 (Accept the default speed value 10 and close
the window, Click the right mouse button to terminate the path).

To create Subnet
7. Select wireless subnet icon in the toolbar now select MOBILE NODE1, MOBILE NODE2 and
ACCESS POINT1 by clicking on left mouse button, and clicking right mouse button will create a
subnet.
8. Repeat the above step for MOBILE NODE3, MOBILE NODE4 and ACCESS POINT2.
9. Click on the “E” icon on the toolbar to save the current topology e.g:
file8.tpl
(Look for the ******.tpl extension.)
NOTE: Changes cannot / (should not) be done after selecting the “E” icon.

Step2: Configuration
1. Double click the left mouse button while cursor is on HOST1 to open the HOST window.
2. Select Add button on the HOST window to invoke the command window and providethe following
command in the command textbox.
ttcp –r –u –s –p 8001
 3. Click OK button onthe command window to exit
4. Repeat this step and add the following commands at HOST1ttcp –r –u –s –p 8002
ttcp –r –u –s –p 8003ttcp –r –u –s –p 8004 ttcp –r –u –s –p 8005
5. Click NODE EDITOR Button on the HOST1 window and select the MACtab from the modal
window that pops up.
6. Select LOG STATISTICS and select checkbox for Input throughput in the MAC window
7. Click OK button on the MAC window to exit and once again click on theOK button on the HOST
window to exit.
8. Double click the left mouse button while cursor is on MOBILE NODE 1 to open the MOBILE
NODE window.
9. Select Application tab and select Add button to invoke the command window and provide the
following command in the command textbox.
ttcp –t –u –s –p 8001 1.0.2.2 (host’s ip address)
10. Click NODE EDITOR Button on the MOBILE NODE1 window andselect the MAC tab
from the nodal window that pops up.
11. Select LOG STATISTICS and select checkbox for Output throughput in the MACwindow
12. Click OK button on the MAC window to exit and once again click onthe OK button onthe
MOBILE NODE1 window to exit.
13. Repeat the above steps (step 8 to step12) for the MOBILE NODE2,3 and4 and add
thefollowing commands at
MOBILE NODE2:- ttcp –t –u –s –p 8002 1.0.2.2 MOBILE NODE 3:- ttcp –t–u –s –p 8003
1.0.2.2 MOBILE NODE4:- ttcp –t –u –s –p 8004 1.0.2.2
14. Double click the left mouse button while cursor is on ROTER1 to open the ROUTER
window.
15. Click NODE EDITOR Button on the ROUTER1 window and you can see three stacks.
two stacks for two ACCESS POINTS and another stackfor HOST1 which is connected to the
ROUTER1.
16. Select the MAC tab of ACCESS POINT1 and Select LOG STATISTICS and select
checkbox for Input throughput in the MAC window. Click OK button on the MAC window to exit.
17. Select the MAC tab of ACCESS POINT2 and Select LOG STATISTICS and select
checkbox for Input throughput in the MAC window. Click OK button on the MAC window to exit.
18. Select the MAC tab of HOST1 and Select LOG STATISTICS and select checkbox
forOutput throughput in the MAC window. Click OK button onthe MAC window to exit.
19. Add the following command for router
ttcp –t –u –s –p 8005 1.0.2.2 (host’s ip address)

Step3: Simulate
I Click “R” icon on the tool bar
.
I Select Simulation in the menu bar and click/ select
I RUN in the
.
dropdown list to execute the simulation.
III. To start playback select “►” icon located at the bottom right corner of theeditor.
IV. MOBILE NODE’s start moving across the paths alreadydrawn.