User Manual

NetSim User Manual
Contents
1 NetSim – Introduction ......................................................................... 11

1.1 Introduction to modeling and simulation of networks ............................................................... 11
1.2 Versions of NetSim – Academic, Standard & Pro........................................................................ 12
1.3 Components in Pro and Standard versions................................................................................. 14
2 Getting Started in NetSim ................................................................... 16

2.1 Installing NetSim in Client ........................................................................................................... 16
2.2 Setting up License Server ............................................................................................................ 26
2.2.1 Installing NetSim RLM Dongle ....................................................................................... 26
2.2.2 Running RLM Dongle (Server) ....................................................................................... 28
2.2.3 Running NetSim Software ............................................................................................. 29
2.3 Menus in NetSim ......................................................................................................................... 30
2.3.1 Simulation Menu ........................................................................................................... 31
2.3.2 Programming Menu ...................................................................................................... 32
2.3.3 Basics ............................................................................................................................. 33
2.3.4 Help ............................................................................................................................... 33
2.4 Modeling and Simulation of a simple network ........................................................................... 34
2.4.1 Creating a Network scenario......................................................................................... 34
2.4.2 Configuring devices and links in the scenario .............................................................. 36
2.4.3 Modeling Traffic ............................................................................................................ 37
2.4.4 Logging Packet/ Event Trace ......................................................................................... 37
2.4.5 Simulation ..................................................................................................................... 38
2.5 Network – Opening, Saving scenarios and Printing results ........................................................ 39
2.5.1 Opening Saved Experiments ......................................................................................... 39
2.5.2 Saving an Experiment.................................................................................................... 40
3 Simulating different networks in NetSim ............................................ 41

3.1 Internetworks.............................................................................................................................. 41
3.1.1 New Experiment............................................................................................................ 41
3.1.2 Create Scenario ............................................................................................................. 41
3.1.3 Set Node, Link and Application Properties ................................................................... 42
1
3.1.4 Enable Packet Trace, Event Trace & Dynamic Metrics (Optional) ................................ 43
3.1.5 Run Simulation .............................................................................................................. 43
3.1.6 Sample Experiment ....................................................................................................... 43
3.1.7 IP Addressing in NetSim ................................................................................................ 43
3.1.8 SINR, BER and Propagation models for 802.11 a, b, g and n ........................................ 44
3.1.9 Features in WLAN 802.11n/ac ...................................................................................... 49
3.2 Legacy Networks ......................................................................................................................... 55
3.2.1 New Experiment............................................................................................................ 55
3.2.2 Create Scenario ............................................................................................................. 55
3.2.4 Modifying/Viewing/Accepting Properties .................................................................... 56
3.2.5 Enable Packet Trace (Optional) ..................................................................................... 56
3.2.6 Run Simulation .............................................................................................................. 56
3.3 Advanced wireless networks – MANET & Wi-Max ..................................................................... 57
3.3.1 New Experiment............................................................................................................ 57
3.3.2 Create Scenario ............................................................................................................. 57
3.3.7 Run Simulation .............................................................................................................. 59
3.3.8 Link Layer Acknowledgements and Network Layer Acknowledgements in DSR .......... 60
3.4 Advanced wireless networks – VANET........................................................................................ 62
3.4.1 New Experiment............................................................................................................ 62
3.4.2 Create Scenario ............................................................................................................. 62
3.4.5 Enable Packet Trace, Event Trace(Optional) ................................................................. 63
3.4.7 Run Simulation .............................................................................................................. 64
3.5 BGP .............................................................................................................................................. 65
3.5.1 New Experiment............................................................................................................ 65
3.5.2 Create Scenario ............................................................................................................. 65
2
3.5.6 Run Simulation .............................................................................................................. 67
3.6 Cellular Networks – GSM/CDMA ................................................................................................ 68
3.6.1 New Experiment............................................................................................................ 68
3.6.2 Create Scenario ............................................................................................................. 68
3.6.5 Run Simulation .............................................................................................................. 69
3.7 Wireless Sensor Network ............................................................................................................ 71
3.7.1 New Experiment............................................................................................................ 71
3.7.2 Create Scenario ............................................................................................................. 71
3.7.5 Run Simulation .............................................................................................................. 72
3.7.7 SINR, BER and Propagation models for 802.15.4 .......................................................... 72
3.8 Internet of Things ........................................................................................................................ 76
3.8.1 New Experiment............................................................................................................ 76
3.8.2 Introduction .................................................................................................................. 76
3.8.3 Create Scenario ............................................................................................................. 77
3.8.5 Enable Packet Trace, Event Trace & Dynamic Metrics(Optional) ................................. 79
3.8.6 Run Simulation .............................................................................................................. 79
3.9 Zigbee .......................................................................................................................................... 80
3.9.1 New Experiment............................................................................................................ 80
3.9.2 Create Scenario ............................................................................................................. 80
3.9.6 Run Simulation .............................................................................................................. 82
3
3.9.8 SINR, BER and Propagation models for 802.15.4 .......................................................... 82
3.10 Cognitive Radio ........................................................................................................................ 86
3.10.1 New Experiment............................................................................................................ 86
3.10.2 Create Scenario ............................................................................................................. 86
3.10.5 Run Simulation .............................................................................................................. 88
3.11 LTE/LTE-A .................................................................................................................................. 90
3.11.1 New Experiment............................................................................................................ 90
3.11.2 Create Scenario ............................................................................................................. 90
3.11.5 Run Simulation .............................................................................................................. 92
3.11.7 Physical speed of the LTE Air Interface ......................................................................... 92
3.12 Military Radio – TDMA link 16 .................................................................................................. 95
3.12.1 New Experiment............................................................................................................ 95
3.12.2 Create Scenario ............................................................................................................. 95
3.12.3 Set Node Properties ...................................................................................................... 95
3.12.4 Set Environment Properties .......................................................................................... 96
3.12.6 Set Application Properties ............................................................................................ 97
3.12.8 Run Simulation .............................................................................................................. 98
3.13 Military Radio – DTDMA ........................................................................................................... 99
3.13.1 New Experiment............................................................................................................ 99
3.13.2 Create Scenario ............................................................................................................. 99
3.13.3 Set Node Properties ...................................................................................................... 99
3.13.4 Set Environment Properties ........................................................................................ 101
3.13.5 Modifying/Viewing/Accepting Properties .................................................................. 101
3.13.6 Set Application Properties .......................................................................................... 101
4
3.13.7 Enable Packet Trace, Event Trace & Dynamic Metrics (Optional) .............................. 102
3.13.8 Run Simulation ............................................................................................................ 103
3.13.9 Sample Experiment ..................................................................................................... 103
3.13.10 DTDMA Packet size ................................................................................................. 103
3.13.11 Node Join / Leave .................................................................................................... 104
4 Traffic generator in NetSim (Application Models) ............................. 106

4.1 Common properties for all the traffic types ............................................................................. 107
4.2 CBR ............................................................................................................................................ 107
4.3 Custom ...................................................................................................................................... 108
4.4 Voice.......................................................................................................................................... 108
4.5 Video ......................................................................................................................................... 109
4.6 FTP............................................................................................................................................. 112
4.7 Database ................................................................................................................................... 113
4.8 Peer to Peer .............................................................................................................................. 113
4.9 HTTP .......................................................................................................................................... 114
4.10 Email........................................................................................................................................ 115
4.11 Sensor App .............................................................................................................................. 115
4.12 Erlang Call................................................................................................................................ 116
4.13 Emulator.................................................................................................................................. 117
4.14 Priority and QoS of Applications ............................................................................................. 118
4.15 Modelling Poisson arrivals in NetSim...................................................................................... 119
5 Running simulation via CLI ................................................................ 121

5.1 Running NetSim via CLI ............................................................................................................. 121
5.1.1 Running CLI via Quick edit mode ................................................................................ 125
5.2 Understanding Configuration.xml file ....................................................................................... 126
5.2.1 How to use Visual Studio to edit the Configuration file? ............................................ 127
5.2.2 Sections of Configuration file ...................................................................................... 128
5.2.3 Sample Configuration file............................................................................................ 129
5.2.4 Configuration.xsd file .................................................................................................. 129
6 Analysis ............................................................................................ 130

6.1 Performance Metrics ................................................................................................................ 130
5
6.2 Packet Animation ...................................................................................................................... 134
6.2.1 Example on how to use NetSim packet animation feature: ....................................... 136
6.3 Dynamic Metrics (only in Standard/Pro Version) ..................................................................... 139
6.4 Analytics Menu (Multiple Experiments) ................................................................................... 140
6.5 Packet Trace (only in Standard/Pro Version) ............................................................................ 142
6.5.1 Introduction ................................................................................................................ 142
6.6 Event Trace (only in Standard/Pro Version).............................................................................. 146
6.6.1 NetSim Network Stack ................................................................................................ 146
6.7 Trace Data Analysis (only in Standard/Pro Version) ................................................................. 149
6.8 Packet Capture & analysis using Wireshark (www.wireshark.com) (only in Standard/Pro
Version) ........................................................................................................................................... 152
6.8.1 Enabling Wireshark in the network scenario .............................................................. 152
6.8.2 Viewing captured packets ........................................................................................... 152
6.8.3 Filtering captured packets........................................................................................... 153
6.8.4 Analyzing packets in Wireshark .................................................................................. 154
7 Custom code in NetSim ..................................................................... 159

7.1 Writing your own code ............................................................................................................. 159
7.1.1 Modifying code ........................................................................................................... 159
7.1.2 Building Dlls ................................................................................................................. 161
7.1.3 Linking Dlls .................................................................................................................. 163
7.1.4 Running Simulation ..................................................................................................... 164
7.2 Implementing your code - Examples ........................................................................................ 165
7.2.1 Hello World Program .................................................................................................. 165
7.2.2 Introducing Node Failure in MANET ........................................................................... 166
7.2.3 Transferring file from source to destination in WSN .................................................. 168
7.3 Debugging your code ................................................................................................................ 173
7.3.1 Via GUI ........................................................................................................................ 173
7.3.2 Via CLI and co-relating with event trace ..................................................................... 176
7.3.3 Viewing & Accessing variables .................................................................................... 182
7.4 NetSim API’s .............................................................................................................................. 190
8 Advanced Features ........................................................................... 192

8.1 Random number Generator and Seed Values .......................................................................... 192
8.2 Static Routing ............................................................................................................................ 193
6
RIP .............................................................................................................................................. 193
8.3 Mobility Models in NetSim ....................................................................................................... 197
8.3.1 Random Walk mobility model..................................................................................... 197
8.3.2 Random Waypoint Mobility Model ............................................................................ 197
8.3.3 Group mobility ............................................................................................................ 197
8.3.4 File Based Mobility ...................................................................................................... 197
8.4 Interfacing MATLAB with NetSim ............................................................................................. 200
8.4.1 Implement Nakagami Distribution of MATLAB in NetSim without using .m file ........ 200
8.4.2 Debug and understand communication between NetSim and MATLAB.................... 209
8.4.3 Implement Nakagami Distribution of MATLAB in NetSim using .m file: ..................... 213
8.4.4 Plot a histogram in MATLAB using the values generated by Nakagami distribution for
NetSim (using .m file) .................................................................................................................. 215
8.5 Adding Custom Performance Metrics ....................................................................................... 219
9 Programming Exercises ..................................................................... 221

9.1 Architecture .............................................................................................................................. 223
9.2 Creating .exe file for Programming Exercise ............................................................................. 224
9.2.1 Using Visual Studio ...................................................................................................... 224
9.2.2 Using GCC .................................................................................................................... 229
9.2.3 Using Dev C++ ............................................................................................................. 231
9.3 Steps to perform Programming Exercise in NetSim ................................................................. 234
9.4 How to De-bug your code linked to NetSim’s Programming Exercise ...................................... 235
9.5 Programming Exercises ............................................................................................................. 238
9.5.1 Address Resolution Protocol ....................................................................................... 238
9.5.2 Assignment of Sites to Concentrator .......................................................................... 241
9.5.3 Cryptography - Substitution - Encryption ................................................................... 244
9.5.4 Cryptography - Substitution - Decryption ................................................................... 246
9.5.5 Cryptography - Transposition - Encryption ................................................................. 249
9.5.6 Cryptography - Transposition – Decryption ................................................................ 250
9.5.7 Cryptography - XOR - Encryption ................................................................................ 253
9.5.8 Cryptography - XOR - Decryption ................................................................................ 254
9.5.9 Cryptography - Data Encryption Standard (DES) - Encryption .................................... 257
9.5.10 Cryptography - Data Encryption Standard (DES) - Decryption.................................... 260
9.5.11 Rivest-Shamir - Adleman Algorithm (RSA) .................................................................. 264
7
9.5.12 Cryptography - Wired Equivalent Privacy (WEP) – Encryption ................................... 266
9.5.13 Cryptography - Wired Equivalent Privacy (WEP) - Decryption ................................... 268
9.5.14 Distance Vector Routing ............................................................................................. 271
9.5.15 Distance Host Configuration Protocol......................................................................... 274
9.5.16 Error Correcting Code - Hamming Code ..................................................................... 277
9.5.17 Error Detection Code - Cyclic Redundancy Check (CRC) - 12 ...................................... 280
9.5.18 Error Detection Code - Cyclic Redundancy Check (CRC) – 16 ..................................... 283
9.5.19 Error Detection Code - Cyclic Redundancy Check (CRC) - 32 ...................................... 286
9.5.20 Error Detection Code - Cyclic Redundancy Check (CRC) – CCITT ................................ 289
9.5.21 Error Detection Code - Longitudinal Redundancy Check (LRC) .................................. 292
9.5.22 Framing Sequence – Bit Stuffing ................................................................................. 294
9.5.23 Framing Sequence – Character Stuffing...................................................................... 297
9.5.24 Virtual Scheduling Algorithm ...................................................................................... 300
9.5.25 Address Mask .............................................................................................................. 303
9.5.26 Binary Conversion ....................................................................................................... 305
9.5.27 Classless InterDomain Routing.................................................................................... 308
9.5.28 Network Address......................................................................................................... 312
9.5.29 Special Addresses ........................................................................................................ 314
9.5.30 Subnetting ................................................................................................................... 316
9.5.31 EUI-64 Interface Identifier .......................................................................................... 319
9.5.32 IPV6 Host Addresses ................................................................................................... 322
9.5.33 IPV6 Subnetting........................................................................................................... 325
9.5.34 Leaky Bucket Algorithm .............................................................................................. 328
9.5.35 Multi Level Multi Access ............................................................................................. 331
9.5.36 Code Division Multiple Access .................................................................................... 332
9.5.37 Time Division Multiple Access..................................................................................... 338
9.5.38 Orthogonal Frequency Division Multiple Access ........................................................ 342
9.5.39 PC to PC Communication - Socket Programming TCP................................................. 347
9.5.40 PC to PC Communication - Socket Programming UDP ................................................ 352
9.5.41 PC to PC Communication – Chat Application TCP ....................................................... 358
9.5.42 PC to PC Communication – Chat Application UDP ...................................................... 363
9.5.43 Scheduling - First In First Out (FIFO) ........................................................................... 369
9.5.44 Scheduling - Max - Min Fair (MMF)............................................................................. 372
9.5.45 Shortest Path - Floyd’s ................................................................................................ 375
8
9.5.46 Shortest Path - Link State ............................................................................................ 378
9.5.47 Sliding Window Protocol - Go Back N ......................................................................... 381
9.5.48 Sliding Window Protocol - Selective Repeat ............................................................... 386
9.5.49 Sorting Technique - Bubble Sort ................................................................................. 391
9.5.50 Sorting Technique - Insertion Sort .............................................................................. 394
9.5.51 Sorting Technique - Quick Sort ................................................................................... 397
9.5.52 Sorting Technique - Selection Sort .............................................................................. 399
9.5.53 Spanning Tree – Borovska ........................................................................................... 403
9.5.54 Spanning Tree – Kruskal .............................................................................................. 406
9.5.55 Spanning Tree – Prims................................................................................................. 409
9.5.56 Transmission Flow Control - Go Back N ...................................................................... 412
9.5.57 Transmission Flow Control - Selective Repeat ............................................................ 416
9.5.58 Transmission Flow Control - Stop and Wait ................................................................ 420
9.6 Programming exercise - How to practice without NetSim ....................................................... 424
10 NetSim Emulator ............................................................................... 428

10.1 Introduction ............................................................................................................................ 428
10.1.1 Emulation: How Simulation interacts with the real world.......................................... 428
10.2 Emulation Set-up: ................................................................................................................... 429
10.2.1 Setting up the NetSim Server: ..................................................................................... 429
10.2.2 Setting up the NetSim Client: ...................................................................................... 430
10.2.3 Setting multiple Virtual Machines (VM) to act as Nodes for Emulation ..................... 432
10.3 Emulation examples in NetSim ............................................................................................... 435
10.3.1 Example Application 1 – PING (One way Communication)......................................... 435
10.3.2 Example Application 1 – PING (Two way Communication) ........................................ 437
10.3.3 Example Application 2 – Video (One way Communication) ....................................... 438
10.3.4 Example Application 3 – File Transfer using FileZilla (One way Communication) ...... 443
10.3.5 Example Application 4 –Skype (Two way Communication) ........................................ 446
10.3.6 Example Application 5 – JPerf Network performance measurement graphical tool
(One way Communication) ......................................................................................................... 448
11 Troubleshooting in NetSim................................................................ 451

11.1 CLI mode ................................................................................................................................. 451
11.1.1 I/O warning displayed in CLI mode: ............................................................................ 451
11.1.2 Connection refused at server<-111> error displayed: ................................................ 452
9
11.1.3 Unable to load license config dll(126) problem: ......................................................... 452
11.1.4 “Error in getting License” error in CLI mode: .............................................................. 453
11.1.5 Unable to load license config dll displayed: ................................................................ 454
11.2 Configuration.xml ................................................................................................................... 455
11.2.1 Blue zigzag lines in configuration file attributes: ........................................................ 455
11.2.2 Red zigzag lines in configuration file attributes: ......................................................... 455
11.2.3 Zigzag lines appearing at configuration.xsd in the Configuration file:........................ 456
11.2.4 Simulation terminates and “NetSim Backend has stopped working” displayed: ....... 457
11.2.5 Monitor screen resolution is less than 1024X768: ..................................................... 458
11.3 Licensing .................................................................................................................................. 458
11.3.1 No License for product (-1) error ................................................................................ 458
12 Known Issues in NetSim v9 ............................................................... 459

12.1 User modified parameters in device properties will not reflect in newly dropped devices .. 459
12.2 Dynamic metrics not updated on modifying scenario ............................................................ 459
12.3 Packet animation in map view does not show node mobility ................................................ 459
12.4 Device properties does not revert to default values .............................................................. 460
12.5 Incumbent ID in network and metrics not matching .............................................................. 460
12.6 BGP link speed issues .............................................................................................................. 460
12.7 Dynamic Metrics limit is 500 graphs ....................................................................................... 460
12.8 Running Application between unconnected nodes ................................................................ 460
12.9 RIP Hop count ......................................................................................................................... 461
12.10 Default gateway can’t be empty ........................................................................................... 461
12.11 Packet size limit in TDMA(Military Radio)............................................................................. 461
12.12 Removing link between switches leads to IP addressing issue............................................. 461
12.13 Packet animation simulation time bar is not functioning properly in WSN, IOT .................. 461
13 NetSim Videos .................................................................................. 462
10
1 NetSim – Introduction
1.1 Introduction to modeling and simulation of networks

A network simulator enables users to virtually create a network along with its components
such as devices, links, and applications etc. to study the behavior and performance of the
Network.
Some examples of applications of network simulators are
 Protocol performance analysis

 Application modeling and analysis
 Network design and planning
 Research and development of new networking technologies
 Test and verification
The key features essential to any network simulation are -
 Building the model – Create a network scenario with devices, links, applications etc
 Running the simulation - Run the discrete event simulation (DES) and log different
performance metrics
 Visualizing the simulation- Use a packet animator to view the flow of packets
 Analyzing the results - Examine output performance metrics such as throughput,
delay, loss etc. at multiple levels - network, sub network, link, queue, application etc.
 Developing your own protocol / algorithm - Extend existing algorithms by
modifying the simulators source C code
11
1.2 Versions of NetSim – Academic, Standard & Pro
NetSim is used by people from different areas such as academics, industry and defense to
design, simulate, analyze and verify the performance of different networks.
NetSim comes in three versions- Academic, Standard and Pro. The academic version is
used for lab experimentation and teaching. The standard version is used for project work and
research while Pro version addresses the needs of defense and industry. The standard and pro
versions are available as components in NetSim v9 from which users can choose and
assemble. The academic version is available as a single product and includes all the
technologies shown below. The main differences between the various versions are tabulated
below:
Features Academic Standard Pro

Technology Coverage
Internetworks   
Legacy Networks   
BGP   
Advanced Wireless Networks   
Cellular Networks   
Wireless Sensor Networks   
Internet of Things   
Zigbee   
Cognitive Radio Networks   
LTE/LTE-A Networks   
Military Radio: TDMA-Link16,HF,VHF,UHF
Bands
  
Basics
Understand networking concepts using   
more than 400 animations
Performance Reporting
Performance metrics available for   
Network and Sub-network
Packet Animator
Used to animate the packet flow in   
network
Packet Trace and Event Trace
Available in tab ordered .txt format for   
easy post processing
Protocol Library Source Codes with
Documentation
  
Protocol C source codes and appropriate
header files with extensive documentation
External Interfacing
Interfacing with SUMO, MATLAB and   
Wireshark
12
Integrated debugging
Users can write their own code, link their
  
code to NetSim and debug using Visual
Studio
Dynamic Metrics
Allows users to plot the value of a   
parameter over simulation time
50 Nodes 1,00,000 Nodes
500 Nodes
Simulation Scale 32 bit 32bit/64bit
32 bit build
build build
Custom Coding and Modeling Support   
Emulator (Add on)
Connect to real hardware running live   
application
Educational
Commercial
(Lab Educational
Target Users and Segment Experiment (Research)
(Industrial and
Defense)
ation)
13
1.3 Components in Pro and Standard versions
In NetSim v9, users can choose and assemble components for Pro and Standard version. The
components are as follows:
Component No Networks / Protocols International Standards

Internetworks
Ethernet - Fast & Gigabit
Address Resolution Protocol IEEE 802.3
WLAN - 802.11 a, b, g , n, ac ,e & p RFC 826
Propagation – Free space, Log-normal 802.11 a/b/g/n/ac/e
Shadowing, Rayleigh Fading
IP v4, Firewalls
Routing - RIP, OSPF
Queuing - Round Robin, FIFO, Priority,
Component 1 WFQ RFC 2453,2328
(Base. TCP, UDP
Required for RFC's 793, 2001 and 768
all Common Modules
components) Applications (Traffic Generator): CBR,
Voice, Video, FTP, Database, HTTP,
Email, Peer-to-peer and Custom
Application encryption – AES, DES
Virtual Network Stack
Simulation Kernel
Command Line Interface
Metrics Engine with packet trace, event
trace and dynamic metrics
Packet Animator,
Legacy Networks IEEE 802.3
Aloha – (Pure & Slotted) IEEE 802.4
CSMA/CD IEEE 802.5
Component 2
Token Ring ATM Forum
Token Bus ITU Forum
IETF RFC 3031
BGP Networks
Component 3
Border Gateway Protocol (BGP) IETF RFC‟s 1771 & 3121
Advanced Wireless Networks IETF RFC 4728, 3561, 3626

Component 4 MANET - DSR, AODV, OLSR, ZRP, IEEE 802.16d
VANET and Wi-Max
Cellular Networks 3GPP, ETSI, IMT-MC, IS-95

Component 5 GSM A/B, IxRTT, 1x-EV-Do,
CDMA 3xRTT
14
Wireless Sensor Networks, Internet
Component 6 of Things & ZigBee
IEEE 802.15.4 MAC ,
(Component 4 WSN with agent model & battery MANET in L3
required) models
ZigBee
Cognitive Radio Networks

Component 7 WRAN IEEE 802.22
Long Term Evolution

Component 8 LTE/LTE-Advanced 3GPP
Military Radio (Only in PRO

Component 9 Version)
(Component 4 TDMA Link 16, Dynamic TDMA, ----
required) Frequencies – HF,VHF, UHF Bands
Network Network Emulator – Connect real

Emulator hardware running live applications to ----
Add On NetSim Simulator
15
2 Getting Started in NetSim
2.1 Installing NetSim in Client
Note: Based on the NetSim version under installation the version type being displayed in the
following windows will change. For example you will see NetSim Standard for a standard
version install –
Click on Yes button to install the software.
Setup prepares the installation wizard and

software installation begins with a
Welcome Screen.
Click on the Next button
In the next screen, License agreement will

be displayed.
16
Read the agreement carefully, scroll down to read the complete license agreement. If the
requirement of the license agreement is accepted click “I Agree” button else quit the setup by
clicking Cancel button.
If you agree with the license agreement, you will be prompted to select the components to be
installed. The list of components is available for selection and assembly only in the Standard
and Pro version. Other versions of NetSim are available as a single package.
Click on the Next button.
Note: Select all the supporting applications

for complete installation of the software.
In the next screen, you will be requested to

enter the installation path
Select the path in which the software needs

to be installed and click on Next button.
Note: In the case of 64 bit machine, ensure

that the path is <OS installed drive>:/Program
Files(x86)/NetSim Standard
In the next screen, you will be requested to

enter the Start menu folder name.
17
Click on the Install button to start the
installation.
The installation process begins.
After the installation of required files, the

installation of supporting software begins.
For NetSim Academic, Adobe Flash
Player will be installed. For NetSim
Standard Version and Pro Version,
gnuplot installation will start by default (if
not deselected during 3rd party software
selection)
The below screen will appear to choose the

language.
After selecting English language, next screen is

as follows
Click on the Next button to install gnuplot

(Supporting Software), License Agreement
screen will appear as shown:
18
Click on I accept the agreement and then
Next icon as shown above.
Click on Next.
In the next screen, you will be requested to enter

the installation path. Select the installation path
and click on Next icon:
19
In this screen, select Full installation and
components to be installed and select
Next. All the components are required
except Japanese language support:
Set the Start Menu Folder name.
Select Next when the additional tasks

screen appears. No settings are changed.
20
Click Install to continue with the
installation, the following screen appears:
Click on Next.
After completion of the installation of the

software, the “Completing gnuplot Setup
Wizard” screen will be displayed.
Click on the Finish button to complete the

gnuplot installation.
For NetSim Standard Version and Pro Version, Wireshark installation will start by default ( if not
deselected during 3rd party software selection)
21
Click on Next to start Wireshark installation.
In the following window, click on I Agree.
Click on I Agree.
Select all the components and click on Next.
Click on Next to go to Install Location window

as shown below.
22
Specify the destination and select Next.
Select Install WinPcap and click on Install.
After the installation of the software, you will

be requested to click Finish to complete the
installation process.
To start Python software installation,

Select whether to install for all users or
particular user alone.
Click on Next.
Click on Next.
23
Click on Next and the
installation begins.
Click on Finish.
To install Pywin32,
Click on Next.
Select the Python directory and

Click on Next.
24
Click on Next and the installation
Pywin32 begins.
Click on Finish. This completes the installation

of Python Software.
Select “Run NetSim” and then click on the

Finish button.
This completes the installation of NetSim

Software.
Note: During the installation of NetSim Academic version the supporting software installed are
Adobe Flash player and WinPcap.
25
2.2 Setting up License Server
2.2.1 Installing NetSim RLM Dongle
This section guides you to install the RLM Dongle software from the CD-ROM.
 Insert the CD-ROM disc in the CD drive.

 Double click on My Computer and access the CD Drive
 Double click on Driver_Software folder.
 Double click on HASPUserSetup.exe
Each prompt displayed during the process tells you what it is about to do and prompts to
either continue or Exit.
Setup prepares the installation wizard and the software installation begins with a Welcome
Screen.
Note: Any other program running during the

installation of the Dongle will affect the
proper installation of the software.
In the next screen, the License agreement is

displayed.
Read the license agreement carefully,

scroll down to read the complete license
agreement. If the requirement of the
license agreement is accepted select the “I
accept” button else quit the setup by
clicking Cancel button.
26
Click on the Next button. The installation

process begins.
After the installation of the software, you will be requested to click Finish button to complete
the installation process.
Now the RLM driver software is installed successfully.
If the driver has been successfully installed then upon connecting the Dongle in the USB port
red light would glow (Refer picture below). If the driver is not correctly installed this light
will not glow when the dongle is connected to the USB port.
27
2.2.2 Running RLM Dongle (Server)
After the Driver Software installation, connect the RLM dongle to the system USB port.
 Double click on My Computer and access the CD Drive

 Copy the NetSim License Server folder and paste it on Desktop.
 Double click on NetSim License Server folder from Desktop.
 Double click on rlm.exe
Note: For running NetSim, rlm.exe must be running in the server (license server) system and
the server system IP address must be entered correctly. Without running rlm.exe, NetSim
won‟t run.
When you run rlm.exe, the screen will appear as shown below.
28
2.2.3 Running NetSim Software
After running rlm.exe, click the NetSim icon in the Desktop.
The screen given below will be obtained.
Enter the Server IP address where the

rlm.exe is running, then click ok button.
You have now reached to the main menu of

NetSim,
29
2.3 Menus in NetSim
In Academic/Standard Version
Opens the Simulation menu consisting of New, Open, Save, Save As and Analytics.
User can simulate Internetworks, Legacy, BGP, Advanced Wireless Networks
(MANET, VANET and Wimax), Cellular, Wireless Sensor Networks, Internet of
Things, Zigbee Networks, Cognitive Radio Networks and LTE/LTE-A Networks.
Opens the Programming menu where different

network programming lab exercises are available.
Consists of Animated explanations of Displays all the Help related to

networking principles, protocol working NetSim. Help covers Simulation
and packet formats. Experiments also.
NOTE: Present in Academic version
only
In Pro Version
Displays all the Help related to NetSim. Help covers

Simulation Experiments also.
Opens the Simulation menu consisting of New, Open, Save, Save As and Analytics.
User can simulate Internetworks, Legacy, BGP, Advanced Wireless Networks
(MANET, VANET, Wimax), Cellular, Wireless Sensor Networks, Internet of Things,
ZigBee Networks, Cognitive Radio Networks and LTE/LTE-A Networks.
30
2.3.1 Simulation Menu
The Simulation menu contains options such as New, Open, Save, Save As and Analytics.
2.3.1.1 New
Click on New and select the desired protocol from
Internetworks, Legacy, BGP, Advanced Wireless-
(MANET, VANET, Wi-max), Cellular, Personal Area,
Wireless Sensor, Internet of Things, ZigBee Networks,
Cognitive Radio and LTE/LTE-A Networks to create a
new network scenario.
2.3.1.2 Open
To open an already created network scenario, go to Open  Network.
To open the performance metric window of already

simulated network scenario, go to Open Metrics.
Refer Section 2.3 for detailed understanding.
2.3.1.3 Save
To save any Network scenario, go to Save.
A. To Save any specific experiment, select Save, then specify the Experiment Name,
Path and click Ok.
2.3.1.4 Save As
To save any Network scenario, go to Save As.
B. To Save any specific experiment with different name and different path, select
Save As, then specify the Experiment Name, Path and click Ok.
31
2.3.1.5 Analytics
To compare the metrics of various network scenarios of same network, go to Analytics.

2.3.2 Programming Menu
The Programming menu contains network programming exercises. Click on this menu and
select the desired programming exercise.
Note: This menu is available only in Academic and Standard Version.
Upon selection, the following screen will appear. Please refer Section 9(NetSim
Academic/Standard User Manual) for detailed help.
Using the “User mode” users can link and run their
own source code.
Clicking on the Concept, Algorithm, Pseudo Code

and Flowchart would open-up for that program.
Clicking on Interface Source Code

32
will open the .c source files
2.3.3 Basics
In this menu, various network concepts are explained using animations. Note: This menu is
available only in Academic Version.
For example: On selecting “Ethernet” under “Internetworks”, following screen will be

displayed.
2.3.4 Help
This menu contains all the Help related to NetSim.
NetSim User Manual - It contains the documentation about the working of NetSim.
NetSim Source Code Help – It contains the documentation about network protocol source
code (Available with NetSim Standard as well as Pro Version)
33
NetSim Experiment Manual – It contains selected experiments which can be performed in
NetSim.
2.4 Modeling and Simulation of a simple network

This section will demonstrate how to create a basic network scenario and analyze in NetSim.
Let us consider Internetworks. To create a new scenario, go to Simulation  New 

Internetworks
2.4.1 Creating a Network scenario
Consider we want to design a network with two subnets in Internetworks.
Let us say the subnet 1 consists of two wired nodes connected via a Switch and the other
subnet 2 is a wired node. Both the subnets are connected using a Router. Traffic in Network
is generated from a wired node in subnet 1 to the wired node in subnet 2.
Perform the following steps to create the network scenario which looks like this:
34
Step 1: Drop the devices
Click on Node icon and select  Wired Node
Click on the environment (the grid in the center) where you want
the Wired Node to be placed. In this way, place two more wired
nodes.
Similarly to place a Switch and a Router, click on the respective

device and click on the environment at the desired location.
Step 2: Connecting devices on the environment
In order to connect devices present in the environment,

click on Link and select Wired Link.
Click and select the devices successively where link is

required. For example, select wired link and select Switch
and Router successively to connect them. In this manner,
continue to link all devices.
35
2.4.2 Configuring devices and links in the scenario
Step 1: To configure any device, right click on the

device and select properties
User can set values according to requirement. Modify the

properties of any device and click on Accept.
In above scenario, default values already present in the

properties are accepted.
Step 2: To configure the links, right click on any Link and

select Properties.
User can set values

according to requirement.
In above scenario, default

values already present in the
properties are accepted.
36
2.4.3 Modeling Traffic
After the network is configured, user needs to model traffic from Wired Node B to Wired
Node C.
Select the Application Button and click on the gap between the Grid Environment and the
ribbon. Now right click on Application and select Properties.
In above scenario, default values already present in the properties are accepted. The
Source_ID is 2 and Destination_ID is 5. Click on Accept.
2.4.4 Logging Packet/ Event Trace
If the user wants to analyze the simulation result using Packet and Event Trace, then they
need to be enabled before simulation.
37
Click Packet Trace / Event Trace icon in the tool bar. Set the name and path and select the
required attributes. To get detailed help, please refer section 6.5 and 6.6 respectively.
2.4.5 Simulation
For simulating the network scenario created, click on Run

Simulation present in the Ribbon
Set the Simulation Time to 10 seconds. Select OK.
38
2.5 Network – Opening, Saving scenarios and Printing results
2.5.1 Opening Saved Experiments
2.5.1.1 Open Network – All Networks
Go to Simulation  Open  Network menu to open saved experiments. The following

steps need to be followed:
Open saved experiment folder and select the configuration file you want to open.
2.5.1.2 Open Metrics– All Networks
Go to Simulation  Open  Metrics menu to open saved experiments. The following

steps need to be followed:
Click on Browse and select the Metrics.txt file (present with the saved experiment) you want
to open.
39
2.5.2 Saving an Experiment
2.5.2.1 For all Networks
Step 1: After simulation of the

network, on the top left corner
of Performance metrics screen,
click on the “Save Network and
Metric as” button
Step 2: Specify the Experiment Name and Save Path and click on Save.
40
3 Simulating different networks in
NetSim
3.1 Internetworks
Internetwork simulation is available in NetSim with LAN-WAN-LAN modeling capability.
Internetwork runs Ethernet, Wireless LAN, IP Routing and TCP / UDP and allows users to
log packet and event (in NetSim Standard/Pro version only) traces.
3.1.1 New Experiment
In the Simulation menu,

Select  New  Internetworks
3.1.2 Create Scenario
Internetworks come with the palette of

various devices like Switch, Router,
Wired Node, Wireless Node, AP, etc.
Select the desired devices application
icon in the toolbar and click and drop on
the environment.
To remove devices or application, right click on the particular icon and then click Remove.
Select the appropriate link in the toolbar and connect the devices by
clicking on the device 1 and device 2.
41
3.1.3 Set Node, Link and Application Properties
 Right click on the appropriate node or link and select Properties. Then modify the
parameters according to the requirements. Routing Protocol in Application Layer of
router and all user editable properties in DataLink Layer and Physical Layer of Access
Point and Wireless Node are Global except for IEEE802.11e i.e. changing properties in
one node will automatically reflect in the others in that network..
 Select the Application Button on the ribbon and click on the empty region between the
Grid Environment and the ribbon. Now right click on Application and select Properties.
Multiple applications can be generated by using add button in Application properties.
 Set the values according to requirement and click Accept.
42
3.1.4 Enable Packet Trace, Event Trace & Dynamic Metrics (Optional)
Click Packet Trace / Event Trace icon in the tool bar. To get detailed help, please refer
section 6.5, 6.6 and 6.3 respectively. Select Dynamic Metrics icon for enabling Dynamic
Metrics and click OK.
3.1.5 Run Simulation
Click on Run Simulation icon on the top toolbar.
Set the Simulation Time and click on Simulate.
3.1.6 Sample Experiment
A sample network is created in “Configuration.xml” file which is located inside<NetSim

installed Path>\Docs\ Sample_Configuration \Internetworks\Basic Scenario, which the user
can open using NetSim and understand how devices are connected among themselves for that
network and their default properties.
Furthermore, users can open this Configuration.xml file using Visual Studio 2010 and
analyze how to write a designed network scenario manually. Further information is provided
in “Understanding Configuration.xml file” under “Running NetSim via CLI” chapter 5.
3.1.7 IP Addressing in NetSim
When you create a network using the GUI, NetSim will automatically configure the IP
address of the devices in the scenario.
43
Consider the following scenarios:
If you create a network with two wired nodes and a switch, the IP addresses are assigned as
10.0.1.2 and 10.0.1.3 for the two wired nodes. The default subnet mask is assigned to be
255.255.0.0. It can be edited to 255.0.0.0 (Class A) or 255.255.255.0 (Class C) subnet masks.
Both the nodes are in the same network (10.0.0.0).
Similarly, if you create a network with a router and two wired nodes, the IP addressed are
assigned as 11.1.1.2 and 11.2.1.2 for the two wired nodes. The subnet mask is default as in
above case, i.e., 255.255.0.0. The IP address of the router is 11.1.1.1 and 11.2.1.1
respectively for the two interfaces. Both the nodes are in different networks (11.1.0.0 and
11.2.0.0) in this case.
The same logic is extended as the number of devices is increased.
3.1.8 SINR, BER and Propagation models for 802.11 a, b, g and n

3.1.8.1 Received Power Calculation
The received power can be expressed as

[Prec]dbm = 10log10 (Pt) + [GT] + [GR] + 20log10 (λ/4πd0) + 10ηlog (d0/d) + Pshadow loss + Pfading
Where Pt = Power Transmitted (in mwatts)

GT=Gain of the transmitting antenna (in dB)
GR=Gain of the receiving antenna (in dB)
λ = Wavelength (in meters)
d0= Reference distance (at which the path loss inherits free space path loss)
η = Path loss exponent (ranges between 2 to 5)
Pshadow loss = Power due to Shadowing (in dB)
Pfading = Power due to Fading (in dB)
The code for calculating the received power is included in the file PropagationModel.c, path
for the file is NetSim Standard\src\Simulation\IEEE802_11.
44
3.1.8.2 Propagation Loss
Three different and mutually independent propagation phenomena influence the power of the
received signal: path loss, shadowing and multipath fading.
3.1.8.2.1 Path Loss
Path loss is the reduction in power density of an electromagnetic wave as it propagates

through space. Path loss may be due to many effects, such as free reflection, aperture-
medium coupling loss, and absorption.
Path loss can be represented by the path loss exponent, whose value is normally in the range
of 2 to 5, where 2 is for propagation in free space.
In NetSim, the default value for path loss exponent is taken as 2.
Path loss is usually expressed in dB. In its simplest form, the path loss can be calculated
using the formula
L=10ηlog (d0/d)
Where L is the path loss in decibels, η is the path loss exponent and d is the distance between
transmitter and the receiver, usually measured in meters.
A simplified formula for the path loss between two isotropic antennas in free space:
L (in dBm) = 20log10 (4πd0/λ)
Where L is the path loss in decibels, λ is the wavelength and d is the transmitter-receiver
distance in the same units as the wavelength.
The code for calculating the Path loss is included in the function calculate_pathloss(), which
is present in the file PropagationModel.c, path for the file is NetSim
Standard\src\Simulation\IEEE802_11.
3.1.8.2.2 Shadowing
Slow shadowing in wireless network is the attenuation caused by buildings or any obstacles
between a transmitter and a receiver. In the model with shadowing, the shadowing value X
typically defined in dB, is added to (or subtracted from) the average received power zero
means Gaussian distributed random variable with standard deviation. The default value for
standard deviation is chosen as 5 dB.
The code for calculating the shadow loss is present in file PropagationModel.c, path for the
file is NetSim Standard\src\Simulation\IEEE802.11.
45
3.1.8.2.3 Fading
In wireless communications, fading is deviation of the attenuation affecting a signal over

certain propagation media. The fading may vary with time, geographical position or radio
frequency, and is often modelled as a random process.
In NetSim, the Rayleigh Fading, which follows Rayleigh Probability Distribution with mean
of 1, is used. The code for calculating fading loss is present in the file PropagationModel.c,
path for the file is NetSim Standard\src\Simulation\IEEE802_11.
3.1.8.3 SINR Calculation
Analogous to the SNR used often in wired communications systems, the SINR is defined as
the power of a certain signal of interest divided by the sum of the interference power (from
all the other interfering signals) and the power of some background noise.
The interference power is the difference between the total power received by the receiver and
the power received from one particular transmitter.
The background thermal noise in dBm at room temperature is given by:

PNoise (in dBm) = -174+10log10 (Δf)
Where Δf is the Bandwidth in Hertz. For 802.11a, b, g, Δf = 20 MHz, and for 802.11n, Δf =
20 MHz or 40 MHz.
Therefore, SNR (in dBm) = Power Received (in dBm) - PNoise (in dBm)
3.1.8.4 Bit Error Rate (BER) Calculation
The bit error rate (BER) is the number of bit errors divided by the total number of transferred
bits during a studied time interval. The BER calculation has been done as a hash-table based
on the BER curves for different modulation schemes.
The code for calculating SNR and implementation of SNR vs. BER is included in the
function fn_NetSim_WLAN_802_11x_BER of the file 802_11_x.c (where x=a, b, g and n),
you can find it in the following path NetSim Standard\src\Simulation\IEEE802_11.
46
SNR vs. BER curve for MPSK (where M=2k)
(Reference: From Page 221 Digital Communications by Bernard Sklar 2nd Edition)
SNR vs. BER curve for 5.5CCK and 11CCK
Bit Error Rate

10 0
-1
10
10 -2
5.5CCK
BER
-3
10
TextEnd 11CCK
10 -4
-5
10
-6
10
0 1 2 3 4 5 6 7 8 9 10
Eb/No
(Reference: Higher Rate 802.11b: Double the Data Rate Chris Heegard, Matthew Shoemake & Sid
Schrum Doc: IEEE 802.11-00/091)
47
SNR vs. BER curve for MQAM
(Reference: BER Comparison of M-ary QAM by Mukthar Hussain MATLAB File Exchange)
3.1.8.5 SNR vs. BER Table followed in NetSim
SNR(in BPSK QPSK 16QAM 64QAM 5.5 CCK 11 CCK

dB)
0 to 0.5 7.00E-02 2.50E-01 1.50E-01 1.75E-01 4.50E-01 5.50E-01
0.5 to 1 6.00E-02 2.45E-01 1.35E-01 1.70E-01 4.50E-01 5.50E-01
1 to 1.5 5.00E-02 2.40E-01 1.15E-01 1.65E-01 1.75E-01 2.75E-01
1.5 to 2 4.00E-02 2.35E-01 1.00E-01 1.60E-01 1.75E-01 2.75E-01
2 to 2.5 2.50E-02 2.25E-01 9.50E-02 1.50E-01 9.50E-02 1.50E-01
2.5 to 3 1.50E-02 2.15E-01 9.00E-02 1.40E-01 9.50E-02 1.50E-01
3 to 3.5 1.00E-02 2.05E-01 8.00E-02 1.30E-01 4.50E-02 8.50E-02
3.5 to 4 9.50E-03 1.95E-01 7.00E-02 1.20E-01 4.50E-02 8.50E-02
4 to 4.5 9.00E-03 1.85E-01 6.00E-02 1.10E-01 9.50E-03 3.50E-02
4.5 to 5 7.00E-03 1.75E-01 5.00E-02 1.00E-01 9.50E-03 3.50E-02
5 to 5.5 5.00E-03 1.65E-01 4.00E-02 9.80E-02 6.00E-03 6.00E-03
5.5 to 6 2.50E-03 1.55E-01 3.00E-02 9.20E-02 6.00E-03 6.00E-03
6 to 6.5 1.50E-03 1.45E-01 2.00E-02 8.40E-02 1.50E-03 1.50E-03
6.5 to 7 8.50E-04 1.35E-01 1.00E-02 7.60E-02 1.50E-03 1.50E-03
7 to 7.5 7.00E-04 1.25E-01 9.50E-03 6.80E-02 6.00E-04 6.50E-04
7.5 to 8 2.00E-04 1.15E-01 8.00E-03 6.00E-02 6.00E-04 6.50E-04
8 to 8.5 9.00E-05 9.50E-01 6.50E-03 5.00E-02 7.00E-05 9.50E-05
48
8.5 to 9 6.00E-05 8.75E-02 5.00E-03 4.00E-02 7.00E-05 9.50E-05
9 to 9.5 3.00E-05 7.50E-02 3.50E-03 3.00E-02 7.00E-06 1.50E-06
9.5 to 10 1.50E-05 6.50E-02 2.00E-03 2.50E-02 7.00E-06 1.50E-06
10 to 11 1.00E-06 5.00E-02 1.00E-03 9.50E-03 8.00E-07 1.50E-07
11 to 12 1.00E-07 2.50E-02 7.00E-04 6.50E-03 9.50E-08 5.50E-08
12 to 13 1.00E-08 1.50E-02 3.00E-04 3.50E-03 2.50E-09 9.50E-09
13 to 14 1.00E-09 9.50E-03 1.00E-05 9.50E-04 1.00E-10 1.00E-10
14 to 15 1.00E-09 7.00E-03 1.00E-06 7.00E-04 1.00E-10 1.00E-10
15 to 16 1.00E-09 2.00E-03 1.00E-07 3.50E-04 1.00E-10 1.00E-10
16 to 17 1.00E-09 1.00E-06 1.00E-07 1.00E-05 1.00E-10 1.00E-10
3.1.9 Features in WLAN 802.11n/ac

3.1.9.1 IEEE 802.11n Standard
Mac aggregation and block acknowledgement are two important enhancements to 802.11n
standard. In the aggregation scheme, several MPDU‟s (MAC Protocol Data Units) are
aggregated in to a single A-MPDU (Aggregated MPDU).
The A-MPDU‟s are created before sending to PHY layer for transmission. The MAC does
not wait for MPDU‟s before aggregation. It aggregates the already present packets in the
queue to form an A-MPDU. The maximum size of A-MPDU is 65535 bytes. The maximum
size of each MPDU is 4KB. In A-MPDU, each MPDU has a delimiter of 32bits at the
beginning and padding at the end. These padding bytes ensure that size of MPDU is a
multiple of 4bytes.
In 802.11n, a single block acknowledgement is sent for the entire A-MPDU. The block ack
acknowledges each packet that is received. It consists of a bitmap (compressed bitmap) of
64bits or 8 bytes. This bitmap can acknowledge upto 64 packets, 1bit for each packet.
49
The value of a bitmap field is 1 if respective packet is received without error else it is 0. Only
the error packets are resent until a retry limit is reached. The number of packets in an A-
MPDU is restricted to 64 since the size of block ack bitmap is 64bits.
Block Ack Control Packet
3.1.9.2 Details of 802.11 n implementation in NetSim –
 NetSim aggregates packets in terms of numbers and not size.

 A user can vary the number of packets to aggregate by changing the appropriate
parameters in the GUI.
 NetSim ignores the padding bytes added to the MPDU since its effect is negligible.
 NetSim aggregates packets to the same receiver id and not to the destination ID.
Packets arriving from the NETWORK Layer gets queued up in an access buffer from
which they are sorted according to their priority in the respective QOS buffer according to the
IEEE 802.11e standard. An event MAC_OUT with SubEvent CS (Carrier Sense – CSMA) is
added to check if the medium is free
50
In CS, if the medium is free, then the NAV is checked. This is enabled if RTS/CTS
mechanism is enabled which can be done so by adjusting the RTS Threshold. If the
Present_Time>NAV, then an Event MAC_OUT with SubEvent DIFS End is added at the
time Present_Time + DIFS time.
The medium is checked at the end of DIFS time period and a random time BackOff is
calculated based on the Contention Window (CW). An Event MAC_OUT with SubEvent
Backoff is added at time Present_Time + BackOff Time.
Once Backoff is successful, NetSim starts the transmission process wherein it gets the
aggregated packet from the QOS buffer and stores it in the Retransmit buffer. If the A-MPDU
size is > RTS Threshold, then it enables RTS/CTS mechanism which is an optional feature.
NetSim sends the packet by calling the PHY_OUT Event with SubEvent AMPDU_Frame.
Note that the implementation of A-MPDU is in the form of a linked list.
51
Whenever a packet is transmitted, the medium is made busy and a Timer Event with
SubEvent Update Device Status is added at the transmission end time to set the medium again
as idle.
Events PHY_OUT SubEvent AMPDU_SubFrame, Timer Event SubEvent Update Device
Status and Event PHY_IN SubEvent AMPDU_SubFrame are added in succession for each
MPDU (Subframe of the aggregated packet). This is done for collision calculations. If two
stations start transmission simultaneously, then some of the SubFrames may collide. Only
those collided SubFrames will be retransmitted again. The same logic is followed for an
Errored packet. However, if the PHY header (the first packet) is errored or collided, the entire
A-MPDU is resent.
At the receiver, the device de-aggregates the packet in the MAC Layer and generates a
block ACK which is sent to the transmitter. If the receiver is an intermediate node, the de-
aggregated packets are added to the access buffer of the receiver in addition to the packets
which arrive from Network layer. If the receiver is the destination, then the received packets
are sent to the Network layer. At the transmitter side, when the device receives the block
acknowledgement, it retransmits only those packets which are errored. The rest of the packets
are deleted from the retransmit buffer. This is done till all packets are transmitted successfully
or a retransmit limit is reached after which next set of packets are aggregated to be sent.
52
3.1.9.3 802.11ac MAC and PHY Layer Implementation
Improvements in 802.11ac compared to 802.11n
Feature 802.11n 802.11ac
Spatial Streams Up to 4 streams Up to 8 streams

MIMO Single User MIMO Multi-User MIMO
Channel
20 and 40 MHz 20, 40, 80 and 160 MHz (optional)
Bandwidth
BPSK, QPSK, BPSK, QPSK, 16QAM, 64QAM
Modulation
16QAM and 64QAM and 256QAM (optional)
Max Aggregated
65536 octets 1048576 octets
Packet Size
MAC layer improvements include only the increment of number of aggregated packets from
1 to 64. The MCS index for different modulation and coding rates are as follows:
MCS Index Modulation Code Rate
0 BPSK 1/2
1 QPSK 1/2
2 QPSK 3/4
3 16QAM 1/2
4 16QAM 3/4
5 64QAM 2/3
6 64QAM 3/4
7 64QAM 5/6
8 256QAM 3/4
9 256QAM 5/6
53
Receiver sensitivity for different modulation schemes in 802.11ac (for a 20MHz Channel
bandwidth) are as follows:
MCS Index Receiver Sensitivity (in dBm)
0 -82
1 -79
2 -77
3 -74
4 -70
5 -66
6 -65
7 -64
8 -59
9 -57
Number of subcarriers for different channel bandwidths
Capacity relative to
PHY Standard Subcarriers
20MHz in 802.11ac
802.11n/802.11ac 20MHz Total 56, 52 Usable (4 pilot) x1.0

Now with the knowledge of MCS index and bandwidth of the channel data rate is set in the
following manner
Step1: Get the number subcarriers that are usable for the given bandwidth of the medium.
Step2: Get the Number of Bits per Sub Carrier (NBPSC) from selected MCS
Step3: Number of Coded Bits Per Symbol (NCBPS) = NBPSC*Number of Subcarriers
Step4: Number of Data Bits Per Symbol (NDBPS) = NCBPS*Coding Rate
Step5: Physical level Data Rate = NDBPS/Symbol Time (4micro sec for long GI and 3.6
micro sec for short GI)
54
3.2 Legacy Networks
In the Simulation menu select  New
 Legacy Networks
For example, to arrive Pure Aloha,
In the Simulation menu select  New
 Legacy Networks  Pure Aloha.

Adding Node:
 Click on the Node icon in the tool bar and click and drop inside the grid. (Note: This is
applicable for Pure Aloha and Slotted Aloha)
 Nodes cannot be connected directly to each other because an intermediate connecting
component (such as Hub or Concentrator) is required. (Note: This is applicable for
CSMA/CD, Token Bus and Token Ring)
Adding Hub:
 Click on the Hub icon in the tool bar and click it onto the environment. By default a Hub
has 24 ports. (Note: This is applicable for CSMA/CD and Token Bus).
Adding Concentrator:
 Click on the Concentrator icon in the tool bar and click it onto the environment. By
default a Concentrator consists of 24 ports. (Note: This is applicable for Token Ring).
Set Node Properties
Right Click on the appropriate node and select Properties.
Set the Properties for the devices and links

Right click over the devices and then select Properties to set the properties of the links and
the devices.
55
3.2.4 Modifying/Viewing/Accepting Properties
On opening an already configured properties of an application the input fields will be frozen
(i.e. the input cannot be changed).To modify these values click on the Modify button in the
screen. Now the input value can be changed. Click on the Accept button, the modified values
will be saved.
This View button is enabled once the Accept Button is clicked. To view the given values,
click on the View button.
3.2.5 Enable Packet Trace (Optional)
Click Packet Trace icon in the tool bar. To get detailed help, please refer section
6.5respectively. Select Dynamic Metrics icon for enabling Dynamic Metrics and click OK.
56
3.3 Advanced wireless networks – MANET & Wi-Max
In the Simulation menu select  New 

Advanced Wireless Networks
For example, to arrive MANET,
Advanced Wireless Networks
MANET

Adding Wireless Node (Note: This is applicable for MANET)
 Click on the Node icon in the tool bar, select Wireless Node and click
and drop it inside the grid. One must be aware that TCP is disabled by
default. (Note: A Node cannot be placed on another Node. A Node
cannot float outside of the grid.)
Adding Base Station and Subscriber (Note: This is applicable for Wi-
MAX)
 Click on the Base Station icon in the tool bar and click it onto the
environment.
 Click on the Wi-Max Subscriber icon after clicking Node icon in the
tool bar. Click and drop it onto the environment.
For MANET and Wi-Max
parameters according to the requirements.
o In case of Wi-Max, Routing Protocol in Application Layer of router and all user
editable properties in DataLink Layer and Physical Layer of Access Point and
Wireless Node are Global i.e. changing properties in one node will automatically
reflect in the others in that network.
57
o In case of MANET, in Wireless Node, Routing Protocol in Network Layer and all
user editable properties in DataLink Layer, Physical Layer and Power are Global
i.e. changing properties in one node will automatically reflect in the others in that
network.

On opening an already configured properties of environment, the input fields will be frozen
will be saved.
58

installed Path>\Docs\ Sample_Configuration\ MANET\ <Protocol>, which the user can open
using NetSim and understand how devices are connected among themselves for that network
and their default properties.
59
Note on MANET implementation in NetSim:
 If user wants to implement HTTP application among Nodes, TCP must be enabled in
Source Node as TCP is set to disable by default.
 OLSR is a proactive link-state routing protocol, which uses hello and topology control
(TC) messages to discover and then disseminate link state information throughout the
mobile ad hoc network. Individual nodes use this topology information to compute
next hop destinations for all nodes in the network using shortest hop forwarding paths.
For topology control (TC) messages to disseminate throughout, it requires 5 or more
seconds depending upon the network size. In general, it is (5.5 secs + Tx_Time *
network size). Hence an application must start at least 6-7 seconds after the network
commences and it can be done by setting the “Starting time” parameter in
Application.
3.3.8 Link Layer Acknowledgements and Network Layer

Acknowledgements in DSR
Route Maintenance is the mechanism by which a source node S is able to detect, while
using a source route to some destination node D, if the network topology has changed such
that it can no longer use its route to D because a link along the route no longer works.
Using Link-Layer Acknowledgements
If the MAC protocol in use provides feedback as to the successful delivery of a data packet
(such as is provided for unicast packets by the link-layer acknowledgement frame defined by
IEEE 802.11), then the use of the DSR Acknowledgement Request and Acknowledgement
options is not necessary. If such link-layer feedback is available, it SHOULD be used instead
of any other acknowledgement mechanism for Route Maintenance, and the node SHOULD
NOT use either passive acknowledgements or network-layer acknowledgements for Route
Maintenance.
60
When using link-layer acknowledgements for Route Maintenance, the retransmission
timing and the timing at which retransmission attempts are scheduled are generally controlled
by the particular link layer implementation in use in the network. For example, in IEEE
802.11, the link-layer acknowledgement is returned after a unicast packet as a part of the
basic access method of the IEEE 802.11 Distributed Coordination Function (DCF) MAC
protocol; the time at which the acknowledgement is expected to arrive and the time at which
the next retransmission attempt (if necessary) will occur are controlled by the MAC protocol
implementation.
Using Network-Layer Acknowledgements
When a node originates or forwards a packet and has no other mechanism of

acknowledgement available to determine reachability of the next-hop node in the source route
for Route Maintenance, that node SHOULD request a network-layer acknowledgement from
that next- hop node. To do so, the node inserts an Acknowledgement Request option in the
DSR Options header in the packet. The Identification field in that Acknowledgement
Request option MUST be set to a value unique over all packets recently transmitted by this
node to the same next-hop node.
When using network-layer acknowledgements for Route Maintenance, a node SHOULD

use an adaptive algorithm in determining the retransmission timeout for each transmission
attempt of an acknowledgement request. For example, a node SHOULD maintain a separate
round-trip time (RTT) estimate for each node to which it has recently attempted to transmit
packets, and it SHOULD use this RTT estimate in setting the timeout for each retransmission
attempt for Route Maintenance.
61
3.4 Advanced wireless networks – VANET
 In the Simulation menu select 

New  Advanced Wireless
Networks VANET
 In the dialogue box that appears,
browse to the Sumo Configuration
File.

After selecting the Sumo configuration file name, the scenario is opened,
with nodes placed at their respective starting positions (tracked form Sumo).
Roads and Traffic Lights are also placed exactly as present in SUMO
Configuration file.
 Routing Protocol in Network Layer and all user editable properties in Data Link Layer,
Physical Layer and Power are Global
 Mobility Model is set to SUMO and it is non-Editable. This signifies that the Node
movements will be traced from SUMO
 File name gives the path to Sumo Configuration file that was given by the user.
 Step Size is taken from the Sumo Configuration file specified.
62

will be saved.
3.4.5 Enable Packet Trace, Event Trace(Optional)
section 6.5 and 6.6 respectively.
63

installed Path>\Docs\ Sample_Configuration\ VANET\ <Protocol>, which the user can open
using NetSim and understand how devices are connected among themselves for that network
and their default properties.
Some Sample Sumo Examples are also present in the same folder specified above. The user
can run the Configuration file using sumo installed in C drive.
Simulation Time is set from the Configuration File of Sumo. The simulation has three
options
 Record only - which runs Sumo in background. Users can view animation after
completion of Simulation.
 Record and Play – Opens Netsim GUI and Sumo GUI in parallel
 Don‟t record – runs Sumo in Backend. Animation is not recorded
64
3.5 BGP
In the Simulation menu select Simulation  New 

BGP Networks
Adding Border Router:

 Click and drop the Border Router icon from the tool bar. (Note: Maximum you can
have 3 Autonomous systems in a single scenario.)
Adding Internal Router:

 Click on the Internal Router icon in the tool bar and drop the Internal Router onto the
Autonomous systems created. By default a Router has eight ports.
Establishing Connections
The steps for connecting devices in BGP networks are as follows,
 The connections between two wired nodes cannot be made in the network.
 The connection possibilities are
 Wired Node to Internal Router
 Internal Router to Border Router
 Border Router to Border Router
Point and Wireless Node are Global i.e. changing properties in one node will
automatically reflect in the others in that network.
65
On opening an already configured properties of an application the input fields will be frozen
will be saved.
This View button is enabled once the Accept Button is clicked. To view the given values,
click on the View button.
66

installed Path>\Docs\ Sample_Configuration\ BGP, which the user can open using NetSim
and understand how devices are connected among themselves for that network and their
default properties.
67
3.6 Cellular Networks – GSM/CDMA

Cellular Networks
For Example, to arrive CDMA
Cellular Networks  CDMA
Adding Base Transceiver Station (BTS) - Click on the BTS icon in the toolbar and click it
onto the environment.
Adding Mobile Switching Centre (MSC) - Click and drop MSC in the environment.
Adding Mobile Station (MS) -
 Click on the Mobile Station icon in the tool bar, click and drop it on the Base Station
coverage area.
 Mobile Station cannot be placed on another Mobile Station. It has to be clicked and
placed on the Base Station coverage area.
68

69

installed Path>\Docs\ Sample_Configuration\ Cellular\ <Cellular Technology>, which the
user can open using NetSim and understand how devices are connected among themselves
for that network and their default properties.
70
3.7 Wireless Sensor Network
In the Simulation menu select Simulation 
New  Wireless Sensor Networks

Adding Sink Node- Click on the Sink Node icon in the toolbar and click and drop inside the
grid.
Adding Sensor - Click on the Sensor Node icon in the toolbar and click and drop inside the
grid.
Adding Agent- Click on the Agent icon in the toolbar and click and drop inside the grid.
parameters according to the requirements. In Sensor Node, Routing Protocol in Network
Layer and all user editable properties in DataLink Layer, Physical Layer and Power are
Global i.e. changing properties in one node will automatically reflect in the others in that
network.
71

installed Path>\Docs\ Sample_Configuration\WSN, which the user can open using NetSim
default properties.
3.7.7 SINR, BER and Propagation models for 802.15.4
SINR Calculation:
the power of a certain signal of interest divided by the sum of the interference power (from
all the other interfering signals) and the power of some background noise.
P (in dBm) =
where Δf is the Bandwidth in Hertz. For 802.15.4, Δf = 2 MHz
( )
P (in mW) =
72
Therefore, SINR in dBm is calculated as:
SINR (in dBm) = ( )
Bit Error Rate (BER) Calculation:
bits during a studied time interval. The BER results were obtained using the analytical model
from IEEE standard 802.15.2-2003 [B9]. The calculation follows the approach outlined in
5.3.2 of that standard.
( ( ))
BER = ( ) ( ) ∑ ( )
Where SINR = Signal-to-Interference-plus-Noise Ratio. BER should be between 0 and 1.
Propagation Loss:
Shadowing:
between a transmitter and a receiver. In the model with shadowing, the shadowing value Xσ,
typically defined in dB, is added to (or subtracted from) the average received power. Xσ is a
zero means Gaussian distributed random variable with standard deviation σ.
The Probability Density Function (PDF) of the lognormal distribution is:
The default value for standard deviation is chosen as 5 dB.
73
Path Loss:
Path loss is the reduction in power density of an electromagnetic wave as it propagates

through space. Path loss may be due to many effects, such as free-space loss, refraction,
diffraction, reflection, aperture-medium coupling loss, and absorption.
of 2 to 4, where 2 is for propagation in free space and 4 is for relatively loss environments. In
NetSim, the default value for path loss exponent is taken as 2.
using the formula
Where L is the path loss in decibels, is the path loss exponent, d is the distance between the
transmitter and the receiver, usually measured in meters, and C is a constant which accounts
for system losses.
L (in dBm) = ( )
Calculation of Received Power:
In general,
( ) ( ) ( ) ( ) ( )
The path loss model used is described in IEEE Standard 802.15.2-2003[B9], which stipulates
a two-segment function with a path loss exponent of 2.0 for the first 8 m and then a path loss
exponent of 3.3 thereafter. The formula given in IEEE Standard 802.15.2 is shown in
Equation (E.1).
74
pl(d) = {
( )
Where, for 2.4 Ghz,

pl(1) = 40.2 dBm
pl(8) = 58.5 dBm
= 2, the path loss exponent for d ≤ 8m
= 3.3, the path loss exponent for d > 8m
Reference: IEEE Standard 802.15.4 – 2006 Part 15.4: Wireless Medium Access Control
(MAC) and Physical Layer (PHY) Specifications for Low-Rate Wireless Personal Area
Networks (WPANs).
75
3.8 Internet of Things

In the Simulation menu select Simulation 
New  Internet of Things
3.8.2 Introduction
Internet of Things (IoT) is an ecosystem of connected physical objects that are accessible
through the internet. It is the network of physical objects that can communicate, sense or
interact with their internal states or the external environment.
The „thing‟ in IoT could be a person with a heart monitor or an automobile with built-in-
sensors, i.e. objects that have been assigned an IP address and have the ability to collect and
transfer data over a network without manual assistance or intervention.
NetSim IOT is modeled as a wireless sensor network that can connect to the internet via a
6LoPAN Gateway. The default protocols in the WSN section is AODV with IPv6 addressing
in L3 and 802.15.4 MAC & PHY. This WSN sends data to a LowPAN Gateway which has a
Zigbee (802.15.4) interface and a WAN Interface. The Zigbee interface allows wireless
connectivity to the WSN while the WAN interface connects to the internet.
Any WSN comprises of two parts, the sensing part and the network communication part.
NetSim is "agnostic" to the sensing and this sensing is abstracted as an Agent (sometime
known as Agent based modeling). Whatever is sensed is finally converted to a "packet" and it
is from this point on that NetSim simulation can be used.
NetSim does not provide any connectivity / interfacing to real hardware / sensors. However,
NetSim provides interfacing to MATLAB or via text files. In case of text files, real sensors
can write their data to files which can then take as input by NetSim.
76
Total Grid Length (m) settings allows the user to set the
total environment length of IOT Networks containing
sensors, LoWPAN gateway, wired nodes, routers,
switches, access point, wireless nodes.
Sensor Grid Settings (m) allows the user to set the
environment length for placing the sensors uniformly or
randomly. Users can manually create the scenario by
selecting “Via click and drop”, or place the sensors
automatically in an uniform or random manner.
Adding Sensor - Click on Sensor Node icon in toolbar and click and drop inside the grid.
Adding LoWPAN gateway- LoWPAN is an acronym of Low power Wireless Personal Area
Networks. The LoWPAN IoT gateway functions as a border router in a LoWPAN network,
connecting a wireless IPv6 network to the Internet. Designed to send IPv6 packets over
IEEE802.15.4-based networks and implementing open IP standards including TCP, UDP,
HTTP and more, the standard offers end-to-end addressable nodes, allowing a router to
connect the network to IP.
Click on the LoWPAN gateway icon in the toolbar and click and drop inside the grid.
Users can also add devices as shown in Internetworks scenario.
 User need not connect the sensors with LoWPAN gateway using wireless links.
 Interconnection among other devices is same as in Internetworks.
 LoWPAN gateway can be connected with router using wired links.
o Routing Protocol in Application Layer of router and all user editable properties in
DataLink Layer and Physical Layer of Access Point and Wireless Node are
Global i.e. changing properties in one node will automatically reflect in the
others in that network.
77
o In Sensor Node, Routing Protocol in Network Layer and all user editable properties
in DataLink Layer, Physical Layer and Power are Global i.e. changing properties
in one node will automatically reflect in the others in that network.
78
3.8.5 Enable Packet Trace, Event Trace & Dynamic Metrics(Optional)

installed Path>\Docs\ Sample_Configuration\ IOT, which the user can open using NetSim
default properties.
79
3.9 Zigbee
In the Simulation menu select Simulation

 New  ZigBee Networks
Adding Node -
 Click on the ZigBee icon in the toolbar and click and drop it inside the grid (i.e.
Visibility Range - The systems can move and communicate in this range only).
 A Node cannot be placed on another Node. A Node cannot float outside the grid.
Adding PAN Coordinator - Click on the PAN Coordinator icon in the toolbar and click
and drop inside the grid.
Set Environment Properties
Right click in side of the on the Environment and click Properties.
will be saved.
parameters according to the requirements. In Zigbee Node, Routing Protocol in Network
network.
80
81

installed Path>\Docs\ Sample_Configuration\ Zigbee, which the user can open using NetSim
default properties.
3.9.8 SINR, BER and Propagation models for 802.15.4
SINR Calculation:
the power of a certain signal of interest divided by the sum of the interferencepower (from all
the other interfering signals) and the power of some background noise.
P (in dBm) =
where Δf is the Bandwidth in Hertz. For 802.15.4, Δf = 2 MHz
82
( )
P (in mW) =
Therefore, SINR in dBm is calculated as:
SINR (in dBm) = ( )
Bit Error Rate (BER) Calculation:
bits during a studied time interval. The BER results were obtained using the analytical model
from IEEE standard 802.15.2-2003 [B9]. The calculation follows the approach outlined in
5.3.2 of that standard.
( ( ))
BER = ( ) ( ) ∑ ( )
Where SINR = Signal-to-Interference-plus-Noise Ratio. BER should be between 0 and 1.
Propagation Loss:
Shadowing:
between a transmitter and a receiver. In the model with shadowing, the shadowing value Xσ,
typically defined in dB, is added to (or subtracted from) the average received power. Xσ is a
zero means Gaussian distributed random variable with standard deviation σ.
The Probability Density Function (PDF) of the lognormal distribution is:
The default value for standard deviation is chosen as 5 dB.
83
Path Loss:
Pathloss is the reduction in power density of an electromagnetic wave as it propagates

through space. Path loss may be due to many effects, such as free-space loss, refraction,
diffraction, reflection, aperture-medium coupling loss, and absorption.
of 2 to 4, where 2 is for propagation in free space and 4 is for relatively loss environments. In
NetSim, the default value for path loss exponent is taken as 2.
using the formula
Where L is the path loss in decibels, is the path loss exponent, d is the distance between the
transmitter and the receiver, usually measured in meters, and C is a constant which accounts
for system losses.
L (in dBm) = ( )
Calculation of Received Power:
In general,
( ) ( ) ( ) ( ) ( )
The path loss model used is described in IEEE Standard 802.15.2-2003[B9], which stipulates
a two-segment function with a path loss exponent of 2.0 for the first 8 m and then a path loss
exponent of 3.3 thereafter. The formula given in IEEE Standard 802.15.2 is shown in
Equation (E.1).
84
pl(d) = {
( )
Where, for 2.4 Ghz

pl(1) = 40.2 dBm
pl(8) = 58.5 dBm
= 2, the path loss exponent for d ≤ 8m
= 3.3, the path loss exponent for d > 8m
Reference: IEEE Standard 802.15.4 – 2006
Part 15.4: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications
for Low-Rate Wireless Personal Area Networks (WPANs).
85
3.10 Cognitive Radio
Cognitive Radio Network simulation is available
from v7 of NetSim. Cognitive Radio Networks
allows you to connect, if required, with Ethernet,
Wireless LAN, IP Routing, TCP / UDP and
allows users to log packet and event (in NetSim
standard version only) traces.
In the Simulation menu select  New  Cognitive Radio Networks.
Adding Devices –
 Cognitive Radio Networks comes with the palette of various devices like Cognitive Radio
CPE, Cognitive Radio Base Station, Switch, Router, Wired Node, Wireless Node, Access
point, Incumbent etc.
 Select the desired devices in the toolbar and click and drop on the environment.
 To remove devices, right click on the particular device and then click Remove.
Connect the devices
Select the appropriate link in the toolbar and connect the devices by clicking on the device 1
and device 2.
automatically reflect in the others in that network.
86
3.10.4 Enable Packet Trace, Event Trace & Dynamic Metrics

(Optional)
87
Click on Run Simulation icon on the top toolbar. Set the Simulation Time and click on
Simulate.

installed Path>\Docs\ Sample_Configuration\ CognitiveRadio, which the user can open using
NetSim and understand how devices are connected among themselves for that network and
their default properties.
in “Understanding Configuration.xml file” under “Running NetSim via CLI” chapter.
Notes on Cognitive Radio implementation in NetSim:
 CR BS allocates max one symbol per CPE. If the generation rate is more than the data
filled in one symbol then allocation fails and it results in zero throughput.
 The first symbol is reserved for CR control frames or any broadcast PDU
 Operational frequency: It is the frequency band at which the incumbent operates. It
ranges from 54 MHz to 862 MHz.
 Operational interval(s): It is the time gap between two successive incumbent
operations. It ranges from 0-10.
 Operational time(s): It is the active period of the incumbent. i.e. If the operational
interval is set to 5s, then incumbent operates with an interval of every 5s. If the
operational interval is set to 0s, then the incumbent remains active.
88
For Operational Time(s) = 4, Operational interval=9
The timing diagram is as follows:
Incumbent --- 0s to 10s (OFF), 10s to 14s (ON), 14s to 24s (OFF), 24s to 28s (ON) ... and
so on.
 NetSim gives App layer throughput which is lesser than that of MAC layer
throughput because of
 TCP connection establishment
 ARP set-up
 Service flow creation CPE-BS and BS-CPE
 BW request
 To avoid the above effects

 Generate custom traffic
 Set DL/UL Ratio as 1:1 so that the BS transmits whatever it receives
 Run UDP in transport layer
 Use static ARP
 Run Simulation for more than 100 sec
89
3.11 LTE/LTE-A
In the Simulation menu selectNew

LTE/LTE-A Networks.
Adding MME- Click on the Router icon in the tool bar, click and drop the MME (Mobility
Management Entity) onto the environment.
Adding ENB - Click on the Evolved node B (ENB) icon in the toolbar and click it onto the
environment.
Adding Relay - Click on the Relay icon in the toolbar and click it onto the environment.
Adding UE –
 Click on the UE (User Equipment) icon from the Node icon in the toolbar, click and
drop it on the ENB coverage area.
 UE cannot be placed on another UE. It has to be clicked and placed on the ENB node
coverage area.
Connect the devices
Select the appropriate link in the toolbar and connect the devices by clicking on the device 1
and device 2.
automatically reflect in the others in that network. Transmission Mode Index of ENB,
Relay and UE are also global properties.
90
91

installed Path>\Docs\ Sample_Configuration\ LTE, which the user can open using NetSim
default properties.
3.11.7 Physical speed of the LTE Air Interface

The theoretical calculation for the LTE Air Interface is as follows
One Resource block can have 12 subcarriers (each carrier is 15 kHz) in frequency domain
and 0.5ms (7 symbols) in time domain.
12 subcarriers = 180 kHz
7 symbols = 0.5ms
92
Thus, total number of symbols per resource block = 12 * 7 = 84
Each symbol can accommodate certain number of bits based on the modulation scheme as per
the table below
Modulation scheme Bits per symbol

QPSK 2
16-QAM 4
64-QAM 6
The table below shows the number of resource blocks available for different LTE channel
bandwidths.
Channel Bandwidth 5 10 15 20
(MHz)
Resource Blocks 25 50 75 100
(RB)
No. of subcarriers 300 600 900 1200
(RB*12)
Occupied bandwidth 4.5 9 13.5 18
(MHz)
Note: In LTE 10% of total bandwidth is used for guard band. For example if the channel
bandwidth is 20MHz, then 2MHz is used for guard band. Thus, if 180 kHz has 1 RB, 18 MHz
will have 100 RBs
Given below is the calculation for PHY rate:
In LTE for 20MHz, there are 100 Resource blocks and each Resource block has 12*7 = 84
symbols
Example: PHY rate calculation for 20MHz band, using 64-QAM and 4*4 Tx Rx antennae
 For 20 MHz there are 100 Resource blocks

 Each resource block has 12*7 = 84 symbols
 100 resource blocks have 8400 symbols
 1 sub frame = 1 ms = 2 time slots
 16800 symbols per subframe (or per ms)
 64-QAM can transmit 6 bits per symbol
 1 subframe using 64-QAM modulation can transmit 100800 bits/ms
93
 100.8*10^6 bits per second or 100.6 Mbps
 This is for a 1*1 Tx Rx antenna and for 4*4 Tx Rx antennae 100.8*4 = 403.2 Mbps
The above note explains the theoretical method of calculating the LTE PHY Data rate, where
there are no channel (propagation) losses.
However in the real world there is signal attenuation due to propagation losses. Thus the
calculation for PHY Data rate in NetSim is based on the Transport Block Size which is
specified in the standard. This calculation is as follows
i. Any signal received at the receiver has a SNR (signal to noise ratio).
ii. Based on the SNR a CQI value is calculated.
iii. The SNR - CQI Table is available in LTE.h in NetSim and is per the LTE
standard
iv. Based on the SNR and the CQI an MCS value is calculated
v. The SNR CQI MCS table is available in LTE.h in NetSim and is per the LTE
standard
vi. Based on the MCS the TBS Index is calculated, again from a table available in
LTE.h which is per the LTE Standard
vii. Based on the TBS Index the TBS Table is looked up and the transport block
size is retrieved.
Approximately 25% of overhead is used for controlling and signalling. Effective PHY data
rate is 300 Mbps
94
3.12 Military Radio – TDMA link 16

Select  New  Advanced Wireless Networks
 MANET
Click on the Node icon in the Toolbar, and then click on Wireless Node.
Next, click on the environment where you want to drop it inside the grid.
(Note: A Node cannot be placed on another Node. A Node cannot float
outside of the grid.)
3.12.3 Set Node Properties
 Right click on the appropriate node to select Properties.
 In Interface1_Wireless, go to DATALINK_LAYER and PHYSICAL_LAYER section

and change the Protocol to TDMA. In Wireless Node, Routing Protocol in Network
network.
95
 In Interface1_Wireless properties, under network layer, Link layer ack should be
selected as “Network LayerAck” .
3.12.4 Set Environment Properties
 Right click anywhere on the Environment Grid and select Properties.

 Select the Channel Characteristics and set the parameters accordingly.

will be saved.
96
3.12.6 Set Application Properties
97
(Optional)

installed Path>\Docs\ Sample_Configuration\ TDMA, which the user can open using NetSim
default properties.
98
3.13 Military Radio – DTDMA
(Note: DTDMA is featured as part of the MAC and PHY layer of MANET radios)

Select  New  Advanced Wireless Networks
 MANET

Click on the Node icon in the Toolbar, and then click on Wireless Node.
Next, click on the environment where you want to drop it inside the grid.
(Note: A Node cannot be placed on another Node. A Node cannot float
outside of the grid.)
3.13.3 Set Node Properties
 Right click on the appropriate node to select Properties.
 In Interface1_Wireless, go to DATALINK_LAYER and PHYSICAL_LAYER section

and change the Protocol to DTDMA.
99
 Note that in a Wireless Node, Routing Protocol in Network Layer and all user editable
properties in DataLink Layer / Physical Layer / Power model are Global i.e. changing
properties in one node will automatically reflect in the others in that network.
In the Datalink Layer/Physical Layer, we can select the DTDMA protocol as shown in figure
below.
100
Furthermore, in Physical layer, we can select the frequency bands (HF/VHF/UHF). Users
can modify the lower frequency range and the Bandwidth. The sum of the Lower frequency
and Bandwidth gives the Upper frequency. Users can also select the modulation techniques
such as QPSK/16-QAM/64-QAM and, an option to turn ON/OFF frequency hopping is also
provided.
3.13.4 Set Environment Properties
 Right click anywhere on the Environment Grid and select Properties.

 Select the Channel Characteristics and set the parameters accordingly.

will be saved.
3.13.6 Set Application Properties
101

(Optional)
102

installed Path>\Docs\ Sample_Configuration\ DTDMA, which the user can open using
NetSim and understand how devices are connected among themselves for that network and
their default properties.
3.13.10 DTDMA Packet size
It is important to set packet size (of any application running over DTDMA) to be lower than
the Max packet Size setting indicated below. If the packet size exceeds the Max Packet Size
setting then DTDMA would not be able to transmit that packet.
Maximum Packet size (bytes) =
By default,
Bits per slot (bits) – 3000, Overhead per slot (bits) - 600
Users can also edit the values of Bits per slot and Overhead per slot in the GUI.
103
Assuming default values are chosen for Bits per slot and Overhead per slot, DTDMA packet
size is calculated for different protocols as shown below:
i. For DSR protocol (if TCP is enabled),

DSR overhead (one hop) - 12 bytes which is added with Network layer overheads,
plus IP overhead of 20 plus TCP Overhead of 20, totaling 52 bytes (416 bits).
Max Packet size (bytes) = = 248 bytes
ii. For DSR protocol (if UDP is enabled),

DSR overhead (one hop) - 12 bytes which is added with Network layer overheads,
plus IP overhead of 20 plus UDP Overhead of 8, totaling 40 bytes (320 bits).
iii. For AODV,ZRP,OLSR protocol (if TCP is enabled),

Here AODV, ZRP, OLSR overhead – 0 (no overhead is added) plus IP overhead of 20
plus TCP Overhead of 20, totaling 40 bytes (320 bits)
iv. For AODV,ZRP,OLSR protocol (if UDP is enabled),

Here AODV, ZRP, OLSR overhead – 0 (no overhead is added) plus IP overhead of 20
plus UDP Overhead of 8, totaling 40 bytes (224 bits)
3.13.11 Node Join / Leave
Node join(s) - It is the time at which the node join the network and accesses the
communication channel.
Node leave (s) – It is the time at which the node leaves the network.
104
Dynamic metrics will be shown only for the period in which the node is present in the
network. For example, if node join = 0, node leave = 5, even if the simulation time =
100s, the dynamic metrics will be shown only for 5s.
Use case:
Fields can take multiple inputs separated by comma as shown below:
Node join - 0, 10
Node leave - 5, 100
In this case, the node joins the network at 0s and leaves at 5s and the node joins the
network again at 10s and leaves at 100s.
105
4 Traffic generator in NetSim
(Application Models)
NetSim allows users to model and simulate the applications:
1. CBR
2. Custom
3. Database
4. FTP
5. Email
6. HTTP
7. PEER_TO_PEER
8. Video
9. Voice
10. Sensor App
11. Erlang Call
12. Emulator (Only if Emulator Add-on is present)
To set up the application click and drop the application icon from the tool bar as shown
below.
Right click on the application icon and select properties
This properties window allows you to set the traffic. You can add (or) delete one or more
applications.
106
4.1 Common properties for all the traffic types
Application ID
This property represents the unique identification number of the application.
Start time
This property represents the start time of the application in seconds.
End time
This property represent the end time of the application in seconds.
Note: Suppose Start time is 1 and end time is 10 then application starts generating traffic
at 1st second and ends at 10th second.
Source Count
This property represents number of sources for the application. Voice, Video, FTP,
Database and Custom applications have only one source.
Source ID
This property represents the unique identification number of the source.
Destination Count
This property represents number of destinations for the application. Voice, Video,
FTP, Database and Custom applications have only one destination.
Destination ID
This property represents the unique identification numbers of the destination. And to
model, Broadcast application users can select „0‟ as the Destination ID.
4.2 CBR
Packet Size
Distribution: The options available for distribution is
 Constant
Packet Size (Bytes): Sets the size of the packets being generated by the chosen
distribution. By default 1460 bytes is entered.
107
Inter Arrival Time
This indicates the time gap between packets.
 Constant
Inter Arrival Time: Enter the average inter-arrival time between packets. A lower inter-
arrival time would lead to a higher generation rate and vice versa. By default 20000
Micro Sec is entered.
4.3 Custom
Packet Size
Distribution: The options available for distribution are,
 Constant
 Exponential
Inter Arrival Time
 Constant
 Exponential
4.4 Voice
Codec
Codec is the component of any voice system that translates between analog speech and
the bits used to transmit them. Every codec transmits a burst of data in a packet that can
be reconstructed into voice.
108
Five different standards of voice codec‟s are given which can be selected depending on
the variations required. Packet size and Inter-arrival time value will vary depending on
the codec value chosen.
Packet Size
 Constant
 Exponential
Inter Arrival Time
 Constant
 Exponential
Service Type
 CBR - CBR stands for Constant Bit Rate. Packets of constant size are generated at
constant inter arrival times.
 VBR - VBR stands for Variable Bit Rate. The two types of Suppression Model that
can be selected are,
 Deterministic
 Markov Chain
4.5 Video
Video is an electronic medium for the recording, copying and broadcasting of moving
visual images.
109
Model Type
 Continuous Normal VBR – This model is the simplest of all models. It uses Normal
Distribution for the generation of bits per pixel. In this model, consecutive packet
sizes are independent of each other.
o Frames per second – Number of frames arriving per second. This is in the
range of 10 – 50.
o Pixels per frame -Number of pixelsin each frame. This is in the range of
10000 – 100000.
o Bits per pixel (µ)– Mean value of the normal distribution used to generate the
value of bits per pixel.
o Bits per pixel (Σ) – Standard Deviation of the normal distribution used to
generate the value of bits per pixel.
 Continuous State Autoregressive Markov –This model incorporates the

autocorrelation between the frames. Also, current packet size depends on the previous
packet size via the first order autoregressive Markov process.
range of 10 – 50.
o Pixels per frame - Number of pixels in each frame. This is in the range of
10000 – 100000.
o Constant A– First order autoregressive Markov processλ(n) can be generated
by the recursive relation λ(n)=aλ(n-1)+bw(n).
o Constant B– First order autoregressive Markov process λ(n) can be generated
by the recursive relation λ(n)=a λ(n-1)+bw(n).
o Eta– The steady-state average E(λ)and discreet auto covariance C(n) are given
by E(λ) = ( b / (1-a) ) η C(n)=(b2/(1-a2))an where η is the Gaussian parameter.
 Quantized State Continuous Time Markov –In this model the bit rate is quantized
into finite discrete levels. This model takes uniform quantization step as A bits/pixel.
There are M + 1 possible levels (0, A, ….., MA).Transitions between levels are
assumed to occur with exponential rates that may depend on the current level. This
model is approximating the bit rate by a continuous time process λ(t) with discrete
jumps at random Poisson time.
110
range of 10 – 50.
o Pixels per frame - Number of pixels in each frame. This is in the range of
10000 – 100000.
o No of Multiplexed Sources– This model considers the aggregate
instantaneous input rate λN(t) instead of the single source bit rate λ(t). The
total rate is the sum of N independent random processes each with mean E(λ)
and variance C(0) at steady state. Therefore, the steady state- mean of λN(t)
will be E(λ N)=N x E(λ) bits/pixel.
o Quantization Level– This model takes uniform quantization step as A
bits/pixel. There are M + 1 possible levels (0, A, ….., MA). Transitions
between levels are assumed to occur with exponential rates that may depend
on the current level.
 Simple IPB Composite Model–In this model, the frames are organized as
IBBPBBPBBPBBIBBPBB… i.e., 12 frames in a Group of Pictures(GOP).Generate
X0 from a Gaussian distribution N(0, y 0).Set initial value N0= 0, D0 = 1.
For k = 1, 2,…, N-1, calculate Φkj , j = 1, 2,…,k iteratively using the following
formulae
Nk = r(k) – j=1Σk-1Φk-1,j r(k-j)
Dk = Dk-1 –(N2k-1/Dk-1)
Φkk = Nk / Dk
Φkj = Φk-1, j-ΦkkΦk-1,k-j j=1,….,k-1
mk = j = 1ΣkΦkjXk-j
y k = (1- Φ2kk) yk-1
Finally, each Xk is chosen from N(mk, y k). Thus we get a process X with ACF
approximating to r(k).
The auto correlation function can be calculated in a recursive way as follows:
r(0) = 1, r(k+1) = ((k+d)/(k+1))r(k)
Where d= H-0.5.
111
H is called the Hurst parameter k-β is used as the ACF of a self-similar process.We
get the value of H parameter for a self-similar process using the relationship,
Β = 2 – 2H
Distribution of these data is Gaussian. For data to be Beta distributed, the following
mapping is being used.
Yk = F-1β (FN(Xk)), k>0
Xk :Self-similar Gaussian process,
FN :The cumulative probability of normal distribution,
F-1β: The inverse cumulative probability functions of the Beta model.
range of 10 – 50.
o Hurst I–Refer i-button help of Simple IPB Composite Model.
o Hurst B– Refer i-button help of Simple IPB Composite Model.
o Hurst P– Refer i-button help of Simple IPB Composite Model.
o Gamma I – Refer i-button help of Simple IPB Composite Model.
o Gamma B– Refer i-button help of Simple IPB Composite Model.
o Gamma P– Refer i-button help of Simple IPB Composite Model.
o Eta I – Refer i-button help of Simple IPB Composite Model.
o Eta B – Refer i-button help of Simple IPB Composite Model.
o Eta P– Refer i-button help of Simple IPB Composite Model.
4.6 FTP
File Size
 Constant
 Exponential
File Size (Bytes): Sets the size of the packets being generated by the chosen distribution.
By default 100000 bytes is entered.
NOTE: Devices must have TCP enabled in Transport layer for implementing FTP application
successfully.
112
File_Inter Arrival Time
 Constant
 Exponential
arrival time would lead to a higher generation rate and vice versa. By default 5 Sec is
entered.
4.7 Database
Transaction Size
 Constant
 Exponential
Packet_Size (Bytes): Sets the size of the packets being generated by the chosen
Transaction Inter Arrival Time
 Constant
 Exponential
4.8 Peer to Peer

A pure peer-to-peer network does not have the notion of clients or servers but only
equal peer nodes that simultaneously functioning as both "clients" and "servers" to the other
nodes on the network.
113
NOTE: Devices must have TCP enabled in Transport layer for implementing peer to peer application
successfully.
File Size
 Constant
 Exponential
Value (Bytes): This represents the size of the file in bytes.
Piece size (Bytes): Each file is divided into equal sized pieces and then the piece of the
data is transmitted. This property represents the size of each piece.
4.9 HTTP
HTTP (Hyper Text Transfer Protocol) is a protocol that utilizes TCP to transfer its
information between computers (usually Web servers and clients). Hence in NetSim, it is
imperative that TCP is enabled in the Source Node.
Http_request_interarrival_time
This indicates the time gap between the pages.
 Constant
 Exponential
Inter Arrival Time (micro sec): This represents the rate at which client sends the
requests.
Page_property
 Constant
 Exponential
Page Count: This represents the number of pages received from the server.
Page Size (Bytes): This represents the size of each page that is received from the server.
114
4.10 Email
Email_Receive
This represents the rate at which emails are received.
Duration_Distribution: The options available for distribution are,
 Constant
 Exponential
Duration: Time gap between two successive receiving emails in seconds.
Email_Size_Distribution: The options available for distribution are,
 Constant
 Exponential
Email_Size: It represents the size of the email that is received.
Email_Send
This represents the rate at which emails are sent.
Duration_Distribution: The options available for distribution are,
 Constant
 Exponential
Duration: Time gap between two successive sending emails in seconds.
Email_Size_Distribution: The options available for distribution are,
 Constant
 Exponential
Email_Size: It represents the size of the email that is sent.
4.11 Sensor App

Packet Size
 Constant
 Exponential
115
Inter Arrival Time
 Constant
 Exponential
4.12 Erlang Call
Packet Size
 Constant
Inter Arrival Time
 Constant
Call
Duration Distribution: The options available for distribution are,
 Constant
116
 Exponential
Duration: The options available
Inter Arrival Time: Enter the average inter-arrival time between calls. A lower inter-
arrival time would lead to a higher call rate and vice versa. By default 60 Sec is entered.
IAT Distribution: The options available for distribution are,
 Constant
 Exponential
Constant
Service
Service Type
 CBR - CBR stands for Constant Bit Rate. Packets of constant size are generated at
constant inter arrival times.
 VBR - VBR stands for Variable Bit Rate. The two types of Suppression Model that
can be selected are,
 Deterministic
 Markov Chain
Success ratio: Sets the ratio of the packets that are not silenced during VBR calls.
4.13 Emulator
NOTE- Will be present only when Emulator Add-on is installed
Emulation
Source Real IP: Specifies the real IP Address of source device in Emulation
Source Port: Specifies the Port no used for transmission by Application running in
source device
Destination Real IP: Specifies the real IP Address of destination device in Emulation
Destination Port: Specifies the Port no used for reception by Application running in
destination device
117
4.14 Priority and QoS of Applications
The various traffics generated in NetSim have the following priority and QoS values:
Application Type Priority Value Priority QoS Class

Voice – One way 8 High RTPS
Voice – Two way 8 High UGS
Video 6 Medium nRTPS
FTP 2 Low BE
Database 2 Low BE
Custom 2 Low BE
Note: Priority of “Normal” has a Priority Value of 4 and “nRTPS” QoS Class. Ex: Video
over TCP.
118
4.15 Modelling Poisson arrivals in NetSim
What‟s a Poisson process, and how is it useful?
Any time you have events which occur individually at random moments, but which tend to
occur at an average rate when viewed as a group, you have a Poisson process.
For example, we can estimate that a certain node generates 1200 packets per minute. These
are randomly generated throughput the hour throughout the 60 seconds, but there are on
average 1200 packets per minute.
If 1200 packets generated per minute that, on average, one packet is generated every 60 /
1200 = 0.05 seconds. So, let‟s define a variable λ = 1/ 0.05 = 20 and call it the rate
parameter. The rate parameter λ is a measure of frequency: the average rate of events
(packets) per unit of time (in this case, seconds).
Knowing this, we can ask questions like, what is the probability that a packet will be
generated within the next second? What‟s the probability within the next 10 seconds? There‟s
a well-known function to answer such questions. It‟s called the cumulative distribution
function for the exponential distribution, and it looks like this:
F(x) =1−e−λx
Basically, the more time passes, the more likely it is that, a packet is generated. The word
“exponential”, in this context, actually refers to exponential decay. As time passes, the
probability of having no packets generated decays towards zero – and correspondingly, the
probability of having at least one packet generated increases towards one.
119
Plugging in a few values, we find that:
 The probability of generating a packet within the next 0.05 seconds is F(0.05)≈ 0.63
 The probability of generating a packet within 1 second is F(1)≈ 0.999999998
In particular, note that after 0.05 seconds – the prescribed average time between packets – the
probability is F(0.05)≈ 0.63 .
Generating Poisson arrivals in NetSim

We simply write a function to determine the exact amount of time until the next packet. This
function should return random numbers, but not the uniform kind of random number
produced by most generators. We want to generate random numbers in a way that follows our
exponential distribution.
Given that the inverse of the exponential function is ln, it‟s pretty easy to write this
analytically, where U is the random value between 0 and 1:
Next Time when a packet is generated =−ln(1- RandNo) / λ
This is exactly the code used in NetSim, and this is available in the source C file in
../NetSim_Standard/Simulation/Application/Distribution.c. In the case exponential
distribution, you would see
case Distribution_Exponential: /*Exponential Distribution Function*/
fFirstArg = args[0];
nRandOut = fnRandomNo(10000000, &fRand, uSeed, uSeed1);
fRandomNumber = (double) (fRand);
fFirstArg = 1 / fFirstArg;
*fDistOut = (double) -(1 / fFirstArg)* (double) logl(1 - fRandomNumber);
The simple way of selecting this via the UI is to selecting exponential distribution for inter-
arrival time when modelling application properties.
120
5 Running simulation via CLI
5.1 Running NetSim via CLI
Note: This feature is available from v7 onwards. In v8, NetSim can be run via CLI for
Internetworks, Advanced Wireless Networks – MANET, Wireless Sensor Networks, Internet
of Things, ZigBee Networks, BGP Networks, Cellular Networks, LTE Networks and Cognitive
Radio Networks only. For other networks NetSim v8 can only be run via GUI. In v9, NetSim
can be run via CLI for VANET, Wi-max, LTE/LTE-A, Legacy networks.
Advanced users can model their simulation via a configuration file (which can be created
without the NetSim GUI) and run the simulation from command line. This is typically done
in cases where very large networks are to be simulated (it takes too long to create it in the
GUI), or to run a series of simulations automatically. The configuration file contains all
required information to run the simulation including the network topology, devices, links,
traffic, statistics, traces etc.
To run Simulation in NetSim through command line interface (CLI), the following steps have
to be followed.
Step 1: Note the App Path
App path is the file location in the system in which NetSim has been installed.
The app path can be found out by right clicking the NetSim Shortcut in the desktop and
selecting Open file location (Windows 7/8/10). The app path will be something like
“C:\Program Files\NetSim Standard\bin”, depending on where NetSim is installed.
Note: The path to the bin folder of the app path must be mentioned
Step 2: Note the IO Path
IO path (Input/output Path) is the path where the input and output files of an application is
written. This is similar to the temp path of windows OS. For NetSim, the IO path can be got
by Start  Run  %temp%/NetSim. Once you reach this folder, the user can notice that the
path would be something like “C:\Users\Ram\AppData\Local\Temp\NetSim”
121
The IO path is the path where the Configuration.xml (NetSim Configuration file) of the
scenario, that will be simulated, should be present.
App path and IO path can also be same, i.e., Configuration.xml can be placed inside the app
path (if the app path has write permission). Otherwise, users can create a folder for IO path
and Configuration.xml can be placed inside that folder.
Note: Sample configuration.xml files are available in the <NetSim installed Directory>/Docs/
Sample_Configurations folder of the NetSim install directory inside the respective protocol
folder names.
Step 3: Running NetSim through command line for Simulation
To run NetSim through command line, copy the app path where NetSimCore.exe is present
and paste it in the command prompt.
>cd <app path>
Note: File path should be always added in the command prompt within double quotes. For
example,
>cd “C:\Program Files (x86)\NetSim Standard\bin”
For floating/roaming licenses, type the following in the command prompt. The type of license
can be seen by clicking on NetSim Help  About NetSim
>NetSimCore.exe<space> -apppath<space><app path><space>-iopath<space><io

path><space>-license<space>5053@<Server IP Address>
Where,
 <app path> contains all files of NetSim including NetSimCore.exe

 <iopath> contains Configuration.xml and Configuration.xsd (Configuration.xsd is
available in bin folder). Refer section 5.2.4 to know about configuration.xsd file.
 5053 is the port number through which the system communicates with the license server
i.e the system in which the dongle is running (for floating license users)
122
 <Server IP Address> is the ip address of the system where NetSim license server (dongle)
is running. Please contact your network administrator / lab in charge to know the IP
address of the PC where the NetSim license server is running.
The following screenshot is the example of running NetSim through CLI where the ip address
of the NetSim license server is 192.168.0.2
For node-locked licenses, type the following in the command prompt

path><space>
Where,
 <app path> contains all files of NetSim including NetSimCore.exe

 <iopath> contains Configuration.xml and Configuration.xsd
The following screenshot is the example of running NetSim through CLI for the node locked
license.
Simulation will be completed successfully and the text files that are requested by the end user
in Configuration.xml will be written in the <iopath>.
Note: If the folder name contains white space, then mention the folder path within double
quotes while specifying the folder name in the command prompt. For example, if app path
contains white space, then the app path must be mentioned within double quotes in the
command prompt as given below.
123
>cd <app path>
>NetSimCore.exe -apppath <”app path”> -iopath <io path>-license

5053@<License Server IP Address>
To know more about the options that are available to run NetSim via CLI, type the following
in the command prompt.
>cd <app path>
>NetSimCore.exe -h
124
5.1.1 Running CLI via Quick edit mode
With Quick Edit mode, you can copy text between a command window and Windows-based
programs, and you can also paste text into a command window by using a right-click
operation.
To use Quick edit mode in command prompt users can run the command prompt -> Right
Click the icon in the upper-left corner of the Command Prompt window, and then
Click Properties -> In the options, enable Quick Edit mode -> and select ok.
125
5.2 Understanding Configuration.xml file
Let‟s see under the hood to know how NetSim is working.
Using UI
GUI
Using CLI
Configuratio
Metrics.txt
n.xml
Protocol
Engine +
Stack +
Kernel
Fig.1. NetSim Architectural Overview
To model a scenario in order to generate metrics in NetSim, GUI will write all the details
about the devices used in the scenario and its properties, the links used and their properties,
the properties of the environment being used, etc. in Configuration.xml just when the user
performs the simulation.
The back-end engine that contains dlls and NetSimCore.exe will read this Configuration.xml,
execute the simulation and write output metrics files (in .txt format) to the IO path. Then, the
GUI will display the metrics based on the text files written by the backend.
In order to run NetSim through command line (CLI), the user has to create the
Configuration.xml furnishing all the details about the devices, links and the environment of
the desired scenario.
126
5.2.1 How to use Visual Studio to edit the Configuration file?
To edit the Configuration.xml, xml editor is required. There are various xml editors available
in the market. Visual Studio 2010 is one of the xml editors that can be used to edit the
Configuration.xml with efficacy.
This section shows limelight on how to use Visual Studio to edit the Configuration.xml.
XML view provides an editor for editing raw XML and provides IntelliSense and color
coding.
After you type the element name and press the CTRL+ SPACE, you will be presented with a
list of attributes that the element supports. This is known as “IntelliSense”. Using this feature,
you can select the options that are required to create the desired scenario.
Color coding is followed to indicate the elements and the attributes in a unique fashion.
The following screenshot displays the Configuration.xml which is opened through the Visual
Studio.
To reformat it, click on “Reformat Selection” icon.
127
5.2.2 Sections of Configuration file
These are the different sections in Configuration.xml:
 EXPERIMENT_INFORMATION
 GUI_INFORMATION
 NETWORK_CONFIGURATION
 SIMULATION_PARAMETER
 PROTOCOL_CONFIGURATION
 STATISTICS_COLLECTION
EXPERIMENT_INFORMATION:
This section contains the details about the user credentials, such as the user mode
(Admin or Exam or Practice), experiment name, date on which the experiment is created and
the comments about the experiment. This section plays a significant role while running
NetSim through GUI.
GUI_INFORMATION:
This section contains the GUI information like the environment length, view type etc.
and the network name which is desired to be run.
NETWORK_CONFIGURATION:
This section is used to configure the devices and the links of the desired network at
the each layer of the TCP/IP stack. It consists of DEVICE_CONFIGURATION,
CONNECTION and APPLICATION_CONFIGURATION. DEVICE_CONFIGURATION
configures the devices in the desired network while the CONNECTION configures the links
in the desired network and APPLICATION configures the Applications.
SIMULATION_PARAMETER:
Simulation time and seed values are described in this section.
PROTOCOL_CONFIGURATION:
IPV4 and static ARP are enabled or disabled in this section. The text files illustrating
the static routing and static ARP can be obtained by enabling the corresponding tags in the
Configuration.xml.
128
STATISTICS_COLLECTION:
The packet trace and the event trace can be observed in the text files which are created
by enabling the tags in this section. The required fields of the packet trace can be enabled in
the PACKET_TRACE while the event trace can be enabled in the EVENT_TRACE of this
section.
5.2.3 Sample Configuration file
Sample “Configuration.xml” file will be installed in user system along with the software at
<NetSim installed Path>\Docs\ Sample_Configuration\ <Network Technology>. User can
open and edit these files using Visual Studio 2010 or any XML editor. The purpose of
providing the sample “Configuration.xml” file is to assist the user in writing a network
scenario manually by analyzing the format for that specific network technology.
5.2.4 Configuration.xsd file
Configuration.xsd is a XML schema Definition file which is present in the path

<NetSim_Installation_Directory>/bin
Configuration.xsd file can be placed inside the <iopath> along with the configuration.xml file
to verify the contents in the configuration.xml file. This file checks and validates the structure
and vocabulary of a configuration.xml document against the grammatical rules of the
appropriate XML language.
It is not mandatory to place the configuration.xsd file along with the configuration.xml file in
the iopath. But if it is done, then it will be easier to check & validate changes that are done to
the configuration.xml file.
129
6 Analysis
6.1 Performance Metrics
NetSim provides distinct quantitative metrics at various abstraction levels such as Network
Metrics, Link Metrics, TCP Metrics, Application Metrics, etc., at the end of simulation. With
the help of metrics, users can analyze the behavior of the modeled network and can compare
the impact of different algorithms on end-to-end behavior.
After simulation of a scenario is performed, NetSim Performance Metrics are shown on the
screen as shown below:-
The Performance metrics can be further subdivided into sections

 Network metrics: Here users can view the values of the metrics obtained based on
the overall network.
 Link Metrics: Displays the values of the metrics pertaining to each link
 Link_Id-It is the unique Id for the link.
 Packets_Transmitted-It is the total number of packets transmitted in the link.
Along with data packets, it includes protocol control packets like
ARPRequest, ARPReply, TCP_ACK, TCP_SYN, RTS, CTS, WLAN_ACK,
OSPF_ HELLO, RIP packets etc.
 Error_Packets-Total number of packets error in the link inclusive of data and
control packets.
130
 Collided_Packets-Total number of packets collided in the link including data
and control packets.
 Bytes_Transmitted-It is the total number of bytes transmitted in the link. It is
equal to the sum of the „Payload_Transmitted‟ and „Overhead_Transmitted‟
transmitted in the link.
 Payload_Transmitted-It is the total payload transmitted in the link.
 Overhead_Transmitted-It is the total overhead transmitted in the link. It
includes the layer wise overheads and all control packets in the link.
 Queue Metrics: Displays the values of the queue metrics for the devices containing
buffer queue like routers, access points etc.
 Device Id-Unique id number of the device.
 Port Id-Unique id number of the port of the device. This is also called as
interface id.
 Queued Packet-Number of packets queued at a particular port of a device.
 Dequeued Packet-Number of packets removed from the queue at a particular
port of device
 Dropped Packet-Number of packets dropped at a particular port of a device.
 Protocol metrics: Displays the protocol based metrics which are implemented in
Network scenario. Metrics will vary depending upon the type of network simulated.
 Device metrics: Displays device related metrics like ARP table, IP forwarding tables.
This is also dependent upon the type of network
 Application Metrics: Displays the various metrics based on the Application running
in the network scenario.
 Application Id- It is the unique Id of the application running at the source.
 Application Name - It is unique name of the application running.
 Source Id-It is the unique Id of the device running that particular application.
 Destination Id-It is the unique Id of the destination device.
 Packets Transmitted-It is the total number of packets generated and
transmitted from the source.
131
 Packets Received-It is the total number of packets received at the destination.
 Payload Transmitted-It is the total payload transmitted in bytes. It is equal
to the product of „Packets Transmitted‟ and „Packet Size‟.
 Payload Received-It is the total payload received at the destination in bytes.
 Throughput-Total user data (or) payload delivered to their respective

destination every second.
 Delay-It is the average amount of time taken calculated for all the packets to
reach the destination from the source.
Note about metrics: The metrics are calculated at each layer and might not be equivalent to
the same metric calculated at a different layer. For exactness and precision we recommend
users also verify the results with the event trace & packet trace generated by NetSim.
Note about packet transmission: The Network Stack forms the core of NetSim‟s architecture.
The Stack consists of five IN and OUT events: PHYSICAL_IN, MAC_IN, NETWORK_IN,
TRANSPORT_IN, APPLICATION_IN and APPLICATION_OUT, TRANSPORT_OUT,
NETWORK_OUT, MAC_OUT, PHYSICAL_OUT. All the packets when transferred
between devices go through the above events in order. IN events occur when the packet is
entering a device and all the OUT events occur when packet leaves a device.
The following table lists the various files that will be written in the NetSim install directory/
IO path on completion of simulation.
132
S. No File Contents
Contains the metrics of the network

1 Metrics.txt
that is simulated recently.
Contains the data required to plot the

2 MetricsGraph.txt graph between the various
parameters in metrics against time
Contains the status of the
3 LicenseErrorLog.txt communication between the NetSim
dongle and the client.
This file will be written while
reading the Configuration file.
4 ConfigLog.txt
Provides errors if there are errors in
the configuration file.
Contains the logs as the control
5 LogFile.txt flows across various layers in the
Network Stack
Contains the detailed packet
6 PacketTrace.txt information. This file will be written
only when Packet Trace is enabled.
Contains the information about each
7 EventTrace.txt event. This file will be written only
when Event Trace is enabled.
If NetSim runs via the UI, then the metrics will be displayed automatically at the end of
simulation with illustrative tables.
If NetSim runs via CLI, then the metrics will be written into Metrics.txt and
MetricsGraph.txt.
133
6.2 Packet Animation
NetSim provides the feature to play and record animations to the user. Packet animation
enables users to watch traffic flow through the network for in-depth visualization and
analysis.
User has the following options before running simulation:
 No animation,
 Record the animation and
 Play and record animation while running simulation.
Click here to record packet animation
The packet animation would then be recorded and the user can view the animation from the
metrics screen as shown below:
Click here to view packet animation
134
When packet animation is enabled, a screen with the following toolbar appears:
While viewing packet animation, user can see the flow of packets as well as the type of
packet. Blue color packet denotes control packet, green color is used for data packet and red
color is error/collided packet. Packet Animation table is also provided for users to see the
flow of packets along with packet animation.
Example showing packet animation: In first figure, CBR data packet is flowing from
Switch D to Node E (green color) and TCP_ACK is sent from Node E to Switch D in second
figure (blue color).
135
6.2.1 Example on how to use NetSim packet animation feature:
Case 1: ARP PROTOCOL - WORKING
 Create a scenario with 3 wired nodes, 2 switches and 1 router and connect it based on
the following scenario.
 Disable TCP in all the wired nodes.
 Select Application button and click on the gap between grid environment and ribbon.
Right click on application, select properties and set Source_Id and Destination_Id as 1
and 2 respectively.
 Set Simulation time = 100s. After clicking on Run Simulation, edit IP and ARP
Configuration tab by setting Static ARP as Disable. Click on OK button to simulate.
Now click on packet animation and analyse the following:
 NODE-1 sends ARP_Request which is then broadcasted by SWITCH-4.
136
 During the process the devices that receive the ARP_Request packet (Switch, Router,
and Node-2) will update their ARP table or the switch table.
 NODE -2 sends the ARP_Reply to NODE-1 via SWITCH-4.
 Now NODE-1 updates its ARP table with the MAC address of NODE-2 on receiving
the ARP_Reply.
 After this step, NODE-1 starts sending data packets to NODE-2 since the source now
has both IP and MAC addresses of destination.
Case 2: Across-Router-IP-forwarding
 Follow all the steps till Step 2 and perform the following sample.
 To run the simulation, drop the Application icon and set the Source_Id and
Destination_Id as 1 and 3 respectively.
 Click on Run Simulation and set Simulation time as 100 sec.
 Then go to IP and ARP Configuration tab and set Static ARP as Disable. Click on
OK button to simulate.
137
Click on packet animation to analyse the following:
 NODE-1 transmits ARP_Request which is further broadcasted by SWITCH-4.

ROUTER-6 sends ARP_Reply to NODE-1 which goes through SWITCH-4. Then
NODE-1 starts to send data to NODE-3.
 If the router has the address of NODE-3 in its routing table, ARP protocol ends here
and data transfer starts that is PACKET_ID 1 is being sent from NODE-1 to NODE-3.
 In other case, Router sends ARP_Request to appropriate subnet and after getting the
MAC ADDRESS of the NODE-3, it forwards the packet which it has received from
NODE-1.
 When a node has to send data to a node with known IP address but unknown MAC
address, it sends an ARP request. If destination is in same subnet as the source (found
through subnet mask) then it sends the ARP (broadcast ARP message) request,
otherwise it forwards it to the default gateway.
 Former case happens in case of intra-LAN communication. The destination node
sends an ARP response which is then forwarded by the switch to the initial node.
Then data transmission starts.
 In latter case, a totally different approach is followed. Source sends the ARP request
to the default gateway and gets back the MAC address of default gateway. (If it
knows which router to send then it sends ARP request to the corresponding router and
not to Default gateway).
 When source sends data to default gateway (a router in this case), the router
broadcasts ARP request for the destined IP address in the appropriate subnet. On
getting the ARP response from destination, router then sends the data packet to
destination node.
138
6.3 Dynamic Metrics (only in Standard/Pro Version)
Dynamic metrics allows users to monitor the value of a parameter over simulation time.
From NetSim v8, link and application throughputs can be dynamically plotted. These plots
can be done offline or during simulation. Note that enabling them to be plotted during
simulation would consume a lot of memory and slow down the simulation significantly.
Dynamic metrics can be set by clicking on the dynamic metrics icon in the GUI, and
selecting those metrics that you wish to monitor.
Upon completion of the simulation dynamic metrics plots can be viewed by clicking on Link
throughput in Metrics screen.
139
6.4 Analytics Menu (Multiple Experiments)
NetSim analytics module is designed to enable comparison of performance metrics of
multiple experiments. All the different networks of NetSim can be compared in this menu.
Parameters like Simulation time, packets transmitted, packets errored, packets collided, Bytes
transmitted etc., of different sample experiments can be visualized with the help of graphs.
To compare and analyse performance of various networks goto Netsim Simulation menu and
click Analytics to view the Analytics screen. A graphing engine facilitates plotting of
different performance metrics across the different experiments. This can be used to
infer/trend how changes in input parameters affect network performance. An explanation of
the use of the different fields in the Analytics screen is detailed below:
 Select a Metrics File (simulation output file which will be stored where the
simulation experiment is saved) by choosing select the Metrics File to add it onto
the Metrics Table by using Browse button.
Click on
“Browse” to select
the experiments
Click to select the

metrics
Plot the chart here
 The Graph Field
 Select the Metrics - Select the parameters for Y-axis by clicking on the
dropdown menu.
140
 Graph - Based on the X-axis (i.e. Metrics File/ Experiment selected) and Y-axis
(i.e. Metrics selected by using the dropdown menu above the graph), a Bar
graph will be plotted.
 Add metrics file of different experiments to compare.
 The Metrics Table- This is the table that is generated when the Experiments are
selected using the Select the Metrics File/ Experiment option.
 The first column in the Metrics Table consists of the Check Boxes that are used
to select (i.e. by default all the Experiments are selected) or deselect the selected
Experiments. If an Experiment is selected, then that Experiment would be
compared along with other Experiments, else the Experiment would not be
compared with other Experiments.
 The second column in the Metrics Table “X” button is available. This “X” button
is used for deleting the Experiment.
 Change Graph color: This option is provided for users to change the color of the
graph. For this, users can goto change color option  click on color select their
desired color  click on ok.
 Export to .csv - Click on Export to .csv to export the Metrics Table to a “.csv”
format. This action button will export the contents to a “.csv” format that is available.
 Print - Click on the Print option to print the Metrics Table. This action button will
fetch the Print dialogue box.
141
6.5 Packet Trace (only in Standard/Pro Version)
6.5.1 Introduction
NetSim allows users to generate trace files which provide detailed packet information useful
for performance validation, statistical analysis and custom code de-bugging. Packet Trace
logs a set of chosen parameters for every packet as it flows through the network such as
arrival times, payload, overhead, errored, collided, successful packets, etc.
By providing a host of information and parameters of every packet that flows through the
network, packet trace provides necessary forensics for users to catch logical errors without
setting a lot of breakpoints or restarting the program often. Window size variation in TCP,
Route Table Formation in OSPF, Medium Access in Wi-fi, etc, are examples of protocol
functionalities that can be easily understood from the trace.
Note: Turning on Packet Trace will slow down the simulation significantly
By default, the packet tracing option is turned off.
How to enable Packet Trace via UI?
If NetSim runs via the UI, packet trace can be turned on by clicking the Packet Trace
icon in the tool bar and selecting the required fields in the packet trace. NetSim will write the
packet trace to the specified path during simulation.
How to enable Packet Trace via CLI?
If NetSim runs via CLI, then the packet trace can be turned on by enabling the packet
trace in the STATISTICS_COLLECTION tag of the configuration file. NetSim will write the
packet trace to the specified path during simulation.
How to import Packet Trace to Excel?
Step 1: Open Excel sheet, select Data  From Text, it will ask for file, then select the trace
file which you want to export to excel sheet.
142
Step 2: Select the file and click import and following window will appear,
Step 3: Select comma  Click next and then Finish. The following window will appear, in
that select the check box where you want to put your data as mentioned in the following
window, and then click ok.
143
Packet Trace Metrics:
PACKET_ID Specifies the ID of the Data Packet

SEGMENT_ID Specifies the ID of the segment of the Data Packet
Specifies the type of Packet. It can be Control Packet,
PACKET_TYPE Custom, Peer_to_peer, E-Mail, DataBase, FTP, Video,
Voice, HTTP
Specifies the type of Control Packet transmitted. It can
be TCP_SYN, TCP_SYN_ACK, TCP_ACK,
CONTROL_PACKET_TYPE
WLAN_ACK, ICMP_ECHO_REQUEST,
ICMP_ECHO_REPLY etc.
SOURCE_ID Specifies the Node ID of the source device
DESTINATION_ID Specifies the Node ID of the destination device
Specifies the Node ID of the device transmitting the
TRANSMITTER_ID
packet
RECEIVER_ID Specifies the Node ID of the device receiving the packet
Specifies the time(microseconds) at which the data
APP_LAYER_ARRIVAL_TIME packet is generated at Application Layer of source
device
Specifies the time(microseconds) at which the packet
TRX_LAYER_ARRIVAL_TIME
reaches the Transport Layer of source device
NW_LAYER_ARRIVAL_TIME
reaches the Network Layer of source device
MAC_LAYER_ARRIVAL_TIME
reaches the Data Link Layer of source device
PHY_LAYER_ARRIVAL_TIME
reaches the Physical Layer of source device
PHY_LAYER_START_TIME
leaves the Physical Layer of source device
PHY_LAYER_END_TIME
reaches the Physical Layer of destination device
144
APP_LAYER_PAYLOAD Specifies the size of the Payload at Application Layer
TRX_LAYER_PAYLOAD Specifies the size of the Payload at Transport Layer
NW_LAYER_PAYLOAD Specifies the size of the Payload at Network Layer
MAC_LAYER_PAYLOAD Specifies the size of the Payload at Data Link Layer
PHY_LAYER_PAYLOAD Specifies the size of the Payload at Physical Layer
PHY_LAYER_OVERHEAD Specifies the size of the overhead in Physical layer
Specifies whether the Packet is Successful, Collided or
PACKET_STATUS
Errored
LOCAL_ADDRESS Specifies the Port Number at Source Node
FOREIGN_ADDRESS Specifies the Port Number at Destination Node
CWND Specifies the size of congestion window
If TCP is enabled, it specifies the TCP Sequence
SEQ_NO
number of the packet
If TCP is enabled, it specifies the TCP
ACK_NO
Acknowledgement number of the packet
RTT Specifies the Round Trip Time for the packet
RTO Specifies the Retransmission Timeouts
CONNECTION_STATE Specifies the state of TCP connection
145
6.6 Event Trace (only in Standard/Pro Version)
6.6.1 NetSim Network Stack
NetSim‟s Network Stack forms the core of NetSim and its architectural aspects are
diagrammatically explained below. Network Stack accepts inputs from the end-user in the
form of Configuration file and the data flows as packets from one layer to another layer in the
Network Stack.
All packets, when transferred between devices move up and down the stack, and all events in
NetSim fall under one of these ten categories of events, namely, Physical IN, Data Link IN,
Network IN, Transport IN, Application IN, Application Out, Transport OUT, Network
OUT, Data Link OUT and Physical OUT. The IN events occur when the packets are entering
a device while the OUT events occur while the packet is leaving a device.
Every device in NetSim has an instance of the Network Stack shown above. Switches
& Access points have a 2 layer stack, while routers have a 3 layer stack. End-nodes have a 5
layer stack.
The protocol engines are called based on the layer at which the protocols operate. For
example, TCP is called during execution of Transport IN or Transport OUT events, while
802.11b WLAN is called during execution of MAC IN, MAC OUT, PHY IN and PHY OUT
events.
146
When these protocols are in operation they in turn generate events for NetSim's
discrete event engine to process. These are known as SUB EVENTS. All SUB EVENTS, fall
into one of the above 10 types of EVENTS.
Each event gets added in the Simulation kernel by the protocol operating at the
particular layer of the Network Stack. The required sub events are passed into the Simulation
kernel. These sub events are then fetched by the Network Stack in order to execute the
functionality of each protocol. At the end of Simulation, Network Stack writes trace files and
the Metrics files that assist the user in analyzing the performance metrics and statistical
analysis.
Event Trace:
The event trace records every single event along with associated information such as
time stamp, event ID, event type etc in a text file or .csv file which can be stored at a user
defined location.
Apart from a host of information, the event trace has two special information fields
for diagnostics
a) A log of the file name and line number from where the event was generated (Please
refer “Custom Code in NetSim  Debugging your code  Via CLI”) and
b) Previous event which triggered the current event.
NetSim provideson
Note: Turning users with
Event the option
Trace of turning
will slow onsimulation
down the "Event Traces".
significantly
How to enable Event Trace via GUI?
If NetSim runs via GUI, event trace can be turned on by clicking the Event Trace icon
in the tool bar and selecting the required fields in the event trace.
How to enable Event Trace via CLI?
If NetSim runs via CLI, then the event trace can be turned on by enabling the event
trace in the STATISTICS_COLLECTION tag of the configuration file.
147
How to import Event Trace to Excel?
Refer Help on “Generating Packet Trace How to import Packet Trace to Excel?”
Event Trace Metrics
Event_Id Specifies the ID of the Event

Specifies the type of event being performed, for eg -
Event_Type APPLICATION_IN, APPLICATION_OUT, MAC_OUT, MAC_IN,
PHYSICAL_OUT, PHYSICAL_IN,etc
Event_Time Specifies the time(in microseconds) at which the event is being executed
Device_Type Specifies the type of device in which the current event is being executed
Device_Id Specifies the ID of device in which the current event is being executed
Specifies the Interface_Id of device in which the present event is being
Interface_Id
executed.
Specifies the ID of the Application on which the specific event is
Application_Id
executed
Specifies the ID of the packet on which the current event is being
Packet_Id
executed
Specifies the ID of the segment of packet on which the current event is
Segment_Id
being executed
Protocol_Name Specifies the Protocol which is presently executed
Specifies the protocol sub event which is being executed. If the sub event
Subevent_Type value is 0, it indicates interlayer communication (Ex: MAC_OUT called
by NETWORK_OUT) or a TIMER_EVENT which has no sub event.
Packet_Size Specifies the size of packet during the current event
Prev_Event_Id Specifies the ID of the event which generated the current event.
148
6.7 Trace Data Analysis (only in Standard/Pro Version)
This section explains about how to analyze the data of a NetSim trace file.
How to set filters to NetSim trace file
Step 1: Open the trace file. (In this example packet trace is opened)
Step 2: Go to Data menu and click on filter icon to enable the auto filter.
Step 3: Click the arrow in the header of the column you want to filter. In the list of text or
numbers, uncheck the (Select All) box at the top of the list, and then check the boxes of the
items you want to show.
For example, click on arrow of SOURCE_ID and uncheck the “Select all” check box and
select NODE 2 then click on ok.
All the rows which are having NODE 2 as source id will be shown.
149
Typically filters can be set to observe “Errored/Collided/Successful “packets, packets of
destination and packets of source.
Observing packet flow in the Network through packet trace file
Step 1: Open the packet trace file.
Step 2: Set the filter.
Step 3: Click the arrow in the header of the column PACKET_ID and uncheck the
“Select all” check box and select the packet id which you want to observe, for example 1, and
then click on ok.
150
Scenario is as shown below and traffic flow is from Wired Node 1 to Wired Node 2.
Flow of packet 1 can be observed from the packet trace as shown below.
Note: In the trace file device IDs are shown not device names. Wired Node 1’s ID is 2 so it is
Shown as NODE-2, Wired Node 2’s ID is 3 so it is shown as NODE -3, Router-1’ ID is 1 so it
is shown as ROUTER-1. Device IDs are shown on the top of the device icon in the above
scenario.
In a scenario source and destinations are fixed but transmitter and receiver are changed. For
example in the above scenario NODE-2 is the source and NODE-3 is the destination, but
when NODE- 2 sending the packet to the ROUTER-1 then NODE-2 is the transmitter and
ROUTER-1 is the receiver. When ROUTER-1 sending the packet to the NODE-3, ROUTER-
1 is the transmitter and NODE-3 is the receiver.
151
6.8 Packet Capture & analysis using Wireshark
(www.wireshark.com) (only in Standard/Pro Version)
6.8.1 Enabling Wireshark in the network scenario
In NetSim, to enable packet capture in Wireshark, Right Click on the device where
Wireshark will capture packets. In the properties, go to Global_Properties and set the
Wireshark parameter as Online
6.8.2 Viewing captured packets
If enabled, Wireshark automatically starts during simulation and displays all the captured
packets.
To view the details of the packet displayed, click on the packet as shown below:
152
The detail of the contents of the selected packet can be seen in the below panes.
TREE View
BYTE View
In the above figure, the details of the packet are displayed in both tree form and bytes form.
In the tree form, user can expand the data by clicking on the part of the tree and view
detailed information about each protocol in each packet.
6.8.3 Filtering captured packets
Display filters allow you to concentrate on the packets you are interested in while hiding
the currently uninteresting ones. Packets can be filtered by protocol, presence of a field,
values of fields etc.
To select packets based on protocol, type the protocol in which you are interested in the
Filter: field of the Wireshark window and press enter to initiate the filter. In the figure
below, tcp protocol is filtered.
You can also build display filters that compare values using a number of different
comparison operators like ==, != , >, <, <=, etc.
Following is an example displaying filtered packets whose SYN Flag and ACK Flag are
set to 1 in a TCP Stream.
153
6.8.4 Analyzing packets in Wireshark
6.8.4.1 Analyzing Conversation using graphs
A network conversation is the traffic between

two specific endpoints. For example, an IP
conversation is all the traffic between two IP
addresses.
In Wireshark,
Go to Statistics Menu Conversations
Different types of protocols will be available. User can select the specific conversation by
going to the desired protocol. For example, in the following diagram, we have selected TCP.
User can also analyze each of the conversation and can create graphs by selecting them and
clicking on “Graph”
154
The different types of graphs possible are
 Round Trip time
 Throughput
 Time/Sequence (Stevens)
 Time/Sequence (tcptrace)
 Window Scaling
155
6.8.4.2 Comparing the packet lengths
To analyze the packet sizes of all packets transmitted,

go to Statistics MenuPacket lengths.
Users can also set filter to analyze a collection of

specific packets only. For example, tcp filter is set to
obtain the packet length below:
6.8.4.3 Creating IO graphs
To get the graph, go to Statistics Menu IO Graph.
156
6.8.4.4 Creating Flow graphs
The flow graph feature provides a quick and easy to use

way of checking connections between a client and a server.
It can show where there might be issues with a TCP
connection, such as timeouts, re-transmitted frames, or
dropped connections.
To access flow graph, go to Statistics Menu Flow Graph

and select the flow type.
By default you can see the flow graph of all the packets.
157
To get the TCP flow, select TCP flow in “Flow Type” dropdown box and you will obtain the
flow as shown:
158
7 Custom code in NetSim
7.1 Writing your own code
NetSim allows the user to write the custom code for all the protocols by creating a DLL
(Dynamic Link Library) for their custom code and replacing NetSim‟s default DLL with the
user‟s custom DLL.
There are various important steps in this process, and each of these steps has various options
as explained in the subsequent pages:
7.1.1 Modifying code
DLL is the shared library concept, implemented by Microsoft. All DLL files have a .dll file
extension. DLLs provide a mechanism for sharing code and data to upgrade functionality
without requiring applications to be re-linked or re-compiled. It is not possible to directly
execute a DLL, since it requires an EXE for the operating system to load it through an entry
point.
Note: If the DLL needs to be debugged then build the DLL in “debug” mode or else build in
“release” mode.
Dynamic link libraries (DLLs) can be built using different compilers:
(a) Using Microsoft Visual Studio Compiler
a) Compiler: Microsoft Visual Studio
To create the DLL follow the steps given below.
Note: Make sure that Visual Studio 2010 is installed in your computer
Step 1: Go to “../NetSim Standard/src/Simulation” folder and double click on

“NetSim.sln” file to open the solution in visual studio.
Note: It is recommended to keep a separate copy of the “../NetSim

Standard/src/Simulation” folder to have the backup of the original source code.
159
b)
Note: Sometimes you may get the following warning message. Then click on ok
and proceed.
Step 2: Inside Solution Explorer pane in Visual Studio 2010, double click on DSR. Then
open DSR.C file by double clicking on it.
160
Step 3: Add fprintf (stderr, “Source is modified\n”); statement inside the source code of
DSR as shown below to print “Source is modified”.
Note: - Use fprintf (stderr,”Hello World”) instead of printf ( ) to write to standard out.
stdout is redirected to LogFile.txt which is present in <iopath>. So you can see “Hello
World” Statement (or whatever you write inside the printf) inside the LogFile.txt.
Once this is done click to save the changes and overwrite the file (in case of write
protection).
7.1.2 Building Dlls
Step 1: Right Click on the Project (in this case DSR) inside the Solution Explorer pane and
select Build to create DLL file of that specific protocol only
NOTE: To create DLL file of all the protocols actively displayed inside solution pane, click
on “BuildBuild Solution”
161
Check that the build is successful and necessary DLL files have been built.
Step 2: Inside the simulation folder (present on the desktop) a Dll folder will be created and
inside, the DLL‟s are built.
It will contain custom DLL‟s which have been built per the modifications done.
162
7.1.3 Linking Dlls
The procedure to link custom dynamic link libraries (DLLs) is explained below. This
procedure is common for any linking of any custom DLL to NetSim.
Now we will link the customized libDSR.dll to the NetSim.
Step 1: Copy the newly created DLL file of customized DSR from “../NetSim
Standard/src/Simulation” folder
Step 2: Go to “NetSim Standardbin” folder. Here one would find default DLLs for
respective protocols as shown in next figure.
Step 3: Rename the default DLL: It is recommended to rename the default DLL thereby
saving a copy of original DLL. For example libCognitiveRadio.dll has been renamed as
libCognitiveRadio_default.dll as shown below.
Original DLL
Original DLL has been renamed
163
Step 4: Place the custom DLL obtained from Step 1 inside the “NetSim Standard  bin”
folder.
Custom (your) DLL
Note: Ensure that the name of the DLL which is pasted is exactly the same as
the original DLL (before it was renamed). For the example case of DSR, the DLL
must be libDSR.dll.
7.1.4 Running Simulation
User can run the simulation via GUI (Please refer section 3). In this case, user can create a
scenario in any network which involves DSR protocol. Running the simulation with the
custom DLL will give desired output to the user as shown below.
Press enter then simulation will continue.
164
7.2 Implementing your code - Examples
7.2.1 Hello World Program
Objective: Print Hello World from DSR protocol.
Implementation: Add fprintf (stderr, “<MESSAGE>”) statement inside the source code of
DSR as shown below to print “Hello World” when custom built dll is executing.
Note: - Use fprintf (stderr,”Hello World”) instead of printf ( ) to write to standard out.
stdout is redirected to LogFile.txt which is present in <iopath>. So you can see “Hello
World” Statement (or whatever you write inside the printf) inside the LogFile.txt.
Create DLL and Link the DLL to the NetSim as explained in Section 7.1. And run the
simulation, you can see the following output on the console.
Press enter then simulation will continue.
165
7.2.2 Introducing Node Failure in MANET
Objective: Node failure using MANET-DSR using Device Id.
Implementation: Identify the Device ID of the particular node to be failed.
Step 1: Create a file with the name NodeFailure.txt inside the bin folder of NetSim
installation directory. The file will contain two columns: one being the Node ID of the device
to be failed and other being the failure time (in microseconds).
For example, to fail Node Id 2 from 10th sec onwards and fail Node Id 1 from 90th sec
onwards, the NodeFailure.txt file will be as follows:
Step 2: Go to DSR.c in DSR protocol.
Step 3: The function fn_NetSim_DSR_Init() will execute before the protocol execution
starts. So in this function, we will read the NodeFailure.txt and save information regarding
which nodes will fail at which time. Add the following code inside the specified function.
int i;
FILE *fp1;
char *pszFilepath;
char pszConfigInput[1000];
pszFilepath = fnpAllocateMemory(36,sizeof(char)*50);
strcpy(pszFilepath,pszAppPath);
strcat(pszFilepath,"/NodeFailure.txt");
fp1 = fopen(pszFilepath,"r");
i=0;
if(fp1)
{
while(fgets(pszConfigInput,500,fp1)!= NULL)
{
sscanf(pszConfigInput,"%d %d",&NodeArray[i],&TimeArray[i]);
i+=1;
}
}
fclose(fp1);
166
Step 4: The fn_NetSim_DSR_Run( ) is the main function to handle all the protocol
functionalities. So add the following code to the function at the start.
int i,nFlag=1;
if(nFlag)
{
for(i=0;i<100;i++)
if((pstruEventDetails->nDeviceId== NodeArray[i])&&(pstruEventDetails-
>dEventTime >= TimeArray[i]))
{
pstruEventDetails->nInterfaceId = 0;
pstruEventDetails->pPacket=NULL;
return 0;
}
}
Step 5: Add the following code inside DSR.h header file

//Node failure model
int NodeArray[200];
int TimeArray[200];
Step 6: Create DLL and Link the DLL to the NetSim as explained in Section 7.1.
Step 7: Create a scenario in MANET and run the simulation. User can utilize Packet
Animation to check the node failure (i.e. no packets are forwarded by failed nodes) after the
mentioned time.
167
7.2.3 Transferring file from source to destination in WSN
Objective: Transferring a real file from source node to destination node in WSN
Implementation: The code modifications to transfer file from Sensor to Sink node are
described here:
1. Open NetSim.sln in Visual Studio and add the following modifications.
2. The modified files are in Zigbee: Sensor.c and 802_15_4.h
3. In 802_15_4.h add the following line of code
#define _FILE_SEND_ //Uncomment to transfer file
4. In Sensor.c, the code must be modified at specified places in red color. Add the
modified code:
#include "main.h"
#include "List.h"
#include "802_15_4.h"
#define MAX_PAYLOAD 70
int fn_NetSim_FindAgentPos(double* dXPos, double* dYPos, int nAgentId,double

dSensingTime,AGENT** pstruAgent);
double fn_Sensor_CalculateDistance(POS_2D* pstruPos1, POS_2D* pstruPos2);
#ifdef _FILE_SEND_
typedef struct file_info
{
char Packet[100];
long len;
int Packet_Id;
_ele* ele;
}FILE_INFO,*PFILE_INFO;
#define FILE_INFO_ALLOC()
(PFILE_INFO)list_alloc(sizeof(FILE_INFO),offsetof(FILE_INFO,ele))
PFILE_INFO fileinfo=NULL;
static int nPacketId=0;
char file_name[100][50] = {"send.txt"};
char outfile_name[100][50] = {"receive.txt"};
int fnWriteFile(int PacketId)

{
char *packet;
static FILE *file_receive=NULL;
PFILE_INFO file_rec=fileinfo;
size_t siz;
if(!file_receive)
file_receive = fopen(outfile_name[0],"wb");
while(file_rec)
{
if(file_rec->Packet_Id == PacketId)
{
168
//fprintf(stderr,"file written. size = %d\n",file_rec-
>len);
packet = file_rec->Packet;
siz = file_rec->len;
fwrite(packet,sizeof(char),siz,file_receive);
}
file_rec=LIST_NEXT(file_rec);
}
fflush(file_receive);
return 0;
}
int fnsendfile(NETSIM_ID nSensorLoop)

{
NetSim_PACKET *PstruPacket;
FILE *file_transfer;
size_t siz;
long file_size;
long n;
PFILE_INFO file;
if(file_name[nSensorLoop-1] && *file_name[nSensorLoop-1])

file_transfer = fopen(file_name[nSensorLoop-1],"rb");
else
return -1;
if(!file_transfer)
{
perror(file_name[nSensorLoop-1]);
return -1;
}
fseek(file_transfer,0,SEEK_END);
file_size = ftell(file_transfer);
rewind(file_transfer);
n = file_size;
while(n>0)
{
char str[MAX_PAYLOAD+10];
fprintf(stderr,"Size left = %d\n",n);
if(n>=MAX_PAYLOAD)
{
siz = fread(str,sizeof(char),MAX_PAYLOAD,file_transfer);
}
else
{
siz = fread(str,sizeof(char),n,file_transfer);
}
n-=siz;
//Add application out to tramit the position

//Generate the packet
PstruPacket = fn_NetSim_Packet_CreatePacket(5);
PstruPacket->dEventTime = pstruEventDetails->dEventTime;
PstruPacket->nDestinationId = nGlobalPANCoordinatorId;
PstruPacket->nPacketId = ++nPacketId;
PstruPacket->nPacketStatus = 0;
PstruPacket->nPacketType = PacketType_Custom;
169
PstruPacket->nPacketPriority = Priority_Low;
PstruPacket->nQOS =(NETSIM_ID)QOS_BE;
PstruPacket->nSourceId = (NETSIM_ID)nSensorLoop;
//Update the Transport layer information
PstruPacket->pstruTransportData->nSourcePort = SOURCEPORT;
PstruPacket->pstruTransportData->nDestinationPort =
DESTINATIONPORT;
//Update the Network layer information
PstruPacket->pstruNetworkData->szSourceIP =
IP_COPY(fn_NetSim_Stack_GetFirstIPAddressAsId((NETSIM_ID)nSensorLoop,0));
PstruPacket->pstruNetworkData->szDestIP =
IP_COPY(fn_NetSim_Stack_GetFirstIPAddressAsId(PstruPacket-
>nDestinationId,0));
PstruPacket->pstruNetworkData->nTTL = MAX_TTL;
//Update the Application layer information
//For transferring file from Sensor to sink node
//70 bytes at a time
file =FILE_INFO_ALLOC();
memcpy(file->Packet,str,siz);
file->Packet_Id = PstruPacket->nPacketId;
file->len = siz;
LIST_ADD_LAST((void**)&fileinfo,file);
PstruPacket->szPayload = NULL;
PstruPacket->pstruAppData->dPayload = siz;
PstruPacket->pstruAppData->dOverhead = 0;
PstruPacket->pstruAppData->dPacketSize = PstruPacket-
>pstruAppData->dPayload + PstruPacket->pstruAppData->dOverhead;
PstruPacket->pstruAppData->dArrivalTime = pstruEventDetails-
>dEventTime;
PstruPacket->pstruAppData->dEndTime = pstruEventDetails-
>dEventTime;
PstruPacket->pstruAppData->dStartTime = pstruEventDetails-
>dEventTime;
if(NETWORK->ppstruDeviceList[nSensorLoop-1]-
>pstruTransportLayer->isUDP)
PstruPacket->pstruTransportData-
>nTransportProtocol=TX_PROTOCOL_UDP;
else if(NETWORK->ppstruDeviceList[nSensorLoop-1]-
>pstruTransportLayer->isTCP)
PstruPacket->pstruTransportData-
>nTransportProtocol=TX_PROTOCOL_TCP;
else
PstruPacket->pstruTransportData->nTransportProtocol=0;
if(NETWORK->ppstruDeviceList[nSensorLoop-1]-
>pstruSocketInterface->pstruSocketBuffer[0]->pstruPacketlist==NULL)
{
fn_NetSim_Packet_AddPacketToList((NETWORK-
>ppstruDeviceList[nSensorLoop-1]->pstruSocketInterface-
>pstruSocketBuffer[0]),PstruPacket,3);
pstruEventDetails->dPacketSize=PstruPacket-
>pstruAppData->dPacketSize;
pstruEventDetails->nDeviceType = SENSOR;
pstruEventDetails->nApplicationId=0;
170
pstruEventDetails->nProtocolId=PstruPacket-
>pstruTransportData->nTransportProtocol;
pstruEventDetails->nDeviceId=(NETSIM_ID)nSensorLoop;
pstruEventDetails->nInterfaceId=0;
pstruEventDetails->nEventType=TRANSPORT_OUT_EVENT;
pstruEventDetails->nSubEventType=0;
pstruEventDetails->pPacket=NULL;
fnpAddEvent(pstruEventDetails);
}
else
{
fn_NetSim_Packet_AddPacketToList((NETWORK-
>ppstruDeviceList[nSensorLoop-1]->pstruSocketInterface-
>pstruSocketBuffer[0]),PstruPacket,2);
}
}
fclose(file_transfer);
return 0;
}
#endif
/** In this function the sensors sense the agent, creates a packet and
forwards it to sink node.*/
int fn_NetSim_Zigbee_SensorEvent(int nSensorLoop,NETSIM_ID
nGlobalPANCoordinatorId,AGENT** pstruAgent,SENSORS* pstru_Sensor,METRICS**
pstruMetrics,NetSim_EVENTDETAILS* pstruEventDetails)
{
int nFlag = 0;
static int nPacketId;
char str[500];
int nAgentLoop;
POS_2D* pstruPos;
double dDistance;
POS_2D* pstruTemppos;
NetSim_PACKET *PstruPacket;
#ifdef _FILE_SEND_
fnsendfile((NETSIM_ID)nSensorLoop);
return 0;
#endif
pstruPos = (POS_2D*)fnpAllocateMemory(sizeof(POS_2D),1);
pstruTemppos = (POS_2D*)fnpAllocateMemory(sizeof(POS_2D),1);
for(nAgentLoop =0;nAgentLoop<MAXAGENT;nAgentLoop++)
{
if(pstruAgent[nAgentLoop] == NULL)
continue;
5. In 802_15_4.c , the code must be modified at specified places in red color. Add the
modified code:
case MAC_IN_EVENT:
{
.
171
if(pstruPacket->nControlDataType/100 != MAC_PROTOCOL_IEEE802_15_4)
{
//Prepare the Network in event details
pstruPacket->pstruMacData->dOverhead -= 5;
pstruPacket->pstruMacData->dPacketSize = pstruPacket-
>pstruMacData->dPayload + pstruPacket->pstruMacData->dOverhead;
pstruEventDetails->dPacketSize = pstruPacket->pstruMacData-
>dPacketSize;
pstruEventDetails->pPacket = pstruPacket;
pstruEventDetails->nEventType = NETWORK_IN_EVENT;
pstruEventDetails->nSubEventType = 0;
pstruEventDetails->nProtocolId =
fn_NetSim_Stack_GetNWProtocol(pstruEventDetails->nDeviceId);
//Add Network in event
fnpAddEvent(pstruEventDetails);
#ifdef _FILE_SEND_
if(pstruPacket->nPacketType == PacketType_Custom)
fnWriteFile(pstruPacket->nPacketId);
#endif
}
else if(pstruPacket->nControlDataType == BEACON_FRAME)
{ ...
6. Copy the input file (file to be transferred) in NetSim bin folder (“C:\Program
Files\NetSim Standard\bin”) and rename it as send.txt.
7. In Sensor.c, user can optionally edit the name of the input file in file_name[] and
output file in outfile_name[] in the code. For example, currently it is receive.txt for
output file.
8. Build Zigbee (Please refer section 7.1) and link the dll to bin folder of NetSim. Take
care to rename the original libZigbee.dll so as to preserve the original binaries of
NetSim
9. Next, to run the code, follow these steps:
In this section we create a sample scenario to transfer file from Sensor to Sink Node in WSN:
Step 1: Create a scenario in NetSim as follows. Make sure the

sensor is dropped first on the environment
Step 2: Run the simulation. (Make sure the input file to be

transferred is present in bin folder of NetSim).
Step 3: Output file should be present in bin folder of NetSim with

the name receive.txt defined earlier in outfile_name[] in Sensor.c.
Note: Due to retransmissions and errors, sometimes the output file is not reproduced
correctly. To get exact file, user has to enable TCP (WSN works on UDP).
172
7.3 Debugging your code
This section is helpful to debug the code which user has written. To write your own code
please refer Section 7.1
7.3.1 Via GUI
Step 1:- Perform the required modification of the protocol source code. Also add getch()
statement inside init function of the modified protocol.
Step 2:- Build the protocol and replace the dll in bin folder in NetSim. Do not close Visual
Studio.
Step 3:- In NetSim, create a network scenario where the protocol is being used. The
simulation won‟t start and will pause (because of getch())
Step 4:- In Visual Studio, put break point inside the source code where you want to debug.
173
Step 5:- Go to “Debug Attach to Process” in Visual studio as shown and attach to
NetSimCore.exe.
Click on Attach.
174
Press enter in the command window .Then control goes to the project and stops at the break
point in the source code as shown below.
All debugging options like step over (F10), step into (F11), step out (Shift + F11),
continue (F5) are available.
After execution of the function, the control goes back to NetSim and then comes back to the
custom code the next time the function is called in the simulation.
To stop debugging and continue execution, remove all breakpoint and press F5 (key). This
then gives the control back to NetSim, for normal execution to continue.
175
7.3.2 Via CLI and co-relating with event trace
Step 1:- Open the Command prompt.
Press “windows+R” and type “cmd”.
Step 2:- To run the NetSim via CLI copy the path where “NetSimCore.exe” is present.
>cd <apppath>
Step 3:- Type the following command.

path><space>-license<space>5053@<Server IP Address> -d
Press enter. Now you can see the following screen.
Step 4:- Open/Create the Project in Visual Studio and put break point inside the source code.
176
Step 5:- Go to “Debug  Attach to Process”
Attach to NetSimCore.exe.
Click on Attach.
Step 6:- Go to command prompt which is already opened in Step 3. Enter the Event Id.
Note: If you don’t want to stop at any event you can specify 0 as event id.
177
Execution will stop at the specified event.
Press enter then control goes to the project and stops at the break point in the source code as
shown below.
All debugging options like step over (F10), step into (F11), step out (Shift + F11),
continue (F5) are available.
After execution of the function, the control goes back to NetSim and then comes back to the
custom code the next time the function is called in the simulation.
178
To stop debugging and continue execution, remove all breakpoint and press F5 (key). This
then gives the control back to NetSim, for normal execution to continue.
Co-relating with Event Generated
To debug your own (custom) code, it is often helpful to know which section of the code (file
name & line number) generated the event under study. There are 2 ways to enable this
feature.
Procedure 1
Step 1: Open configuration.xml file and provide the file name, path and set status as Enable.
Step 2: Run the NetSim via CLI in debug mode (Refer NetSim Help  Running Netsim via
CLI) with –d as the fourth parameters
Press enter
Step 3: Enter -1 as the event ID
179
Upon running, NetSim will write the file name and line number of the source code that
generated each event.
Note: In the above trace file Event Id 2 is triggered inside the 802_22_lib.c file which is
present in Cognitive radio.lib. Since all the lib files are opaque to the end user, you cannot see
the source code of the lib file. However, Event Id 4 is triggered at line number 80 of sch.c file
and you can find the location of the event by opening the sch.c file as shown below.
File name
Line number
180
Procedure 2:
Step 1: Right click on my computer and select Properties.
Step 2: Go to Advanced System setting  Advanced

Tab  Environment Variables
Step 3: Click New. Type “NETSIM_BREAK” as

Variable name and any negative integer as Variable
value. Click OK.
Step 4: Now perform simulation in NetSim (Enable event trace in

GUI) . Upon running, NetSim will write the file name and line number of the source code
that generated each event.
181
7.3.3 Viewing & Accessing variables
Viewing variables while debugging code -
To see the value of a variable, when debugging hover the mouse over the variable
name in the code. A text box with variable contents appears. If the variable is a structure and
contains other variables, then click on the plus sign which is there to the left of the text box.
Users can pin the variable to watch by clicking on the pin icon to the right of that variable in
the text box.
Adding the variable to watch -
Watch the change in the variable as the code progress by right clicking on the variable
& clicking on "add watch" tab. This is useful if to continuously monitor the change in the
variable as the code progresses.
182
Viewing external variables -
During the process of debug users would come across variables that are defined
outside the source file being built as a .dll. Such variables cannot be viewed directly when
added in the watch tab, as this would throw the error
CX0017: Error:symbol “Variable_Name”not found.
In the call stack window one can find the file in which that variable is situated. Right
click on the dll file name in the call stack window, in this case NetworkStack.dll. Then in the
pull down menu which appears, select "load symbols from" and give the path of the
pdb(program database) file.
A program database (.pdb) file, also called a symbol file, maps the identifiers that a
user creates in source files for classes, methods, and other code to the identifiers that are used
in the compiled executablesof the project. The .pdb file also maps the statements in the
source code to the execution instructions in the executables. The debugger uses this
information to determine: the source file and the line number displayed in the Visual Studio
IDE and the location in the executable to stop at when a user sets a breakpoint. A symbol file
also contains the original location of the source files, and optionally, the location of a source
server where the source files can be retrieved from.
When a user debugs a project in the Visual Studio IDE, the debugger knows exactly
where to find the .pdb and source files for the code. If the user wants to debug code outside
their project source code, such as the Windows or third-party code the project calls, the user
has to specify the location of the .pdb (and optionally, the source files of the external code)
and those files need to exactly match the build of the executables.
The pdb files are usually available in NetSim‟s install directory, else write to
support@tetcos.com for the latest copy of these debug files.
183
Note: If the load symbols menu option is greyed, then it means symbols are already loaded
In the watch window, the variable which the user has to watch should be edited by
double clicking on it and prefixing {,,NetworkStack.dll} to the variable name and pressing
enter. (The name of the respective file in which the variable is defined should be mentioned -
in this case NetworkStack.dll).
Prefixing to the variable name
184
Accessing External Variables –
In NetSim, while a scenario is simulated, it is possible to access variables which are

defined in one .dll file from another .dll file. An example is given below showing how a
IEEE802.11 file variable dReceivedPower_mw can be accessed in the DSR file.
The user must modify the files present in <Installed Directory>\src\Simulation as

specified below.
The variable dReceivedPower_mw is defined in a structure stru_802_11_Phy_Var. So the

user will have to access a pointer of type stru_802_11_Phy_Var. In the header file where the
structure definition is given, the following line of code must be written –
_declspec(dllexport) IEEE802_11_PHY_VAR *var1;
In the example, the code line must be written in IEEE802_11_Phy.h file present inside
IEEE802_11 folder.
In the main function where a user wishes to find the dReceivedPower_mw, the variable must
be assigned the respective value. In the above case, the following line of code must be written
inside fn_NetSim_IEEE802_11_PhyIn() function in IEEE802_11_Phy.c file present inside
IEEE802_11 folder.
var1 = DEVICE_PHYVAR(pstruEventDetails->nDeviceId,pstruEventDetails->nInterfaceId);
185
Note that the parameters given in the macro or any function which assigns a value to
the variable must be defined beforehand in the code. Here nDeviceId and nInterfaceId are
defined beforehand.
The solution must be built and the resulting <Installed Directory>\src\Simulation

\Dll\libIEEE802.11.dll file which gets created must be copied in to the NetSim standard bin
folder.
The modified IEEE802_11.h file along with other header files on which it depends
(IEEE802_11.h, IEEE802_11_enum.h, IEEE802_11_HTPhy.h, IEEE802_11_Phy.h,
IEEE802_11_PhyFrame.h,and IEEE802_11e.h), present inside <Installed Directory> \src
\Simulation \IEEE802_11\ folder must be copied and pasted in the DSR solution folder
<Installed Directory>\src\Simulation\DSR and must be included in the DSR solution in visual
studio.
186
The Object file library <Installed Directory>\src\Simulation \Dll\IEEE802_11.lib file
which got created must be copied and pasted in the lib folder located at <Installed
Directory>\src\Simulation.
The IEEE802_11.h header file which was included in DSR solution must be edited and the
line where _declspec(dllexport) IEEE802_11_PHY_VAR *var1; was written must be
replaced with _declspec(dllimport) IEEE802_11_PHY_VAR *var1;
187
For viewing the variable value in the command prompt, the following lines must be
added in DSR.c.
#include “IEEE802_11_Phy.h”
if(var1)
fprintf (stderr,"\n Received Power- %lf\n",var1->dReceivedPower_mw);
188
Now Right click on DSR project  Properties  Linker Input  add IEEE802_11.lib to
the Additional Dependencies.
The solution must be built and the resulting dll file <Installed
Directory>\src\Simulation \Dll\libDSR.dll must be copied and replaced in the NetSim
Standard bin path. When a scenario is run, the Received Power can be seen in the command
prompt.
189
7.4 NetSim API’s
NetSim provides a wide variety of APIs for protocol developers. These are available in
1. packet.h – Packet related APIs (Eg: Create_Packet ( ), Copy_Packet ( ), Free_Packet (
) etc.)
2. stack.h – Network / device / link and event related APIs (Eg: Get_Device_IP ( ),
Get_Connected_Link( ), Add_Event ( ) etc.)
3. list.h, -- Optimized list operation calls since NetSim uses lists extensively (Eg:
Add_to_list ( ), Sort_list ( ) etc.)
4. NetSim_Graph.h – This is used for plotting graphs using GNU plot
5. IP_Addressing.h – For setting & getting IP address per the appropriate format (Eg:
Convert_IP_to_string ( ), Compare_IP( ) etc.)
For detailed help please refer the appropriateheader (.h) files inside:
../NetSim_Standard/src/simulation/include or read through the doxygen source code
documentation available inside NetSim  Help  NetSim source code Help
 Include all the header (.h) files from the include folder
 NetworkStack.lib is a “import library” file and has the definitions for the functions
present in the NetworkStack.dll
 When developing new protocols users should create their own protocol.h and declare
all the protocol specific variables here. Stack & packet related variables should be
used from stack.h and packet.h
NetSim Network Stack calling individual Protocol
Every protocol should provide the following APIs as hooks to the network stack:
 int (*fn_NetSim_protocol_init)(conststruct stru_NetSim_Network*,conststruct
stru_NetSim_EventDetails*,constchar*,constchar*,int,constvoid**);
Using this API the stack passes all the relevant pointers to variables, paths etc needed for
the protocol. Inside this function a) local variables should be initialized, b) Initial events if
any should be written,eg: Hello packet in RIP, STP in Ethernet c) File pointers for
reading & writing protocol_specific_IO files.
 int (*fn_NetSim_protocol_Configure)( conststruct stru_NetSim_Network*, int
nDeviceId, int nINterfaceID, int nlayertype, fnpAllocateMemory, fnpFreeMemory,
fpConfigLog );
190
The stack calls this API when reading the config file. Upon reaching the appropriate
protocol definition in the XML file, the stack calls this and passes all these pointers to the
protocol
 int (*fn_NetSim_protocol_run)(): This is called by the stack to run the protocol
 char* (*fn_NetSim_protocol_trace)(int): This called by the stack to write the event trace
 int (*fn_NetSim_protocol_CopyPacket)(const NetSim_PACKET* pstruDestPacket,const

NetSim_PACKET* pstruSrcPacket):
This is for copying protocol specific parameters / data into the packed
 int (*fn_NetSim_protocol_FreePacket)(const NetSim_PACKET* pstruPacket): The this

to free the protocol specific parameters / data in the packet
 (*fn_NetSim_protocol_Metrics)(const FILE* fpMetrics): This is to write the metrics file

upon completion of the simulation
 int (*fn_NetSim_protocol_Finish)(): To release all memory after completion
 char* (*fn_NetSim_protocol_ConfigPacketTrace)(constvoid* xmlNetSimNode); To

configure the packet packet trace in terms of the parameters to be logged
 char* (*fn_NetSim_protocol_WritePacketTrace)(const NetSim_PACKET*); To

configure the event trace in terms of the parameters to be logged
191
8 Advanced Features
8.1 Random number Generator and Seed Values
All network simulations involve an element of randomness. Some examples are -
a. It is possible to configure the traffic sources in the simulation to generate traffic in a
perfectly regular pattern. However, this is typically not the case in the real world.
b. Node back-off‟s after collisions are random to resolve contention issues
c. The exact bit which is errored, based on Bit error probability of a wireless channel, is
decided randomly
NetSim uses an in-built Linear Congruential Random Number Generator (RNG) to generate
the randomness. The RNG uses two seeds values to initialize the RNG.
Having the same set of seed values ensures that for a particular network configuration the
same output results will be got, irrespective of the PC or the time at which the simulation is
run. This ensures repeatability of experimentation.
Modifying the seed value will lead to the generation of a different set of random numbers and
thereby lead to a different sequence of events in NetSim. When simulations are run for a
network configuration with different seed values, the results will likely be slightly different.
More advanced users get “Confidence” by analyzing a set of results with different seed
values for the same network scenario.
192
8.2 Static Routing
Static routing is a form of routing that occurs when a router uses a manually-configured
routing entry, rather than information from a dynamic routing traffic. In many cases, static
routes are manually configured by a network administrator by adding in entries into a routing
table, though this may not always be the case. Unlike dynamic routing, static routes are fixed
and do not change if the network is changed or reconfigured.
RIP
RIP (Routing Information Protocol) is a well-known and commonly used distance-vector routing
protocol which employs the hop count as a routing metric. Although originally developed for
LANs, RIP can also be used in WANs. RIP prevents routing loops by implementing a limit
on the number of hops allowed in a path from source to destination. The maximum number of
hops allowed for RIP is 15, which limits the size of networks that RIP can support. A hop
count of 16 is considered an infinite distance and the route is considered unreachable. RIP
generally uses the User Datagram Protocol (UDP) as its transport protocol.
OSPF
Open Shortest Path First (OSPF) is a routing protocol for Internet Protocol (IP) networks. It
uses a link state routing algorithm and falls into the group of interior routing protocols,
operating within a single autonomous system. OSPF routes are typically more reliable than
RIP routes. RIP only takes the number of hops into account when computing a route‟s cost,
but OSPF also considers the relative cost of each link used in the route. OSPF usually
computes the cost of a link relative to that link‟s inverse bandwidth. In addition, RIP
networks are limited to 15 hops whereas OSPF allows networks to expand beyond this limit.
How to Setup Static Routes in RIP and OSPF
Using GUI
Step1: Create a scenario in internetworks and set properties of the devices. Configure the
applications.
Step 2: While running the simulation, go to IP and ARP configuration tab and enable Static
IP forwarding and browse the path where it has to be saved.
193
Using CLI
Step1: In internetworks, Static Routes can be set for any scenario having a minimum of 3
routers, 2 switches and 3 wired nodes. The easiest way to do this is to first run the scenario
with routing protocol set as RIP/OSPF. For that, users can go to Router properties 
Application Layer properties  set RIP/OSPF protocols and save the Configuration file.
Step 2: Open the Configuration file with Visual studio. Expand the Protocol configuration
and set the Static Routing information in Application Layer property of the device, by
enabling the Static routing status. Then set the appropriate Static routing file name and file
path.
By default:
<PROTOCOL_CONFIGURATION>
<PROTOCOL NAME="IPV4">
<STATIC_IP_FORWARDING_TABLE FILE="" STATUS="DISABLE"/>
</PROTOCOL>
<PROTOCOL NAME="ARP">
<STATIC_ARP FILE="" STATUS="ENABLE"/>
</PROTOCOL>
</PROTOCOL_CONFIGURATION>
194
Change to:
<PROTOCOL_CONFIGURATION>
<PROTOCOL NAME="IPV4">
<STATIC_IP_FORWARDING_TABLE FILE="C:\Program Files (x86)\NetSim
Pro\Docs\Sample_Configuration\Internetworks\Static Routing Scenario\StaticRouting_TCP.txt"
STATUS="ENABLE"/>
</PROTOCOL>
<PROTOCOL NAME="ARP">
<STATIC_ARP FILE="" STATUS="ENABLE"/>
</PROTOCOL>
</PROTOCOL_CONFIGURATION>
Note:
1. Update this information in any one of the router
2. A sample StaticRouting.txt file will be available inside “C:\Program Files\NetSim

standard\Docs\Sample_Configuration\Internetworks”. Appropriately modify it for the
scenario.
The StaticRouting.txt file contains
1. Device Id
2. List of entries to add in the routing table
DEVICE_ID:1
ROUTE ADD 192.168.0.0 MASK 255.255.255.0 192.168.0.1 METRICS 1 IF 1
DEVICE_ID:2
ROUTE ADD dest_ip MASK subnet_mask gateway_ip METRICS metric_value IF Interface_Id
1. The ROUTE ADD command to add the static route

2. The dest_ip is the Network address for the destination network
3. The MASK is the Subnet mask for the destination network
195
4. The gateway_ip is the IP address of the next-hop router
5. The METRICS is the value used to choose between two routes
6. The IF is the Interface to which the gateway_ip is connected. The default is 1.
Step 3: After this, run this configuration file through CLI and static routes will be used for
routing.
196
8.3 Mobility Models in NetSim
Mobility models represent the movement of mobile user, and how their location, velocity and
acceleration change over time. Such models are frequently used for simulation purposes
when new communication or navigation techniques are investigated, or to evaluate the
performance of mobile wireless systems and the algorithms and protocols at the basis of
them. Typical mobility models provided in NetSim are as follows:
8.3.1 Random Walk mobility model
It is a simple mobility model based on random directions and speeds. In this mobility model,
a mobile node moves from its current location to a new location by randomly choosing a
direction and speed in which to travel. The new speed and direction are both chosen from
pre-defined ranges. Each movement in the Random Walk Mobility Model occurs in either a
constant time interval or a constant distance traveled, at the end of which a new direction and
speed are calculated.
8.3.2 Random Waypoint Mobility Model
It includes pause time between changes in direction and/or speed. A mobile node begins by
staying in one location for a certain period of time (i.e., a pause time). Once this time expires,
the mobile node chooses a random destination in the simulation area and a speed that is
uniformly distributed between [minspeed, maxspeed]. The mobile node then travels toward
the newly chosen destination at the selected speed. Upon arrival, the mobile node pauses for a
specified time period before starting the process again.
8.3.3 Group mobility
It is a model which describes the behavior of mobile nodes as they move together. i.e. the
sensors having common group id will move together.
8.3.4 File Based Mobility
In File Based Mobility, users can write their own custom mobility models and define the
movement of the mobile users. The name of the trace file generated should be kept as
mobility.txt and it should be in the NetSim Mobility File format.
197
The user can also generate the mobility files using external tools like SUMO (Simulation of
Urban MObility), Vanet MobiSim etc.
The NetSim Mobility File format is as follows
Step 1: Create a text file inside <NetSim Installation Directory>\bin and rename it as
“mobility.txt”
Step 2: Open the text file and write the code in format shown below
# To write comments, use # tag
# User needs to specify the total number of Nodes and Environment size as shown below
#nodes: <No. of Nodes> max x = <X_Environment_Size>, max y: <Y_Environment_Size>
#First specify the location of all the devices as per their X, Y and Z Axis
$node_(<Node _ID - 1>) set X_ <Initial X_Coordinate>
$node_(<Node _ ID - 1>) set Y_ <Initial Y_ Coordinate >
$node_(<Node _ ID - 1>) set Z_ <Initial Z_ Coordinate >
#Specify the new location of the specific device at the specific time
$time <Time_in_Secs> "$node_(<Node_ ID - 1>) <X_Coordinate> <Y_ Coordinate > <Z_
Coordinate >"
Step 3: In NetSim, go to MANET and create a Network scenario. Click on Node

properties and in Global properties, set the Mobility Model as “File Based Mobility” and
simulate.
A sample file based mobility experiment is present at <NetSim Installed Directory> \Docs\
Sample_Configuration\ MANET.
A sample mobility.txt file for a MANET network containing 2 nodes is shown below
#
#nodes: 2 max x = 500.0, max y: 500.0
#
$node_(0) set X_ 70.0
$node_(0) set Y_ 70.0
198
$node_(0) set Z_ 0.0
$node_(1) set X_ 150.0
$node_(1) set Y_ 150.0
$node_(1) set Z_ 0.0
$time 0.0 "$node_(0) 70.00 70.00 0.00"
$time 0.0 "$node_(1) 150.0 150.0 0.0"
$time 5.0 "$node_(0) 100.00 70.00 0.00"
$time 5.0 "$node_(1) 150.0 160.0 0.0"
$time 10.0 "$node_(0) 130.00 70.00 0.00"
$time 10.0 "$node_(1) 150.0 170.0 0.0"
$time 15.0 "$node_(0) 160.00 70.00 0.00"
$time 15.0 "$node_(1) 150.0 180.0 0.0"
$time 20.0 "$node_(0) 190.00 70.00 0.00"
$time 20.0 "$node_(1) 150.0 190.0 0.0"
$time 25.0 "$node_(0) 220.00 70.00 0.00"
$time 25.0 "$node_(1) 150.0 200.0 0.0"
$time 30.0 "$node_(0) 250.00 70.00 0.00"
$time 30.0 "$node_(1) 150.0 210.0 0.0"
$time 35.0 "$node_(0) 280.00 70.00 0.00"
$time 35.0 "$node_(1) 150.0 220.0 0.0"
$time 40.0 "$node_(0) 310.00 70.00 0.00"
$time 40.0 "$node_(1) 150.0 230.0 0.0"
$time 45.0 "$node_(0) 340.00 70.00 0.00"
$time 45.0 "$node_(1) 150.0 240.0 0.0"
$time 50.0 "$node_(0) 370.00 70.00 0.00"
$time 50.0 "$node_(1) 150.0 250.0 0.0"
199
8.4 Interfacing MATLAB with NetSim
8.4.1 Implement Nakagami Distribution of MATLAB in NetSim without
using .m file
In this example we will replace the default Rayleigh Fading (part of the path loss calculation)
used in NetSim, with a Fading Power calculated using the Nakagami Distribution from
MATLAB
Procedure:
1) Create a MATLAB_Interface.c file inside the IEEE802_11 folder which can be found
in the path <NetSim_Install_Direcotry>/src/Simulation/. Write the following code inside the
MATLAB_Interface.c file:-
/*
*
* This is a simple program that illustrates how to call the MATLAB
* Engine functions from NetSim C Code.
*
*/
#include <windows.h>
#include <stdlib.h>
#include <stdio.h>
#include <string.h>
#include "engine.h"
#include "mat.h"
#include "mex.h"
char buf[100];
Engine *ep;
int status;
mxArray *h=NULL, *i=NULL, *j=NULL,*k=NULL;
mxArray *out;
double *result;
double fn_netsim_matlab_init()
{
/*
* Start the MATLAB engine
*/
if (!(ep = engOpen(NULL))) {
MessageBox ((HWND)NULL, (LPCWSTR)"Can't start MATLAB engine",
(LPCWSTR) "MATLAB_Interface.c", MB_OK);
exit(-1);
}
engEvalString(ep,"desktop");
return 0;
}
double fn_netsim_matlab_run()
200
{
//write your own implementation here
int nakagami_shape=5,nakagami_scale=2;
engPutVariable(ep,"h",h);
sprintf(buf,"h=ProbDistUnivParam('nakagami',[%d
%d])",nakagami_shape,nakagami_scale);
status=engEvalString(ep,buf);
engPutVariable(ep,"i",i);
sprintf(buf,"i=random(h,1)");
out=engGetVariable(ep,"i");
result=mxGetPr(out);
return *result;
}
double fn_netsim_matlab_finish()
{
status=engEvalString(ep,"exit");
return 0;
}
2) Now open IEEE802_11 project file, inside the IEEE802_11 folder.
201
3) Right click on “IEEE802_11 Project” present in “Solution Explorer” window and
select Add  Existing Item and select the MATLAB_Interface.c file.
4) MATLAB_Interface.c file contains the following functions

a) fn_netsim_matlab_init() - Opens the MATLAB Engine
b) fn_netsim_matlab_run() - Communicates with MATLAB Command
Window
c) fn_netsim_matlab_finish() - Closes the MATLAB Engine
5) In the Solution Explorer double click on the IEEE802_11.c file.
6) Add a call to fn_netsim_matlab_init() inside the fn_NetSim_IEEE802_11_Init()

function.
202
7) Similarly add a call to fn_netsim_matlab_finish() inside the
fn_NetSim_IEEE802_11_Finish() function.
8) In the Solution Explorer double click on the IEEE802_11.h file. Add definitions of
the following functions
double fn_netsim_matlab_init();
double fn_netsim_matlab_run();
double fn_netsim_matlab_finish();
203
9) In the Solution Explorer double click on the PropagationModel.c file.
10) Inside fnCalculateFadingLoss() function comment the lines,

*dFadingPower = log(*dFadingPower);
*dFadingPower= 10*log10(-*dFadingPower);
11) Make a call to the fn_netsim_matlab_run() function by adding the following line,
*dFadingPower = fn_netsim_matlab_run();
12) To compile a MATLAB engine application in the Microsoft Visual Studio 10.0
(2010) environment, Right click on the IEEE802_11 project and select PROPERTIES in the
solution explorer. Once this window has opened, make the following changes:
204
a) Under C/C++  General, add the following directory to the field ADDITIONAL
INCLUDE DIRECTORIES:
<Path where MATLAB is installed>\extern\include
NOTE: To determine path where MATLAB is installed, entering the following command in the
MATLAB command prompt:
matlabroot
b) Under C/C++  Precompiled Headers, set PRECOMPILED HEADERS as "Not

Using Precompiled Headers".
205
c) Under Linker  General, add the directory to the field ADDITIONAL LIBRARY
DIRECTORIES:
<Path where MATLAB is installed>\extern\lib\win32\microsoft
d) Under Configuration Properties Debugging, Add the following Target path in the
ENVIRONMENT:
<Path where MATLAB is installed>\bin\win32
206
13) Under Linker  Input, add the following names to the field marked ADDITIONAL
DEPENDENCIES:
libeng.lib, libmx.lib, libmat.lib
14) Make sure that the following directory is in the environment variable PATH:
<Path where MATLAB is installed>\bin\win32
NOTE: To do step 14, check the Windows system path by clicking on Start  Right click on
Computer  Properties  Advanced System Settings  Environment variables  System
Variables  Open "Path" for editing.
Note: If the machine has more than one MATLAB installed, the directory for the target platform
must be ahead of any other MATLAB directory (for instance, when compiling a 32-bit
application, the directory in the MATLAB 32-bit installation must be the first one on the
PATH).
15) Now Right Click on IEEE802_11 project and select Rebuild.
207
16) Now replace the newly built libIEEE802.11.dll from the DLL folder, into the NetSim
bin folder. Please ensure you rename the original libIEEE802.11.dll file to retain a copy of
the original file.
[For more information, follow steps provided in “Writing your own code: Linking Dlls”
under “Custom Code in NetSim” chapter]
17) Run NetSim in Administrative mode. Create a Network scenario involving

IEEE802_11 say MANET, and set the Fading Figure value in the Multipoint to Multipoint
Link properties to 1, to ensure that Rayleigh fading is set.
18) Perform Simulation. You will find that once the Simulation starts MATLAB
command window starts and gets closed once the simulation is over.
Note: On Windows systems, engOpen opens a COM channel to MATLAB. The

MATLAB software you registered during installation starts. If you did not register
during installation, enter the following command at the MATLAB prompt:
!matlab -regserver
208
8.4.2 Debug and understand communication between NetSim and
MATLAB
1. In the Solution Explorer of Visual Studio double click on IEEE802_11.c and Add a
getch() inside the fn_NetSim_IEEE802_11_Init() function.
2. In the Solution Explorer double click on MATLAB_Interface.c file and place a

breakpoint inside the fn_netsim_matlab_run() function before the return statement.
209
3. Rebuild the Dll and replace in bin path.
4. Now run the NetSim Scenario. The simulation window stops for user interrupt.
5. In Visual studio, go to Debug  Attach to Process.
6. From the list of Processes select NetSimCore.exe and click on Attach.
7. Now go to the Simulation window and press Enter.
8. MATLAB Command Window and MATLAB Desktop Window will start and
breakpoint in Visual Studio gets triggered.
210
9. Now when debugging (say, by pressing F5 each time) you will find the computation
taking place in the MATLAB Workspace.
10. This value of i obtained from MATLAB is used to calculate fading power instead of
the Rayleigh Fading Model.
11. Add a watch to the *dFadingPower variable in the PropagationModel.c file. For this,
right click on the variable *dFadingPower and select “Add Watch” option. You will find a
watch window containing the variable name and its value in the bottom left corner.
211
12. Now place another breakpoint after the line *dFadingPower = fn_netsim_matlab_run()
13. Now when debugging (say by pressing F5 each time) you will find that the watch
window displays the value of *dFadingPower whenever the control reaches the recently set
breakpoint. You will also find that the value of *dFadingPower in the Visual Studio Watch
window and the value of i in the MATLAB workspace window are similar.
212
8.4.3 Implement Nakagami Distribution of MATLAB in NetSim using
.m file:
Procedure:
1. From the NetSim_MATLAB_Interface.zip, Copy and paste

NetSim_MATLAB_Interface /Example1a /nakagami.m file inside <Path where MATLAB is
installed>. The nakagami.m file contains the following code:
function WLAN=nakagami(scale,shape)
h=ProbDistUnivParam('nakagami',[scale,shape]);
i=random(h,1);
WLAN=i;
NOTE: To determine path where MATLAB is installed, entering the following command in the
MATLAB command prompt:
matlabroot
2. From the NetSim_MATLAB_Interface.zip, Copy and Paste

NetSim_MATLAB_Interface /Example1a/ MATLAB_Interface.c file inside the
IEEE802_11 folder.
Replace the MATLAB_Interface.c file used for “Implement Nakagami Distribution of
MATLAB in NetSim without using .m file” (incase if you have performed that section
before).
3. Follow steps 2 to 14 as given in “Implement Nakagami Distribution of MATLAB in

NetSim without using .m file”.
213
4. Now double click on MATLAB_Interface.c file in the Solution Explorer if a link
exists, else right click on IEEE802_11 project and select add existing item to add the file to
the project.
5. Go to the fn_netsim_matlab_run() function
double fn_netsim_matlab_run()
{
sprintf(buf,"k=nakagami(%d,%d)",nakagami_shape,nakagami_scale);
out=engGetVariable(ep,"k");
return *result;
}
6. A call to the nakagami() function inside the nakagami.m file is made, and
nakagami_shape and nakagami_scale parameters are passed from NetSim.
7. Right Click on IEEE802_11 project and select Rebuild.
8. Replace the newly build libIEEE802.11.dll from the DLL folder in the NetSim bin
folder after renaming the original libIEEE802.11.dll file.
9. Create a Network scenario involving IEEE802_11 say MANET, and set the Fading
Figure value in the Multipoint to Multipoint Link properties to 1 to ensure that Rayleigh
fading is set.
10. You will find that once the Simulation is run MATLAB Command Window starts and
gets closed once the Simulation is over.
You can also debug the code to understand the communication between NetSim and
MATLAB as explained in the DEBUGGING section above.
214
8.4.4 Plot a histogram in MATLAB using the values generated by
Nakagami distribution for NetSim (using .m file)
Procedure:
1. From the NetSim_MATLAB_Interface.zip, Copy and paste

NetSim_MATLAB_Interface/Example1b/NetSim_MATLAB.m file inside
$MATLABROOT.
The NETSIM_MATLAB.m file contains the following code:
function WLAN=NETSIM_MATLAB(choice,varargin)
switch(choice)
case 'nakagami'
h=ProbDistUnivParam('nakagami',[varargin{1},varargin{2}]);
i=random(h,1);
fid = fopen('plotvalues.txt','a+');
fprintf(fid,'%f',i);
fprintf(fid,'\r\n');
fclose('all');
WLAN=i;
case 'plothistogram'
fid=fopen('plotvalues.txt');
mx=fscanf(fid,'%f');
hist(mx);
fclose('all');
end
2. From the NetSim_MATLAB_Interface.zip, Copy and Paste

NetSim_MATLAB_Interface/Example1b/ MATLAB_Interface.c file inside the IEEE802_11
folder. Replace the MATLAB_Interface.c file if it already exists.
3. Follow steps 2 to 14 as given in Example 1
215
4. Now double click on MATLAB_Interface.c file in the Solution Explorer if a link
exists, else right click on IEEE802_11 project and select add existing item to add the file to
the project.
5. Go to the fn_netsim_matlab() function
double fn_netsim_matlab(char *arr)

{
if(strcmp(arr,"nakagami")==0)
{
engPutVariable(ep,"h",h);
sprintf(buf,"h=NETSIM_MATLAB('nakagami',%d,%d)",nakagami_shape,nakagami_scale);
out=engGetVariable(ep,"h");
return *result;
}
else if(strcmp(arr,"plothistogram")==0)
{
status=engEvalString(ep,"NETSIM_MATLAB('plothistogram')");
return 0;
}
else
return 0;
}
6. A call to the NetSim_MATLAB() function inside the NetSim_MATLAB.m file is

made, for fading power calculation with parameters distribution(„nakagami‟),
nakagami_shape and nakagami_scale parameters are passed from NetSim.
7. A call to the NetSim_MATLAB() function inside the NetSim_MATLAB.m file is

made, for plotting histogram for the values generated by MATLAB..
8. Also add the following call to fn_netsim_matlab_run() function along with a getch()
to plot the histogram before closing the MATLAB Engine.
216
9. Similarly in the call made to fn_netsim_matlab_run() function in PropagationModel.c
file add the parameter “nakagami” as shown below:-
10. Also modify the function definition of fn_netsim_matlab_run() function in

IEEE802_11.h file as shown below:-
217
11. Right Click on IEEE802_11 project and select Rebuild.
12. Now Replace the newly build libIEEE802.11.dll from the DLL folder in the NetSim
bin folder after renaming the original libIEEE802.11.dll file.
13. Create a Network scenario involving IEEE802_11 say MANET, and set the Fading
Figure value in the Multipoint to Multipoint Link properties to 1 to ensure that Rayleigh
fading is set.
14. You will find that once the Simulation is run MATLAB Command Window starts and
once the Simulation is over a histogram is displayed in MATLAB for the values that were
generated using nakagami distribution.
15. The graph and the MATLAB windows gets closed once you press any key.
You can also debug the code to understand the communication between NetSim and
MATLAB as explained in the DEBUGGING section above.
218
8.5 Adding Custom Performance Metrics
In Performance Metrics, users have the latitude of adding their own customized metric
variables by editing the source code of the protocol of that specific networking technology.
The following example provides a better understanding of how to implement it.
For illustration, an example regarding Wireless Sensor Network is provided. In this example,
users will print Sensor Node Name, Residual Energy, State (On/Off) and turn–off time in the
performance metrics
STEP 1: Copy the provided code at the top in 802_15_4.h file
#include "string.h"
double NetSim_Residual_Energy[100];
string NetSim_Node_name[100];
double NetSim_Off_Time[100];
string NetSim_Node_state[100];
STEP 2:
Copy the below code (in red colour) in 802_15_4.c file (inside fn_NetSim_Zigbee_Metrics()
function)
_declspec(dllexport) int fn_NetSim_Zigbee_Metrics(char* szMetrics)

{
FILE* fp;
int i;
NETSIM_ID nDeviceCount = NETWORK->nDeviceCount;
fp=fopen(szMetrics,"a+");
fprintf (fp,"#Custom WSN Metrics\n");
fprintf (fp,"Node Name\tStatus\tTime\tResidual_Energy\n");
for (i = 1; i <= nDeviceCount; i++)
{
NetSim_Residual_Energy[i-1]=pstruDevicePower[i-1]->dRemainingPower;
fprintf(fp,"%s\t%s\t%lf\t%lf\n",NetSim_Node_name[i-1],
NetSim_Node_state[i-1], NetSim_Off_Time[i-1], NetSim_Residual_Energy[i-1]);
}
fclose(fp);
return fn_NetSim_Zigbee_Metrics_F(szMetrics);
}
219
STEP 3:
Copy the below code (in red colour) at the end of ChangeRadioState.c file (inside IF(nStatus)
loop)
if(nStatus)
{
WSN_PHY(nDeviceId)->nOldState = nOldState;
WSN_PHY(nDeviceId)->nRadioState = nNewState;
NetSim_Node_state[nDeviceId-1]= "ON";
NetSim_Node_name[nDeviceId-1]= NETWORK->ppstruDeviceList[nDeviceId-1]-
>szDeviceName;
return nStatus;
}
else
{
WSN_PHY(nDeviceId)->nRadioState = RX_OFF;
WSN_MAC(nDeviceId)->nNodeStatus = OFF;
NetSim_Off_Time[nDeviceId-1] = ldEventTime;
NetSim_Node_state[nDeviceId-1]= "OFF";
NetSim_Node_name[nDeviceId-1]= NETWORK->ppstruDeviceList[nDeviceId-1]-
>szDeviceName;
return nStatus;
}
STEP 4:
Build DLL with the modified code and run a Wireless Sensor Network scenario.
After Simulation, user will notice a new Performance metrics named “Custom WSN
Metrics” is added.
220
9 Programming Exercises
This menu contains network programming exercises and is not available in Pro version.
Run down the menu and select the desired programming exercise. The programs available are
as follows,
 Assignments of Sites to Concentrator
 Address Resolution Protocol
 Cryptography
o Substitution
o Transposition
o XOR
o Advanced
 Data Encryption Standard
 RSA
 Wired Equivalent Privacy
 Distance Vector Routing
 Dynamic Host Configuration Protocol
 Error Correcting Code
o Hamming Code
 Error Detecting Codes
o Cyclic Redundancy Check
o Longitudinal Redundancy Check
 Framing Sequence
o Bit Stuffing
o Character Stuffing
 Generic Cell Rate Algorithm
o Virtual Scheduling Algorithm
 IPV4 Addressing
o Address Mask
o Binary Conversion
o Classless InterDomain Routing
o Network Address
o Special Addresses
221
o Subnetting
 IPV6 Addressing
o EUI - 64 Interface Identifier
o Host Addresses
o Subnetting
 Leaky Bucket Algorithm
 Multi Level Multi Access
 Multiple Access Technology
o CDMA
o TDMA
o OFDMA
 PC to PC Communication
o Socket Programming
o Chat Application
 Scheduling
 Shortest Path
 Sliding Window Protocol
 Sorting Techniques
 Spanning Tree
 Transmission Flow Control
NetSim‟s Programming Lab has been designed to provide hands - on network programming
skills to students. The labs come with a GUI where students can first run the experiment in
“Sample mode” and subsequently link their own code and visualize it‟s working. Programs
can be written in C and the executable can be linked to NetSim.
222
9.1 Architecture
The following Architecture is applicable for all the exercises under the Programming
menu. Each exercise has two modules
Using the Input - Output module inputs are given and output is viewed. The working of the
concept/algorithm is done in the process module. The link between the Input - Output
module and process module is as follows
Input - Output Process
Input Text file

Input Read Input
(Input.txt)
Process
Output Output Text file

(Output.txt) Write Output
Process is the module for which the user has to write and link the written code when using the
user mode.
The code can be written either by C or C++, the executable file created should be linked to
the software.
The input and output file format should be as required, as they form the link between the
software and the user executable file.
223
9.2 Creating .exe file for Programming Exercise
9.2.1 Using Visual Studio
1. Select FileNewProject
2. Select Win32Console Application. Name the project and select location to save the
project and then click OK button.
224
3. Click Next Check Whether Console application is selected or not. If selected, then
select Empty Project, otherwise select Console application and Empty Project and
finally click Finish button.
4. Add source codes to the project. Right click on the Source FilesAddNew Item
225
5. Select C++ File (.cpp) and name the file with extension of .c
6. Now Source file is created
226
7. Copy and paste the source code.
8. Select the mode for creating the exe i.e., debug or release mode by choosing the
required option as shown in the figure. The preferred setting is debug mode.
227
9. To build the Solution,Select Build Menu Build Solution
10. Now, Exe is created in the Project Folder as shown below.
228
9.2.2 Using GCC
 By using Command Prompt:
C / C++ files can be created using any editor. Ex: Notepad
Once C / C++ file is ready go to command prompt using Start  Run.
There are three cases for creating Exe (.exe) file using GCC.
Case 1: C programs
1. Set the path as C program path
2. Create Output file (.o file) using the command

gcc - C Filename.c
3. Create exe file (.exe file) using the command

gcc -o filename filename.o
4. Once exe file is created link that exe file with NetSim  Programming  User mode
229
Case 2: C++ programs
1. Set the path as C++ program path.
2. Create output file (.o file) using the command.

g++ -C Filename.c
3. Create exe file (.exe file) using the command

g++ -o filename filename.o
Case 3: Socket programs
1. Set the path to Socket program location.
2. Create output file (.o file) using below command.

gcc -C Filename.c
230
3. Create exe file (.exe file) using below command
gcc -o send send.o -lws2_32
9.2.3 Using Dev C++
1. Open the C source code file in Dev C++. Then go to Execute  Compile.
Dev C++ will create the exe file in the same location where the C source code file is
located
2. Once exe file is created , link that exe file with NetSim  Programming  User mode
Note: For Windows 8 and above, use Dev C++ v 5.11
231
Note: For Windows Vista, set up Dev C++ as shown below
In Dev C++ 4.9.9.2.exe, go to Tools Compiler Options  Directories tab  Binaries tab
Add the following path as per your installation directory in the text box provided and click on
add button.
C:\Dev-Cpp\libexec\gcc\mingw32\3.4.2
In the C Includes tab add the follwing path in the text box provided and click on add button.
C:\Dev-Cpp\lib\gcc\mingw32\3.4.2\include
232
In the programs tab edit the following paths as shown in screenshot.
233
9.3 Steps to perform Programming Exercise in NetSim
In NetSim, select “Programming  < The exercise you want > ”.
Step 1:
In the left panel, select the Mode as Sample. Provide the required inputs in the panel and
click on Run.
So presently NetSim will run that algorithm code already present in the software and will
display the result graphically.
Step 2:
For user to write their own C Code in NetSim and check the result, click on “Concept
Algorithm Pseudo Code and Flowchart” (present in Help in the left pane) and understand the
working of the algorithm.
Step 3:
Then click on Interface Source Code (present in Help in the left pane).
Open Dev C++ or any GNU C compiler based IDK and copy the code from the Interface
Source Code.
The user needs to edit the Interface Source Code at the following location. For Example,
int fnCrc12(char* pszString)

{
// Write your own code here
}
So the user needs to write the code, create exe and attach it with NetSim to run.
Step 4:
Create .exe file. In the left panel, select the Mode as User. Select the .exe file created above.
Set the input and click Run. So presently NetSim will run code which is written by the user
and will display the result graphically.
In case of any error, “ERROR IN USER CODE” message will be displayed.
234
9.4 How to De-bug your code linked to NetSim’s
Programming Exercise
In NetSim, programming exercise menu, users can write and link their code as executables
(*.exe). If the user‟s *.exe file does not provide the correct output, NetSim UI will display the
message “Error in User Code”. To de-bug your code on getting this message, follow the steps
given below:
1. Run the scenario again in sample mode. On completion, minimize NetSim and keep it
running without closing the programming exercise.
2. Open your code in Visual studio 2010.The procedure is explained above in “Creating.exe
file for Programming Exercises”.
3. Right click on your project in the Solution Explorer pane and select properties as shown
below
235
4. Inside the properties window select Debugging and edit the Command Arguments as
shown
5. Inside command argument add the following two paths

a. Path to where NetSim is installed within double quotes “ “. This is usually
C:\Program Files\NetSim Standard. This can be got by right clicking on the NetSim
icon and selecting Find target or open file location.
b. The windows temporary path which has the NetSim folder for temporary data. This
can be got by Start  Run and typing %temp%/NetSim
c. On clicking this, you will get a path similar to C:\Users\George\Local Settings

\Temp\NetSim. As mentioned above, this should also be in double quotes “ “, and
there should be a single space between the first path and the second path.For example:
"C:\Program Files (x86)\NetSim Standard\bin\NetSim.exe" "C:\Users\George
\AppData \Local \Temp\NetSim”
236
6. Now add a breakpoint to your code in your function or in the main ( ), and proceed with
de-bugging
7. At the end check if the output.txt present in the %temp%\NetSim path and the temp.txt
present in the %temp%\NetSim path are exactly similar. Exact similarity would indicate
that your code will work fine when you run it in use mode the next time.
237
9.5 Programming Exercises
9.5.1 Address Resolution Protocol
Programming Guidelines
This section guides the user to link his/her own code for Address Resolution Protocol to
NetSim.
Pre - Conditions
The user program should read the input from text file named „Input‟ with extension txt.
The user program after executing the concept should write the required output to a file named
„Output’ with extension txt.
Note: The temporary directory is navigated through the following step.
Run Type "%temp%"  NetSim  "Input.txt" and "Output.txt"
General Program Flow
The program begins with the Reading of the Inputs from the input file Input.txt.
Executing the required concept and
The results of the program should be written into the output file Output.txt.
Input File Format Output File Format
The first line of the Input.txt contains the The output file should contain two lines,
number of nodes in the network, following The first line has the details of the Source
which the IP Addresses are assigned to each (i.e.) in which class it is present. The second
node (ascending order). The last two lines are line has the result of the ARP i.e., whether
the Source node IP Address and the destination is present in the class.
Destination node IP Address respectively.
An example format of input.txtis given below, The second line has the flag value
(important) that is used for the animation.
Number_of_Nodes=3
The result for the above is:
Node1_IP_Address=192.168.1.1
Node2_IP_Address=192.168.1.2 Source is Class C.Destination is present in
Node3_IP_Address=192.168.1.3 that class 2
Source_Node_IP_ Address=192.168.1.3
Destination_Node_IP_Address=192.168.1.1
238
Interface Source Code
Interface Source code written in C is given and using this the user can write only the Address
Resolution Protocol inside the function fnARP () using the variables already declared.
To view the interface source code, go to NetSim Installation path / src / Programming /
ARP.c
To find NetSim‟s Installation path right click NetSim icon and select
 Open file location in Windows 7/8/10
Sample Scenario:
Objective - To find the Medium Access Control (MAC) Address of the Destination Node
using Address Resolution Protocol (ARP).
How to Proceed? - The objective can be executed in NetSim by using the programming
exercise available. In the Programming menu select Address Resolution Protocol(ARP).
Sample Input - By using the Input Panel that is available on the left hand side a Sample
Scenario is created. The Steps involved in creating are as follows,
 Sample Mode should be selected.

 Click on the drop down button and select 6 Nodes.
 List of NodesNumbers along with their IPAddresses that would be availed are,
Node Numbers IP Address
1 192.168.1.1
2 192.168.1.2
3 192.168.1.3
4 192.168.1.4
5 192.168.1.5
6 192.168.1.6
 ARP Request System and ARP Reply System needs to be selected. That is,
1. ARP Request System 192.168.1. “1” (Any one Node Number to be
selected)
2. ARP Reply System 192.168.1. “6” (Any one Node Number to be selected)
 Then Run button need to be clicked.
Output - Output for the above Sample is as follows,
239
 The Source Node (i.e. Node Number 1 in the above example) sends the ARP
Request to the Connecting Device.
 The Connecting Device then broadcasts the ARP Request to all the Nodes
available in the network.
 The Destination Node (i.e. Node Number 6 in the above example) sends an
acknowledgement in the form of ARP Reply (i.e. The Destination MAC -
MAC Address of the Destination Node) to the Connecting Device.
 The Device then transmits the ARP Reply (i.e. The Destination MAC - MAC
Address of the Destination Node) only to the Source Node.
 Once the sample experiment is done, then Refresh button can be clicked to
create new samples.
240
9.5.2 Assignment of Sites to Concentrator
This section guides the user to link his/her own code for Assignment of Sites to Concentrator
to NetSim.
Pre - Conditions
The user program should read the inputted scenario from text file named „Input‟ with
extension txt.
Note:The temporary directory is navigated through the following step.
Executing the required concept and,
Input file format Output file format
Input.txt contains the number of sites, In the output file (i.e. „Output.txt‟) each line
number of concentrators, and number of should indicate one complete traverse. For
sites that can be assigned to a concentrator, example, for the above input, the output file
the order in which sites are to be assigned should be:
and the distance matrix given by the user. 2>1>
The format of input.txtis:
1>2>
Number_of_Sites=2
In each line, the first character indicates the
Number_of_Concentrators=2 site and the rest indicates the concentrators.
Sites_per_Concentrator=1 The second character (excluding the „>‟
symbol) is the first concentrator found with
Selected_Priority=1>0>
minimum distance/cost. The third character
Distance is a concentrator, which has the minimum
1>2> distance/cost compared to the previous one
and so on.
3>4>
Note:„>‟ is the delimiter symbol, which is
Note: „>‟ is the delimiter symbol, which is used to separate each input.
used to separate each input.
241
Interface Source code code written in C is given using this the user can write only the
Assignments of Sites to Concentrators inside the function fnAssignmentsofSites() using the
variables already declared.
To view the interface source code, go to
NetSim Installation path / src / Programming/ AssignSites.c
Sample Scenarios:
Objective - To allocate the resource which is concentrator to the require system which is
sites based on the distance for each sites to concentrator.
How to proceed? - The objective can be executed in NetSim using the programming exercise
available, under programming user has to select Assignment of Sites to Concentrator.
 Number of Sites need to be selected. The value that has selected ranges from 1 to
7.
 Number of Concentrators need to be selected. The values available for selection
are 2, 3 and 4.
 Number of Sites / Concentrators need to be selected. The value that has selected
ranges from 1 to 7.
 Click on the image to select Priority. Click on Change Priority to reset the
Priority of the Sites.
 Enter the Distance in the given table. Distance should be in the range, 1 to 99 km.
 Then Run button need to be clicked. Refresh button can be used if new Inputs
have to be given.
 Click on Concept, Algorithm, Pseudo Code & Flow Chart to get help on it.
Output - The following steps are under gone internally,
242
 The site which has the highest priority searches for a concentrator which is the
nearest.
 A red line appears between the site and a concentrator. This indicates the only
shortest path available between the site and the concentrators. Hence, it
indicates the site has been allocated to that concentrator.
 A site can have only one concentrator, whereas a concentrator can have many
sites linked to it.
create New Samples.
243
9.5.3 Cryptography - Substitution - Encryption
This section guides the user to link his/her own code for Substitution to NetSim.
Pre-conditions
extension txt.
Executing the required concept and, the results of the program should be written into the
output file Output.txt.
There are six lines in Input.txt file. Plain letter>encrypted letter for the
corresponding plain letter>
Cryptographic_Technique=Substitution
t>u>v>
Cryptographic_Method=Encryption
e>f>g>
Plain_Text:
t>u>v>
tetcos
c>d>e>
Key_Text:
o>p>q>
2
s>t>u>
244
Interface Source code written in C is given using this the user can write only the Substitution-
Encryption inside the function fnSubstutionEncryption () using the variables already
declared.
NetSim Installation path / src / Programming/ SubstEncrypt.c
245
9.5.4 Cryptography - Substitution - Decryption
This section guides the user to link his/her own code for Substitution to NetSim.
Pre - Conditions
extension txt.
There are six lines in Input.txt file. Cipher letter>decrypted letter for the
corresponding cipher letter>
Cryptographic_Technique=Substitution
v>u>t>
Cryptographic_Method=Decryption
g>f>e>
Cipher_Text:
v>u>t>
vgvequ
e>d>c>
Key_Text:
q>p>o>
2
u>t>s>
Interface Source code written in C is given using this the user can write only the Substitution-
Decryption inside the function SubstutionDecryption () using the variables already declared.
246
NetSim Installation path / src / Programming/ SubstDecrypt.c
Sample Scenarios:
Objective - Encrypt and decrypt the message with the same key value using Substitution.
How to Proceed? - The objective can be executed in NetSim using the programming
exercise available. Under programming user has to select Cryptography  Substitution.
 Encryption:
Sample Input: In the Input panel the following steps need to be done,
 SampleMode should be selected.
 Encryption need to be selected.
 Enter the Plain Text that needs to be encrypted. Maximum of 8 alphabets need
to be entered.
 Enter the Key Value. This is an Integer which is within the range 0 to 26.
 Then Run button need to be clicked. Refresh button can be used if new
Inputs have to be given.
 The Plain Text and Key Value entered would be displayed in red color.
 The corresponding Cipher Text would be obtained.
create New Samples.
 Decryption:
 Decryption need to be selected.
247
 Cipher Text obtained while encryption is filled in the Plain Text and also the
Key Text is same as that entered while encrypting.
 The Cipher Text and Key Value entered would be displayed in red color.
 The corresponding Plain Text that had been entered at the time of encrypting is
obtained.
create New Samples.
248
9.5.5 Cryptography - Transposition - Encryption
This section guides the user to link his/her own code for Transposition Encryption to NetSim.
Pre-conditions
extension txt. The user program after executing the concept should write the required output
to a file named „Output’ with extension txt.
Cryptographic_Technique=Transposition 1>3>4>5>2>
Cryptographic_Method=Encryption T>E>T>C>O>S>T>E>T>C>
Plain_Text: T>S>O>C>E>T>T>E>C>T>
TETCOS
Key_Text:
BLORE
Interface Source code written in C is given using this the user can write only the
Transposition-Encryption inside the function fnTranspositionEncryption() using the variables
already declared.
NetSim Installation path / src / Programming/ TranspEncrypt.c
249
9.5.6 Cryptography - Transposition – Decryption
This section guides the user to link his/her own code for Transposition Decryption to NetSim.
Pre - Conditions
Cryptographic_Technique=Transposition BELOR>
Cryptographic_Method=Decryption 1>5>2>3>4>
Cipher_Text: T>O>E>T>C>S>C>T>E>T>
TSOCETTECT
Key_Text:
BLORE
Interface Source code written in C is given using this the user can write only the
Transposition-Decryption inside the function fnTranspositionDecryption() using the variables
already declared.
NetSim Installation path / src / Programming/ TranspDecrypt.c
250
Sample Scenarios:
Objective - Encrypt and decrypt the message with the same key text using Transposition.
exercise available. Under programming user has to select Cryptography  Transposition.
 Encryption:
 Enter the Cipher Text. Maximum of 14 Characters can be entered.
 Enter the Key Value. Maximum of 8 alphabets can be entered.
 The entered Key Value would be displayed first.
 The order of the Key Value is internally sensed.
 The corresponding Cipher Text is obtained.
 Once the sample experiment is done, then Refresh button can be clicked
to create New Samples.
 Decryption:
 Once Encryption is done Decryption has to be selected.
 The Cipher Text obtained for Encryption is the Cipher Text for
Decryption. This would be automatically taken. Maximum of 14
Characters can be entered.
 Enter the Key Value will also be taken internally. Maximum of 8 alphabets
can be entered.
251
 The entered Key Value would be displayed first. This is arranged in such a
way that the order is changed when compared to Encryption.
 The order of the Key Value is internally sensed.
 The corresponding Plain Text is obtained. This Plain Text would be

similar to the Plain Text entered at the time of Encryption.
252
9.5.7 Cryptography - XOR - Encryption
This section guides the user to link his/her own code for XOR Encryption to NetSim.
Pre - Conditions
extension txt.

Cryptographic_Technique=XOR 01010100>01000010>00010110>
Cryptographic_Method=Encryption 01000101>01001110>00001011>
Plain_Text: 01010100>01001100>00011000>
TETCOS 01000011>01001111>00001100>
Key_Text: 01001111>01010010>00011101>
BNLORE 01010011>01000101>00010110>
Interface Source code written in C is given using this the user can write only the XOR-
Encryption inside the function fnXOREncryption () using the variables already declared.
NetSim Installation path / src / Programming/ XorEncrypt.c
253
9.5.8 Cryptography - XOR - Decryption
This section guides the user to link his/her own code for XOR Decryption to NetSim.
Pre - Conditions
extension txt.
Run Type"%temp%"NetSim "Input.txt" and "Output.txt"
Cryptographic_Technique=XOR 00010110>01000010>01010100>
Cryptographic_Method=Decryption 00001011>01001110>01000101>
Cipher_Text: 00011000>01001100>01010100>
00010110000010110001100000001100000 00001100>01001111>01000011>
1110100010110 00011101>01010010>01001111>
Key_Text: 00010110>01000101>01010011>
BNLORE
Here a skeleton code written in C is given using this the user can write only the XOR-
Decryption inside the function fnXORDecryption () using the variables already declared.
NetSim Installation path / src / Programming/ XorDecrypt.c
254
Sample Scenarios:
Objective - Encrypt and Decrypt the message by using the same KeyText in XOR.
exercise available. In the Programming menu select Cryptography XOR.
Note:Encryption should be done first and then Decryption should be done.
 Encryption:
Sample Inputs - By using the InputPanel that is available on the left hand side a
SampleScenario is created. The Steps involved in creating are as follows,
o SampleMode should be selected.
o EncryptionMode needs to be selected.
o PlainText and KeyValue need to be entered in the fields available. That
is,
 Plain Text tetcos (Maximum of 8 Characters)
 Key Text  123456 (Maximum of 8 Characters)
Note: If the length of the PlainText and Key Value differs then an error
would pop out.
o Then Run button need to be clicked.
o Plain Text  t e t c o s
o Key Text  1 2 3 4 5 6
o Binary of plain text  01110011
o Binary of key text  00110110
o XOR Value  01000101
o ASCII Equivalent  69 87 71 87 90 69
o Cipher Text E W G W Z E
 Decryption:
255
Sample Inputs - By using the InputPanel that is available on the left hand side a Sample
o After completing the Encryption part, DecryptionMode needs to be
selected.
o CipherText (this field is automatically filled) and KeyValue (this should
be same as the one that is entered in Encryption) need to be entered in the
fields available. That is,
 CipherText
010001010101011101000111010101110101101001000101 (Cipher
Text in Binary Format Maximum 64 bits)
 KeyText 123456 (Maximum of 8 Characters)
Note - Both Cipher Text and Key Text is automatically taken when
Decryption button is selected (i.e. after undergoing Encryption).
o Cipher Text E W G W Z E
o Key Text  1 2 3 4 5 6
o Binary of cipher text  01000101
o Binary of key text  00110110
o XOR Value  01110011
o ASCII Equivalent  116 101 116 99 111 115
o Plain Text  t e t c o s
Note -
o Text in the Input of the Encryption and Output of the Decryption
should be the same if the Key Value is same.
o The Cipher Text in case of Encryption is Alpha Numeric (i.e. for the
user to understand in a better manner)and in case of Decryption the tool
converts it to Binary form (i.e. since, the tool doesn‟t recognize Alpha
Numeric).
256
9.5.9 Cryptography - Data Encryption Standard (DES) - Encryption
This section guides the user to link his/her own code for DES Encryption to NetSim.
Pre - Conditions
extension txt.
Executing the required concept and,The results of the program should be written into the
257
6bit - 4 Bit conversion logic (in each S-Box):
Of the 6 input bits, 4 bits (1, 2, 3, and 4) are used for identifying the S-Box column (4 bits
representing 16 columns) and the remaining 2 bits (0, 5) are used for identifying the S-Box
row (2 bits representing 4 rows). The corresponding hexadecimal number is chosen from the
S-box. Since each Hexadecimal number represents 4 bits in binary form, the total output is of
32 bits.
258
Cryptographic_Method=Encryption The number of lines present depends on the number of

iterations chosen. The number of lines equals the number
Key_Text=abcdef1234567890
of iterations, plus one. The last line of inputs gives the
No_of_Iterations=1 data (encrypted data if encryption has been chosen, else
Data=tetcos the decrypted data
if decryption has been chosen). The previous lines give
the DES Key generated for encryption or decryption.
1101010101111100100110101100001011100110000110
01616075733F724B40
Interface Source code written in C is given using this the user can write only the DES-
Encryption inside the function fnDESEncryption() using the variables already declared.
NetSim Installation path / src / Programming/ DesEncrypt.c
259
9.5.10 Cryptography - Data Encryption Standard (DES) - Decryption
This section guides the user to link his/her own code for DES Decryption to NetSim.
Pre - Conditions
extension txt.
260
6bit - 4 Bit conversion logic (in each S-Box):
Of the 6 input bits, 4 bits (1, 2, 3, 4) are used for identifying the S-Box column (4 bits
representing 16 columns) and the remaining 2 bits (0, 5) are used for identifying the S-
Box row (2 bits representing 4 rows). The corresponding hexadecimal number is chosen from
the S-box. Since each Hexadecimal number represents 4 bits in binary form, the total output
is of 32 bits.
261
Cryptographic_Method=Decryption The number of lines present depends on the number of

iterations chosen. The number of lines equals the number of
Key_Text=abcdef1234567890
iterations, plus one. The last line of inputs gives the data
No_of_Iterations=1 (encrypted data if encryption has been chosen, else the
Data=616075733F724B40 decrypted data if decryption has been chosen). The previous
lines give the DES Key generated for encryption or
decryption.
110101010111110010011010110000101110011000011001
tetcos
Interface Source code written in C is given using this the user can write only the DES-
Decryption inside the function fnDESDecryption () using the variables already declared.
NetSim Installation path / src / Programming/ DesDecrypt.c
Sample Scenarios:
Objective - Encrypt and decrypt the message with the using DES.
exercise available. Under programming user has to select
CryptographyAdvancedDataEncryptionStandard.
 Encryption:
Sample Inputs - In the Input panel the following steps need to be done,
 Enter the Key Text in the provided field. Only hexadecimal characters
have to be entered. Maximum of 16 characters can be entered in this field.
Characters more than 16 will be filled in the Data field.
262
 Number of Iterations need to be selected. The value ranges from 1 to 16.
 Data needs to be entered in this field that has to be encrypted. Data can be
entered only when the Enter Key Text field is filed with 16 hexadecimal
characters. Maximum of 1500 characters can be stuffed into this field.
Output -
 Key1 (i.e. if Iteration is 1) in binary format is obtained.
 The corresponding Cipher text is obtained.
 Click on Copy button and then on the Paste button to make use of the
Cipher text for Decryption.
 Decryption:
 Once the Encryption is done, click on Copy and Paste buttons. The
encrypted data is filled in the data field available in the Decryption view.
 Fields such as Enter the Key Text, Number of Iteration and Data is filled
in automatically when Copy and Paste button is clicked.
 Key1 (i.e. if Iteration is 1) in binary format is obtained.
 The Data that was entered in the Encryption view would be encrypted and
displayed.
create New Samples.
263
9.5.11 Rivest-Shamir - Adleman Algorithm (RSA)
This section guides the user to link his/her own code for RSAAlgorithmto NetSim.
Pre - Conditions
extension txt.
The path of the input file and the output file can be viewed on clicking the Button “Path” in
NetSim.

Input.txt file has the input data. The dt1>dt2>dt3>dt4>dt5>dt6>dt7>dt8>
format is: dt 1: specifies the prime P
Plain_Text=T dt 2: specifies the prime Q
dt 3: specifies the value of N
dt 4: specifies the value of Z
dt 5: specifies the value of Kp
dt 6: specifies the value of Ks
dt 7: specifies the value of the Cipher Text
dt 8: specifies the value of the Plain Text
Example:
For input: „T‟
Output: 11>3>33>20>7>3>14>20>
264
NetSim Installation path / src / Programming/ RSA.c
Sample Scenario:
Objective - Encrypt and decrypt the message with the using DES.
exercise available. Under programming user has to select
CryptographyAdvancedRSA.
 Plain Text of only one character has to be entered in the field available.
 Value of the prime numbers P and Q are obtained.
 Value of N[p*q] is obtained.
 Value of Z [(p-1)*(q-1)] is obtained.
 Value of Kp and Ks is obtained
 Plain Text which is the actual count of the alphabet is obtained.
 The corresponding Cipher Text is obtained.
create New Samples.
265
9.5.12 Cryptography - Wired Equivalent Privacy (WEP) – Encryption
This section guides the user to link his/her own code for WEP Encryption to NetSim.
Pre - Conditions
extension txt.
Cryptographic_Method=Encryption There are 3 lines in output.txt file

Data: Initialization Vector
TETCOS Key Text
Cipher Text
Ex:
8A699C
0123456789
364130B9CA018D5B760383CD85528751
266
Interface Source code written in C is given using this the user can write only the WEP-
Encryption inside the function fnWEPEncrypt () using the variables already declared.
NetSim Installation path / src / Programming/ WEPEncrypt.c
267
9.5.13 Cryptography - Wired Equivalent Privacy (WEP) - Decryption
This section guides the user to link his/her own code for WEP Decryption to NetSim.
Pre - Conditions
extension txt.
Note:
The temporary directory is navigated through the following step.

Output File Format

Input File Format
Cryptographic_Method=Decryption Plain text

Initialization_Vector=8A699C Ex:
Key=0123456789 TETCOS
Data: 364130B9CA018D5B760383CD85528751
Interface Source code written in C is given using this the user can write only the WEP-
Decryption inside the function fnWEPDecrypt () using the variables already declared.
NetSim Installation path / src / Programming/ WEPDecrypt.c
268
Sample Scenarios:
Objective - Encrypt and Decrypt the message by using WEP.
exercise available. In Programming menu select CryptographyAdvancedWired
Equivalent Privacy.
Note: Encryption should be done first and then Decryption should be done.
 Encryption
Sample Inputs - By using the Input Panel that is available on the left hand side a
o Under CryptographicMethod, Encryption Mode needs to be selected.
o InputData (Maximum of 1500 Characters) - NetSim TetCos
Bangalore
Sample Output - Output for the above Sample is as follows,

o Initialization Vector : 3E41C6
o Key : ABCDEF0123
o The Encrypted Text obtained -
“786441A955C419F9537576954F897BCC5866549653DB5CA73E1B4D
F63CA939AD”
o Click on Copy button and then on Paste button. This would Copy the
EncryptedText onto the DecryptionInputDatafield.
 Decryption
Sample Inputs - By using the InputPanel that is available on the left hand side a Sample
o Sample Mode should be selected. (This is Automatically selected once

the Paste button is clicked at the time of Encrypting the Data).
269
o Under Cryptographic Method, Encryption Mode needs to be selected.
(This is Automatically selected once the Paste button is clicked at the
time of Encrypting the Data).
o Enter Key Value 3E41C6ABCDEF0123 (16Hexadecimal Characters).
(This field is Automatically filled once the Paste button is clicked at the
time of Encrypting the Data).
o Number of Iterations 1.
o InputData -
“786441A955C419F9537576954F897BCC5866549653DB5CA73E1B4D
F63CA939AD” (This field is Automatically filled once the Paste button
is clicked at the time of Encrypting the Data).
Sample Output - Output for the above Sample is as follows,

o Initialization Vector : 3E41C6
o Key : ABCDEF0123
o The EncryptedText obtained - NetSim TetCos Bangalore
270
9.5.14 Distance Vector Routing
This section guides the user to link his/her own code for Distance Vector Routing to NetSim.
Pre - Conditions
Router_ID=1>Router_Name=Router_1>No_Of_Neig Initial Stage>Source Router ID -

hbour=2>Neighbours_ID=2>5 1>Destination
RouterID>CostID>Intermediate
Router_ID=2>Router_Name=Router_2>No_Of_Neig
RouterID
hbour=1>Neighbours_ID=1
Ex:
hbour=0 0>1>2>1>0
Router_ID=4>Router_Name=Router_4>No_Of_Neig 0>1>5>1>0
hbour=0 0>2>1>1>0
Router_ID=5>Router_Name=Router_5>No_Of_Neig 0>5>1>1>0
hbour=1>Neighbours_ID=1
1>1>2>1>0
hbour=0 1>1>5>1>0
1>2>1>1>0
1>2>5>2>1
1>5>1>1>0
1>5>2>2>1
271
2>1>2>1>0
2>1>5>1>0
2>2>1>1>0
2>2>5>2>1
2>5>1>1>0
2>5>2>2>1
Interface Source code written in C is given using this the user can write only the Distance
Vector Routing inside the function fnDistVectAlgorithm() using the variables already
declared.
NetSim Installation path / src / Programming/ DVR.c
Sample Scenarios:
Objective - Find the Shortest Path using Distance Vector Routing.
exercise available. In the Programming menu selectDistance Vector Routing.
Sample Input -Follow the below given steps,
 Click on two Routers to establish a Path (i.e. 1st Click on Router number 1
and 2, then similarly on Router number 2 and 3, 3 and 4, 4 and 5, 5 and 6,
& 6 and 1).
 Router 1, 2, 3, 4, 5, 6 are connected.
 Click on Initial, Intermediate and Final button to execute.
Output - The Output that is obtained is given below,
272
Initial button can be clicked to view the initial table of the all router.
Intermediate button can be clicked to view the intermediate table of the all router.
Final button can be clicked to view the final table of the all router.
273
9.5.15 Distance Host Configuration Protocol
This section guides the user to link his/her own code for Dynamic Host Configuration
Protocol to NetSim.
Pre - Conditions
Number_of_Clients = 4 DHCP_DISCOVER>
Start_Address = 192.168.0.105 Node1>Node2>
End_Address = 192.168.0.109 Node1>Node3>
Mask = 255.255.255.0 Node1>Node4>
Node1>Server
DHCP_OFFER>
Server>Node1
DHCP_REQUEST>
Node1>Server
DHCP_ACK>
Server>192.168.0.105
DHCP_DISCOVER>
Node2>Node1>
Node2>Node3>
Node2>Node4>
Node2>Server
DHCP_OFFER>
Server>Node2
DHCP_REQUEST>
Node2>Server
274
DHCP_ACK>
Server>192.168.0.106
DHCP_DISCOVER>
Node3>Node1>
Node3>Node2>
Node3>Node4>
Node3>Server
DHCP_OFFER>
Server>Node3
DHCP_REQUEST>
Node3>Server
DHCP_ACK>
Server>192.168.0.107
DHCP_DISCOVER>
Node4>Node1>
Node4>Node2>
Node4>Node3>
Node4>Server
DHCP_OFFER>
Server>Node4
DHCP_REQUEST>
Node4>Server
DHCP_ACK>
Server>192.168.0.108
Interface Source code written in C is given using this the user can write only the Dynamic
Host Configuration Protocol inside the function fnDHCPServer() and fnDHCPClient() using
the variables already declared.
NetSim Installation path / src / Programming / DHCP.c
Sample Scenarios:
Objective - Find the Shortest Path using Dynamic Host Configuration Protocol.
275
exercise available. In the Programming menu selectDynamic Host Configuration
Protocol.
Sample Input -Follow the below given steps,
 Select number of clients.
 Set the Start Address and the End Address
 Click on Run button to execute.
Output - The Output that is obtained is given below,
276
9.5.16 Error Correcting Code - Hamming Code
This section guides the user to link his/her own code for Hamming Code Generator to
NetSim.
Pre - Conditions
extension txt.
NetSim.
Parity=Odd „Output.txt ‟ file, the first line is the count of check bits to be
introduced in the current hamming code application. The next 8
Data=a
lines is the check bit calculation process, the first four lines are
Error_Position=7 for input data and the next four lines are for the error data.
Data_Bits_Original=01100001 1 and 2 are the check bits that vary in the Hamming String. The
Data_Bits_Error=00100001 last value is the actual position in the Hamming Code generated
where the data bits has been changed.
4 - The number of check bits introduced
277
3>5>7>9>11>13>0>0>- the check bit of position 1 of input
data
3>6>7>10>11>1>1>- the check bit of position 2 of input data
5>6>7>12>13>0>0>- the check bit of position 4 of input data
9>10>11>12>13>0>0>- the check bit of position 8 of input
data
3>5>7>9>11>13>0>0>- the check bit of position 1 of error
data
3>6>7>10>11>1>1>- the check bit of position 2 of error data
5>6>7>12>13>1>1>- the check bit of position 4 of error data
9>10>11>12>13>1>1>- the check bit of position 8 of error
data
4>8>12>- the check bit position whose value has been changed
and the final error position.
NetSim Installation path / src / Programming/ HammingCode.c
Sample Scenarios:
Objective - To detect and correct the single bit error occurs in the transmission of data.
How to proceed? - The objective can be executed in NetSim using the programming exercise
available, under programming user has to select Error Correcting Code  Hamming Code
 Parity need to be selected. Either Odd or Even can be selected.
 Data need to be entered. Maximum of 8 alphabets can be entered.
 Error Position needs to be selected. Based on the input, its values ranges.
278
 Data Bits which if in the binary form is obtained. This Data Bits is obtained for
Original Data entered as well as for the Error selected.
 Depending on the Parity selected, tables of Hamming String, Original Data and
Error Data will be obtained.
 For the Error Data table to be obtained click on the Next button available in the
output panel. When the Error Data table is obtained Error Position value is
also obtained.
create New Samples.
279
9.5.17 Error Detection Code - Cyclic Redundancy Check (CRC) - 12
This section guides the user to Run his/her own code for Cyclic Redundancy Check to
NetSim.
Pre - Conditions
The user program should read the input scenario from text file named „Input‟ with extension
txt.
Input File Format Output File format
Algorithm=CRC_12 Output contains two values, which is the

written in the separate line.
Condition=No_Error
The First line has the CRC value of the
File_Path=C:\Users\P.Sathishkumar\Docum
data (Sender side CRC value).
ents\1 Th.txt>
The Second line has the CRC value of the
data (Receiver side CRC value).
Example: 8CB
000
280
Interface Source code written in C is given using this the user can write only the Cyclic
Redundancy Check inside the function fnCRC () using the variables already declared.
NetSim Installation path / src / Programming/ Crc12.c
Sample Scenarios:
Objective - To detect the error found in the file transferred between a Sender and Receiver
using CRC12.
exercise available. In the Programming Menu selectError Detecting CodesCyclic
Redundancy Check.
Sample Input
 For No Error Case -Follow the below given steps,
0. SampleMode should be selected.
1. SelectCRC12 as Algorithm from the list available.
2. Under Condition, “NoError” should be selected.
3. Under Input, Enter the path of the file name to get its CRC. The file
should be in “.txt” format which should not exceed 5000bytes.
4. Click on Run button to execute. Refresh button can be used if new Inputs
have to be given.
 For Error Case - Follow the below given steps,
2. Under Condition, “Error” should be selected.
3. Under Input, Enter the path of the file name to get its CRC.The file
281
have to be given.
Sample Output
 For No Error Case: The CalculatedCRC should be Zero when the “.txt file” is
received by the Node2. The message “Data Frame is Flowing from Node1 to
Node2 with No Error”.
 For Error Case: The CalculatedCRC should be Non-Zero when the “.txt file”
is received by the Node2. The message “Data Frame is Flowing from Node1 to
Node2 with Error”.
282
9.5.18 Error Detection Code - Cyclic Redundancy Check (CRC) – 16
This section guides the user to link his/her own code for Cyclic Redundancy Check to
NetSim.
Pre - Conditions

Condition=No_Error written in the separate line.
The First line has the CRC value of the data
File_Path=C:\Users\P.Sathishkumar\Doc
(Sender side CRC value).
uments\1 Th.txt>
The Second line has the CRC value of the data
(Receiver side CRC value).
Example:
0FCF
0000
283
Sample Scenarios:
using CRC16.
exercise available. In the Programming menu selectError Detecting CodesCyclic
Redundancy Check.
Sample Input
7. Under Condition, “No Error” should be selected.
9. Click on Run button to execute. Refresh button can be used if new

284
Sample Output
 For No Error Case: The CalculatedCRC should be Zero when the “.txtfile”
is received by the Node2. The message “DataFrame is Flowing from Node1
to Node2 with NoError”.
 For Error Case: The CalculatedCRC should be Non-Zero when the
“.txtfile” is received by the Node2. The message “DataFrame is Flowing
from Node1 to Node2 with Error”.
285
9.5.19 Error Detection Code - Cyclic Redundancy Check (CRC) - 32
NetSim.
Pre - Conditions

Condition=No_Error
File_Path=C:\Users\P.Sathishkumar\Documents\1 The First line has the CRC value of the
data (Sender side CRC value).
Th.txt>
The Second line has the CRC value of
the data (Receiver side CRC value).
Example:
DD8F598B
00000000
286
Sample Scenarios:
using CRC32.
Redundancy Check.
Sample Input
3. Under Input, Enter the path of the file name to get its CRC. The
file should be in “.txt” format which should not exceed 5000bytes.

3. Under Input, Enter the path of the file name to get its CRC. The
file should be in “.txt” format which should not exceed 5000bytes.
287
Sample Output
 For No Error Case: The CalculatedCRC should be Zero when the
from Node1 to Node2 with NoError”.
 For Error Case: The CalculatedCRC should be Non-Zero when the
from Node1 to Node2 with Error”.
288
9.5.20 Error Detection Code - Cyclic Redundancy Check (CRC) – CCITT
NetSim.
Pre - Conditions
txt.
run Type "%temp%"  NetSim  "Input.txt" and "Output.txt"
Algorithm=CRC_CCITT Output contains two values, which is the

Condition=No_Error
The First line has the CRC value of the data
File_Path=C:\Users\P.Sathishkumar\Document
(Sender side CRC value).
s\1 Th.txt>
The Second line has the CRC value of the
data (Receiver side CRC value).
Example:
92BF
0000
289
NetSim Installation path / src / Programming/ CrcCcitt.c
Sample Scenarios:
using CRC CCITT.
Redundancy Check.
Sample Input
1. SelectCRCCCITT as Algorithm from the list available.
have to be given.

1. SelectCRCCCITT as Algorithm from the list available.
have to be given.
290
Sample Output
 For No Error Case: The CalculatedCRC should be Zero when the “.txtfile” is
received by the Node2. The message “DataFrame is Flowing from Node1 to
Node2 with NoError”.
 For Error Case: The CalculatedCRC should be Non-Zero when the “.txt file”
is received by the Node2. The message “DataFrame is Flowing from Node1 to
Node2 with Error”.
291
9.5.21 Error Detection Code - Longitudinal Redundancy Check (LRC)
This section guides the user to link his/her own code for Longitudinal Redundancy Check to
NetSim.
Pre - Conditions
extension txt.
The user program after executing the concept should write the required output to a file
named „Output’ with extension txt.
NetSim.
„Input.txt‟ file has the original data bits, the type of parity „Output.txt ‟ file, the First line
(odd or even) and the error data bits. is the LRC bits value for the
original data bits. The Second
Parity=Odd (or Even)
line is the LRC bits value for
Data=Tetcos the error data bits.
Data_Bits_Original=0101010001100101011101000110001 00111010 - LRC bits of the
10110111101110011 original data
Data_Bits_Error=001010110100010101010100011000110 01000101 - LRC bits of the
110111101110011 error data
292
Interface source code written in C is given using this the user can write only the Longitudinal
Redundancy Check inside the function fnLRC () using the variables already declared.To view
the interface source code, go to
NetSim Installation path / src / Programming/ LRC.c
Sample Scenarios:
Objective - To study the working of Longitudinal Redundancy Check (LRC)
exercise available, under programming user has to select Error Detecting Codes in that
Longitudinal redundancy Check,
Sample Input - In the Input panel the following steps need to be done,
 Parity need to be selected. Either Odd or Even can be selected.
 Data need to be entered. Maximum of 8 alphabets can be entered.
 Error Position needs to be selected. The value ranges from 1 to 48.
 Data Bits which if in the binary form is obtained. This Data Bits is obtained for
Original Data entered as well as for the Error selected.
 Depending on the Parity selected, tables of LRC of Original Data Bits and LRC
of Error Data Bits are obtained.
 In each of the above mentioned tables last row would contain the Parity.
 Error In Column(s) is obtained.
293
9.5.22 Framing Sequence – Bit Stuffing
This section guides the user to link his/her own code for Bit Stuffing to NetSim.
Pre - Conditions
txt which is in Temporary Directory. The user program after executing the concept should
write the required output to a file named „Output’ with extension txt in Temporary
Directory.
Input File Output File
The “Input.txt” file contains, The “Output.txt” file contains,

Destination Address=Value Message=Value>
Source Address=Value H=Value>e=Value>l=Value>l=Value>o=Value>
Data=Message Binary Values= Value >
CRC Polynomial=Value CRC Polynomial= Value >
Error Status=0 or 1 CheckSumSender= Value >
Seed Value=Value <Stuffing>
Destination Address= Value >
Example: Source Address= Value >
Destination Address=00011111 Data= Value >
Source Address=00111111 <DeStuffing>
Data=Hello Destination Address= Value >
CRC Polynomial=10010 Source Address= Value >
Error Status=0 Data= Value >
Seed Value=45 Error Status= Value >
CheckSumReceiver= Value >
Binary Values= Value >
H= Value >e= Value >l= Value >l= Value >o= Value >
294
Message= Value >
Example:
Message=Hello>
H=72>e=101>l=108>l=108>o=111>
Binary
Values=0100100001100101011011000110110001101111>
CRC Polynomial=10011>
CheckSumSender=1110>
<Stuffing>
Destination Address=000111110>
Source Address=001111101>
Data=010010000110010101101100011011000110111110110>
<DeStuffing>
Destination Address=00011111>
Source Address=00111111>
Data=01001000011001010110110001101100011011111110>
Error Status=0>
CheckSumReceiver=0000>
BinaryValues=0100100001100101011011000110110001101111>
H=72>e=101>l=108>l=108>o=111>
Message=Hello>
Interface source code written in C is given. Using this, the user can write only the functions
fnBitStuffing () and fnDeStuffing (), using the variables already declared.
To view the interface source code, go to NetSim Installation path / src / Programming/
BitStuffing.c
Sample Scenarios:
Objective - To study the working of Bit Stuffing technique.
exercise available, under programming user has to select Framing Sequence  Bit Stuffing.
Sample Inputs - In the Input panel,
295
 Sample mode should be selected.
 Fill in the HDLC Frame fields available
o Enter the 8 binary digits in the Source Address field.
o Enter the 8 binary digits in the Destination Address field.
o Enter data, with a maximum of 5 characters
o CRC polynomial will be chosen by default and select either Error or
No Error.
 Then Run button needs to be clicked. Refresh button can be used if new
Output - The following steps are done internally by NetSim -
 Data will be converted into ASCII Values. ASCII Values will be converted
into Binary Values.
 The Binary Value for CRC polynomial will be shown.
 Checksum will be calculated for the user data in Sender side.
 HDLC frame will be formed in Sender side and Bit Stuffing process is
animated (Adding „0‟ for every consecutive five 1‟s).
 Then Destuffing process will be animated in Receiver side.
 Checksum will be calculated in receiver side.
 Again Binary Values will be converted into ASCII values.
 Finally the ASCII values will be converted into Data which the user
entered.
296
9.5.23 Framing Sequence – Character Stuffing
This section guides the user to link his/her own code for Character Stuffing to NetSim.
Pre - Conditions
txt which is in Temporary Directory
named „Output’ with extension txt in Temporary Directory.

The “Input.txt” file contains, The “Output.txt” file contains,
Starting Delimiter=Value Stuffing>
Destination Address=Value Destination Address=Value>
Source Address=Value Source Address= Value>
Data=Value Data= Value>
Checksum=Value Checksum= Value>
Ending Delimiter=Value DeStuffing>
Example: Destination Address= Value>
Starting Delimiter=a Source Address= Value>
Destination Address=eraerwbr Data= Value>
Source Address=asdasdas Checksum= Value>
Data=sdfgf Example:
297
Checksum=shfsdfsd Stuffing>
Ending Delimiter=h Destination Address=eraaerwbr>
Source Address=aasdaasdaas>
Data=sdfgf>
Checksum=shhfsdfsd>
DeStuffing>
Destination Address=eraerwbr>
Source Address=asdasdas>
Data=sdfgf>
Checksum=shfsdfsd>
Interface source code written in C is given. Using this, the user can write only the functions
fnCharacterStuffing () and fnDeStuffing (), using the variables already declared. To view
NetSim Installation path / src / Programming/ CharacterStuffing.c
Sample Scenarios:
Objective - To study the working of Character Stuffing technique.
exercise available, under programming user has to select Framing Sequence  Character
Stuffing.
 Fill in the HDLC Frame fields available.
o Starting Delimiter has to be filled in.
o Enter the 8 characters in the Destination Address field.
o Enter the 8 characters in the Source Address field.
o Enter in Data field with a maximum of 8 characters.
298
o Enter the 8 characters in the Check Sum field.
o Ending Delimiter has to be filled in.

 HDLC Frame will be formed in Sender side.
 Character stuffing process will be animated in Sender Side.
 Then destuffing process will be animated in Receiver side.
 Once the sample experiment is done Refresh button can be clicked to create
new samples.
299
9.5.24 Virtual Scheduling Algorithm
This section guides the user to link his/her own code for Virtual Scheduling Algorithm to
NetSim.
Pre - Conditions
extension txt.
NetSim.

Input File Content This gives us the format of „Output. Txt‟ to which the
user has to write his program
PCR=1
Each value should be separated by a delimiter„>‟.
CDVT=0.200
There should be no extra white spaces or blank lines.
Actual_Arriva_Time=0.100
Example:
Previous_Theoratical_Time=0.000
Value1>Value2>Value3>
Value1 – Cell conformation Flag,
Value 2 – Next Cells Expected arrival Time
300
Value 3 – Current cell‟s Actual arrival time.
Note: The above convention to write into the
„Output.Txt‟ are mandatory.
A sample file format is as follows:3>2.000>1.000>
Interface source code written in C is given using this the user can write only the Longitudinal
Redundancy Check inside the void main () using the variables already declared.To view the
interface source code, go to
NetSim Installation path / src / Programming/ VSA.c
Sample Scenarios:
Objective - To study the working of Virtual Scheduling Algorithm.
exercise available, under programming user has to select Virtual Scheduling Algorithm,
 Select the Peak Cell Rate (PCR). Its value ranges from 1 to 10.
 Select the Cell Delay Variation Tolerance (CDVT). Its value ranges from 0.1
to 0.9.
 Enter in the Actual Arrival Time.
 A graph with the following information is obtained,
o Cell Confirmation,
301
o Actual Arrival Time,
o Expected Time (TAT)
o Whether the Cell has been discarded or successfully received. This

discarding or receiving of the cell depends on the Actual Arrival Time
entered. Go through the 3 rules given in this program.
create New Samples.
302
9.5.25 Address Mask
This section guides the user to link his/her own code for Address mask to NetSim.
Pre - Conditions
File Format
This gives us the contents of the ‘Input. Txt’ The Output File format
from which the user has to get the values Binary value of IP Address>
for his program
Prefix value>Suffix value>
The Input File format
Binary value of Address mask>
IP Address>
Decimal value of Address mask>.
Sample Input text Format
Sample Output text Format
Let us consider how a given input (Data
file and error index) is stored in the text 11000000 10101001 00000000 10010110 >
and read. 1>31>
IP_Address=192.169.0.150 10000000 00000000 00000000
Prefix_Value=1 0000000>128>0>0>0>
Interface source code written in C is given using this the user can write only
thefnAddressMAsk () function using the variables already declared. To view the interface
source code, go to
303
NetSim Installation path / src / Programming/ AddressMask.c
Sample Scenarios:
Objective - To understand the concept of finding Address mask through programming.
 Select the IP Address
 Select the Prefix value
Output - The following steps are done internally,
 Binary value of IP Address is obtained.
 Prefix, Suffix values are obtained
 Binary value of Address Mask is obtained
 Decimal value of Address Mask is obtained
create New Samples.
304
9.5.26 Binary Conversion
This section guides the user to link his/her own code for Binary conversion to NetSim.
Pre - Conditions
File Format
This gives us the contents of the ‘Input. The Output File format
Txt’ from which the user has to get the First Byte value>128>Quotient of First
values for his program Byte/128>Remainder of First Byte/128>
The Input File format Previous remainder>64>Quotient of
IP Address> Previous remainder/64>Remainder of
Previous remainder /64>
Sample Input text Format
Previous remainder>32>Quotient of
IP_Address=192.168.0.100
Previous remainder/32>Remainder of
Previous remainder>16>Quotient of
Previous remainder/16>Remainder of
Previous remainder>8>Quotient of Previous
remainder/8>Remainder of Previous
remainder /8>
305
remainder /4>
remainder /2>
remainder /1>.
.same procedure for all bytes
Binary value>
192>128>1>64>
64>64>1>0>
0>32>0>0>
0>16>0>0>
0>8>0>0>
0>4>0>0>
0>2>0>0>
0>1>0>0>
168>128>1>40>
40>64>0>40>
40>32>1>8>
8>16>0>8>
8>8>1>0>
0>4>0>0>
0>2>0>0>
0>1>0>0>
0>128>0>0>
0>64>0>0>
0>32>0>0>
0>16>0>0>
0>8>0>0>
0>4>0>0>
0>2>0>0>
0>1>0>0>
100>128>0>100>
100>64>1>36>
306
36>32>1>4>
4>16>0>4>
4>8>0>4>
4>4>1>0>
0>2>0>0>
0>1>0>0>
11000000 10101000 00000000 01100100 >
Interface source code written in C is given using this the user can write only the
fnBinaryConversion () function using the variables already declared. To view the interface
source code, go to
NetSim Installation path / src / Programming/ BinaryConversion.c
Sample Scenarios:
Objective - To understand the concept of Binary conversion through programming.
 Each bit is obtained one by one.
create New Samples.
307
9.5.27 Classless InterDomain Routing
This section guides the user to link his/her own code for Classless Inter Domain Routing to
NetSim.
Pre - Conditions
extension txt.
NetSim.
Note:
The temporary directory is navigated through the following step.

File Format
This gives the contents of the The Output file contains the First address, Last
„Input. Txt‟ from which the user has address, Mask, Value and Network Address of
to get the values. all the networks.
The Input File contains: First Address: The Starting Address of the
Starting_IP_Address=150.0.0.0 Network
Last Address: The last address in the Network.
308
No_of_Networks=3 Mask: The Mask address (Mask should be 4 byte
format).
No_of_Hosts_in_Network_1=512
Number of Node: The number of nodes in the
network.
Value: The value will be either 0 or 1.
Host_IP_Address=150.0.1.2
0 - The next line has the network address to
which the given host belongs.
1 - Means that the host does not belong to any
network.
Network Address: If the Value is 1 then the
network to which the host belongs is given.
Note: Each data will have a separate line and
each line will end with ">"
A Sample Output File Format
150.0.0.0>
150.0.1.255>
255.255.254.0>
512>
150.0.4.0>
150.0.7.255>
255.255.252.0>
1024>
150.0.8.0>
150.0.15.255>
255.255.248.0>
2048>
0>
150.0.0.0>
For each network there will be first address, last
address, mask and number of hosts. Since the
input is 3 networks, there are 3 set of outputs.
The last two lines give the details about whether
the host is present in any of the network.
309
Interface source code written in C is given using this the user can write only the CIDR inside
the function fnCIDR () using the variables already declared. To view the interface source
code, go to
NetSim Installation path / src / Programming/ CIDR.c
Sample Scenarios:
Objective - To Implement Classless InterDomain Routing (CIDR).
exercise available, under programming user has to select Classless InterDomain Routing,
 Select the Starting IP Address from the given range.
 Select the No. of Networks from the given range. Maximum of 6 networks
can be selected.
 Select the No. of Hosts from the given range.
 Click on Add button to add the No.ofHosts onto the Hosts Field. The use of
Add button depends on the No. of Networks selected. If a new No. of Hosts
has to be added then remove button can be used.
 Select the Host IP Address.
 Based on the Starting IP Address a table is obtained.
310
 There are 4 columns available in the output table, i.e. First Address, Last
Address, CIDR Mask and No. of Hosts.
 The First Address of the first network would be nothing but the Starting IP
Address which is selected. No. of rows in the table depends on the No. of
Networks selected.
 The Last Address depends on depends on the No. of Host selected.
 CIDR Mask is obtained internally by using the following formula,
CIDR Mask = 32 - (log (No. of Host) / log (2))
create New Samples.
311
9.5.28 Network Address
This section guides the user to link his/her own code for Network Addresses to NetSim.
Pre - Conditions
File Format
IP_Address=192.168.0.140 The Output File format

Prefix_Value=1 Binary value of IP Address>
Prefix value>
Binary value of Address mask>
Binary value of Network Address>
Decimal value of Network Address>.
11000000 10101000 00000000 10001100 >1>
10000000 00000000 00000000 00000000>
10000000 00000000 00000000 00000000>
128>0>0>0>
312
fnNetworkAddress () function using the variables already declared. To view the interface
source code, go to
NetSim Installation path / src / Programming/ NetworkAddress.c
Sample Scenarios:
Objective - To understand the concept of finding Network Address through programming.
 Select the Prefix value
 Binary value of Network Address is obtained
 Decimal value of Network Address is obtained
create New Samples.
313
9.5.29 Special Addresses
This section guides the user to link his/her own code for Special Addresses to NetSim.
Pre - Conditions
txt.
File Format
IP_Address=192.168.0.160 The Output File format

Prefix_Value=5 Binary value of IP Address>
32>Prefix value>Suffix value>
Binary value of Prefix Part> Binary value of
Suffix Part>
Condition number in the table>condition>
Type of address>.
11000000 10101000 00000000 10100000 >
32>5>27>
11000>000 10101000 00000000 10100000>
It doesn't Satisfy the four conditions>
Not a special address>
314
fnSpecialAddress () function using the variables already declared. To view the interface
source code, go to
NetSim Installation path / src / Programming/ HammingCode.c
Sample Scenarios:
Objective - To understand the concept of Special Addresses through programming.
 Select the IP Address in slash notation
 Prefix, Suffix values are obtained
 Binary value of Prefix part and Suffix part are obtained
 Type of address is obtained
create New Samples
315
9.5.30 Subnetting
This section guides the user to link his/her own code for Sub-netting to NetSim.
Pre - Conditions
extension txt.
NetSim.
File Format
Class=B The Output file contains the Default mask (in decimal),
Network portion of Default mask (in binary), Host portion
Network_Address=128.0.0.0
of Default mask (in binary), Subnet mask bit value, Network
No_of_Subnets=2 portion of Subnet mask (in binary), Host portion of Subnet
Host_IP_Address=128.0.0.89 mask (in binary), Subnet mask (in decimal), number of zero
in host portion, number of host in each subnet, Host address,
subnet number of the given host, subnet address of the given
host and Subnet address, Starting address, Ending address,
Broadcast address of each subnet.
The Output File format
Default mask (in decimal)>
Network portion of Default mask (in binary)>Host portion
of Default mask (in binary)>
316
Subnet mask bit value>
Subnet mask (in decimal)>
Network portion of Subnet mask (in binary)>Host portion of
Subnet mask (in binary)>
Number of zero in host portion,>Number of host in each
subnet>
Host address>Subnet number of the given host >Subnet
address of the given host>
Subnet address>Starting address>Ending address>Broadcast
address >
.
.
.until number of subnet is reached
255.255.0.0
11111111 11111111>00000000 00000000>
1>
255.255.128.0>
11111111 11111111 1>0000000 00000000>
15>32766>
128.0.0.89>1>128.0.0.0>
1>128.0.0.0>128.0.0.1>128.0.127.254>128.0.127.255>
2>128.0.128.0>128.0.128.1>128.0.255.254>128.0.255.255>
Interface source code written in C is given using this the user can write only the Leaky bucket
algorithm inside the function fnSubnet () using the variables already declared. To view the
NetSim Installation path / src / Programming/ Subnet.c
317
Sample Scenarios:
Objective - To understand the concept of Subnetting through programming.
exercise available, under programming user has to select Subnetting,
 Select the Class Name
 Select the Network Address from the given list.
 Select the Number of Subnets from the given list.
 Select the Host IP Address.
 Subnet mask value is obtained.
 Number of host in the each subnet is obtained
 Subnet address, Starting address, Ending address and Broadcast address are
obtained.
 Subnet address of the given Host IP address is obtained.
create New Samples.
318
9.5.31 EUI-64 Interface Identifier
This section guides the user to link his/her own code for EUI 64 Interface Identifier to
NetSim.
Pre - Conditions
extension txt.
File Format
IPV6_Network_Id=2000:FE21:5931:72 The Output File format

C3 MAC Address>
MAC_Address=11-11-FF-FF-12-34 First part of MAC Address>Second part of MAC
Address
FF-EE appended Address>
First byte value>Binary value of First byte>
7th bit value>Complement value of 7th bit
Complemented binary value of First byte>Hexa
decimal value of complemented binary value>
Interface Id value> Interface Id in colon notation>
IPV6 prefix value>
319
IPV6 Address>
11-11-FF-FF-12-34>
11-11-FF>FF-12-34>
11-11-FF-FF-FE-FF-12-34>
11>00010001>
0>1>
00010011>13>
13-11-FF-FF-FE-FF-12-
34>1311:FFFF:FEFF:1234>
2000:FE21:5931:72C3>
2000:FE21:5931:72C3:1311:FFFF:FEFF:1234>
Interface source code written in C is given using this the user can write only the fnEUI64 ()
function using the variables already declared. To view the interface source code, go to
NetSim Installation path / src / Programming/ IPV6EUI64.c
Sample Scenarios:
Objective - To understand the concept of EUI 64 Interface Identifier through programming.
exercise available, under programming user has to select IPV6 Addressing  EUI 64
Interface Identifier,
 Select the IPV6 Network Id (IPV6 Prefix)
 Enter the MAC Address.
320
 MAC Address is divided into two parts
 FF-FE value is appended between the two parts
 Interface Identifier is found by complementing 7th bit of firs byte
 IPV6 Network Id (IPV6 prefix) and Interface Identifier are combined to

produce IPV6 address
create New Samples.
321
9.5.32 IPV6 Host Addresses
This section guides the user to link his/her own code for IPV6 Host Addresses to NetSim.
Pre - Conditions
extension txt.
File Format
IPV6_Address=1111:2222: The Output File format

3333:4444:AAAA:BBBB: IPV6 Address>
CCCC:DDDD
Binary value of IPV6 Address>
Prefix_Length=12
Prefix part of IPV6 Address>Suffix part of IPV6 Address>
Prefix part of Starting Address>Suffix part of Starting
Address>
Starting Address in hexa decimal notation>
Prefix part of Ending Address>Suffix part of Ending
Address>
Ending Address in hexa decimal notation>
1111:2222:3333:4444:AAAA:BBBB:CCCC:DDDD>
322
000100010001000100100010001000100011001100110011
010001000100010010101010101010101011101110111011
11001100110011001101110111011101>12>116>
000100010001>00010010001000100010001100110011001
101000100010001001010101010101010101110111011101
111001100110011001101110111011101>
000100010001>00000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000>
1110:0000:0000:0000:0000:0000:0000:0000>
000100010001>11111111111111111111111111111111111
111111111111111111111111111111111111111111111111
111111111111111111111111111111111>
111F:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF>
fnHostAddresses () function using the variables already declared. To view the interface
source code, go to
NetSim Installation path / src / Programming/ IPV6HostAddress.c
Sample Scenarios:
Objective - To understand the concept of IPV6 Host Addresses through programming.
exercise available, under programming user has to select IPV6 Addressing IPV6 Host
Addresses,
 Enter the IPV6 Address.
 Select the Prefix length.
323
 IPV6 is separated into two parts: Network Id bits (prefix) and Host Id bits
(suffix)
 Starting address of the network is found by replacing each bits of suffix part
with zero
 Ending address of the network is found by replacing each bits of suffix part
with one
create New Samples.
324
9.5.33 IPV6 Subnetting
This section guides the user to link his/her own code for IPV6 Subnetting to NetSim.
Pre - Conditions
extension txt.
File Format
IPV6_Address=1111:2222:3 The Output File format

333:4444:AAAA:BBBB:CC Binary value of IPV6 Address>
CC:DDDD
Prefix part of IPV6 Address>Suffix part of IPV6 Address>
Prefix_Length=12
Number of subnets>number of subnet msk bit>
Number_of_Subnets=2
Prefix part of IPV6 Address>Subnet Id part of IPV6
Number_of_Level=2 address>Suffix part of IPV6 Address>
Subnets_in_Level1=2 Prefix part of IPV6 Address>Subnet Id part of IPV6
Subnets_in_Level2=4 address>Suffix part of IPV6 Address>
Prefix part of Level 1 „s first subnet Address> Subnet Id part
of Level 1 „s first subnet Address> Suffix part of Level 1 „s
first subnet Address> Hexa decimal value of Level 1 „s first
subnet address>prefix length of Level 1 „s first subnet>
.
.
325
until number of subnet reached in the first level
First level‟s subnet number>Prefix part of Level 2 „s first
subnet Address> Subnet Id part of Level 2 „s first subnet
Address> Suffix part of Level 2 „s first subnet Address>
Hexa decimal value of Level 2 „s first subnet address>prefix
length of Level 2 „s first subnet>
.
.
until the number of subnets reached in the second level of
first level‟s subnet
.
.
until the number of subnets reached in the first level
1111:2222:3333:4444:AAAA:BBBB:CCCC:DDDD>
0001000100011001001000100010001000110011001100110
1000100010001001010101010101010101110111011101111
001100110011001101110111011101>
000100010001>000100100010001000100011001100110011
0100010001000100101010101010101010111011101110111
1001100110011001101110111011101>2>1>
000100010001>0>001001000100010001000110011001100
1101000100010001001010101010101010101110111011101
111001100110011001101110111011101>
000100010001>0>001001000100010001000110011001100
1101000100010001001010101010101010101110111011101
111001100110011001101110111011101>1111:2222:3333:4
444:AAAA:BBBB:CCCC:DDDD>13>
000100010001>1>001001000100010001000110011001100
1101000100010001001010101010101010101110111011101
111001100110011001101110111011101>1119:2222:3333:4
444:AAAA:BBBB:CCCC:DDDD>13>
0>1111:2222:3333:4444:AAAA:BBBB:CCCC:DDDD>15>
1>111B:2222:3333:4444:AAAA:BBBB:CCCC:DDDD>15>
1>111D:2222:3333:4444:AAAA:BBBB:CCCC:DDDD>15>
1>111F:2222:3333:4444:AAAA:BBBB:CCCC:DDDD>15>
326
fnIPV6Subnetting () function using the variables already declared. To view the interface
source code, go to
NetSim Installation path / src / Programming/ IPV6Subnetting.c
Sample Scenarios:
Objective - To understand the concept of IPV6 Subnetting through programming.
exercise available, under programming user has to select IPV6 Addressing IPV6
Subnetting,
 Enter the IPV6 Address.
 Select the Prefix length.
 Select the number of subnets value
 Click the Add value button to add the levels
 IPV6 is separated into two parts: prefix and suffix
 Number of subnet mask id is calculated
 Then Subnet Id portion is derived from suffix part
 Using the subnet id portion, subnets are calculated
 Like that, subnets in the all levels are calculates by using the above steps
create New Samples.
327
9.5.34 Leaky Bucket Algorithm
This section guides the user to link his/her own code for Leaky Bucket Algorithm to NetSim.
Pre - Conditions
extension txt.
NetSim.
File Format
Output_Capacity=100 „Output.txt‟ file contains three lines of data. The

data format in the output file should be as follows:
Buffer_Size=100
Output rate at 1st second >Output rate at 2nd
Input_Capacity=100,100,500,1
second>…………..>
00,100,100,100,100,100,100,
Discard rate at 1st second >Discard rate at 2nd
second>…………..>
Total number of seconds taken >
The data should be stored in the file with a delimiter
“>” in between.
Sample File data
328
100>100>100>100>100>100>100>100>100>100>1
00>
0>0>300>0>0>0>0>0>0>0>0>
11>
Interface source code written in C is given using this the user can write only the Leaky bucket
algorithm inside the function fnLBA() using the variables already declared. To view the
NetSim Installation path / src / Programming/ LBA.c
Sample Scenarios:
Objective - To understand the concept of Leaky Bucket Algorithm(LBA) through

programming.
exercise available, under programming menu user has to select Leaky Bucket Algorithm.
 Select the Output Capacity from the given list of values. The value ranges
from 100 to 1000.
 Select the Size of Buffer from the given list of values. The value ranges from
100 to 1000.
 Enter in the Input Capacity in the fields provided. The range that can be
entered is from 100 to 1000. These values will be plotted in the graph on the
right hand side panel.
329
 Once the Run button is clicked a graph with Output and Discard Rate is
obtained.
 The graph explains in detail as in what is the Output and Discard Packet Rate
for the given inputs.
create New Samples.
330
9.5.35 Multi Level Multi Access
This section guides the user to link his/her own code for Multi-Level Multi Access Protocol
to NetSim.
Pre - Condition
User written program should read the value from the „Input.txt‟ in the temporary directory
which is having input from the GUI at runtime
The output should be stored in „Output.txt‟ in the temporary directory for display.
User written program should return an integer value.
Executing the required concept and, The results of the program should be written into the
Note:The naming of the input and the output file must be same as the text displayed in the
Methodology screen
File Format
Number_of_Nodes=2 „Output.txt‟ file has the decade‟s number, decade‟s type,

and actual decades, node addresses
Node1_Address=250
Decade No>Decade
Node2_Address=500
Type>Decade>aderess1>adress2>…
Sample Output:
0>0>0000100100>
1>1>0000000001>
2>2>0000000001>500>
3>1>0000100000>
4>2>0000000001>250>
331
Interface source code written in C is given using this the user can write only the Multi-Level
Multi Access Protocol inside the function fnMLMA () using the variables already declared.
NetSim Installation path / src / Programming/ MLMA.c
Sample Scenarios:
Objective - To study the working of Multi Level Multi Access (MLMA).
exercise available, under programming user has to select Multi-Level Multi -Access Protocol.
 Number of Nodes need to be selected. The value ranges from 2 to 15.
 Node Address has to be entered and added onto the Node Address field. The
Number of Nodes selected and the Number of Addresses added into the
Address field should match.
 An Output table is formed.
 On the right hand panel an animation would play. This shows that higher the
address given to the node higher the priority that node gets. Hence the node
with the higher address would transmit the data first.
create New Samples.
9.5.36 Code Division Multiple Access
332
This section guides the user to link his/her own code for Code Division Multiple Access to
NetSim.
Pre - Conditions
txt which is in Temporary Directory.
„Output’ with extension txt in Temporary Directory.
Note:The Temporary Directory is navigated through the following step.
File Format
The “Input.txt” file contains, No. of Transmitting MobileStations=Value>

NumberofTransmittingMobilestation MobileStation=Value>Data=Value>code=Value>En
s=Value> code=Value>Signal=Value>
MobileStation=Value>Data=Value> MobileStation=Value>Data=Value>code=Value>En
Code=Value> code=Value>Signal=Value>
MobileStation=Value>Data=Value> MobileStation=Value>Data=Value>code=Value>En
Code=Value> ecode=Value>Signal=Value
MobileStation=Value> Interference Pattern=Value>
Data=Value>Code=Value> MobileStation=Value>code=Value>Decode=Value>
Example: Data=Value>
NumberOfTransmittingMobileStatio MobileStation=Value>code=Value>Decode=Value>
ns=2> Data=Value>
MobileStation=1>Data=10101010> MobileStation=Value>code=Value>Decode=Value>
Code=1 1 1 1 1 1 1 1> Data=Value>
MobileStation=2>Data=11110000> Example:
333
Code=1 -1 1 -1 1 -1 1 -1> NumberofMobileStations=2>
MobileStation=1>Data=1 0 1 0 1 0 1 0 >Code=1 1 1
1 1 1 1 1 >Encode=1 -1 1 -1 1 -1 1 -1 >Signal=1 1 1
1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 1 1 1 1 -1 -1 -
1 -1 -1 -1 -1 -1 1 1 1 1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1
1 1 1 1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 >
MobileStation=2>Data=1 1 1 1 0 0 0 0 >Code=1 -1
1 -1 1 -1 1 -1 >Encode=1 1 1 1 -1 -1 -1 -1 >Signal=1
-1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1
1 -1 1 -1 1 -1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1
1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 >
InterferencePattern=2 0 2 0 2 0 2 0 0 -2 0 -2 0 -2 0 -
2 2 0 2 0 2 0 2 0 0 -2 0 -2 0 -2 0 -2 0 2 0 2 0 2 0 2 -2
0 -2 0 -2 0 -2 0 0 2 0 2 0 2 0 2 -2 0 -2 0 -2 0 -2 0 >
MobileStation=1>Code=1 1 1 1 1 1 1 1 >Decode=8
-8 8 -8 8 -8 8 -8 >Data=1 0 1 0 1 0 1 0 >
MobileStation=2>Code=1 1 1 1 1 1 1 1 >Decode=8
8 8 8 -8 -8 -8 -8 >Data=1 1 1 1 0 0 0 0 >
Interface source code written in C is given.Using this, the user can write only the function
fnEncode () and fnDecode (), using the variables already declared. To view the interface
source code, go to
NetSim Installation path / src / Programming/ CDMA.c
Sample Scenarios:
Objective - To study the working of Code Division Multiple Access technique
exercise available. Under programming select Multiple Access Technology  Code Division
Multiple Access.
 Sample Mode should be selected
334
 In default, the Encode operation will be enabled.
 Choose the Number of Transmitting Mobile Stations.
 Enter the Binary Datas as per the limits.
 Choose the respective Codes for each Mobile Station.
Number of Transmitting Mobile Stations 3 (Maximum of 8 Mobile Stations)
Mobile Station Binary Data(1Byte) Code

1 01110111 11111111
2 00110011 1 -1 1 -1 1 -1 1 -1
3 11011101 1 1 -1 -1 1 1 -1 -1
 Then Run button needs to be clicked. Refresh button can be used, if new
inputs have to be given.
Output -The Output for the above sample is as follows,
 In Transmitter side, the values of each Mobile Station‟s Binary Data, Code,
Encode and Signal are shown, if the user clicks the Mobile Station.
 The Signals will be broadcast from each Mobile Stations.
 The Interference Pattern will be formed in Base Station and if the user
clicks the Base Station, interference Pattern will be displayed.
 Decode mode needs to be selected.
 In Receiver side, the Interference Pattern will be broadcasted to each

Mobile Station from the Base Station.
 In Receiver side, the values of each Mobile Station‟s Interference Pattern,

Code, Decode and Binary Data are shown, if the user clicks the Mobile
Station.
335
 Once the sample experiment is done Refresh button can be clicked to create
new samples.
The Values are showed in Table.
Transmitter Side
Mobile Binary Code Encode Signal

Station Data(1Byte)
1 01110111 11111111 -1, 1, 1, 1, -1, 1, 1, -1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 1
1 111 11111111 1111
1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 1
1111111 11111111
11111111
2 00110011 1 -1 1 -1 1 -1 1 - -1, -1, 1, 1, -1, -1, 1, -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1
1 1 1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1
1 -1 1 -1 1 -1 -1 1 -1 1 -1 1 -1
1 -1 1 -1 1 -1 1 -1 1 1 -1 1 -1
1 -1 1 -1 1 -1 1 -1 1 -1 1 -1
3 11011101 1 1 -1 -1 1 1 -1 - 1, 1, -1, 1, 1, 1, -1, 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1
1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1 1 1 -
1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -
1 1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 -
1 -1 1 1 1 1 -1 -1 1 1 -1 -1
In Base Station
Mobile Signal
Station
1 -1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
-1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
2 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1
-1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1
3 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1 1 1 -1 -1 1 1 -1 -1
336
1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1 1 1 -1 -1 1 1 -1 -1
Interference 1 1 -3 -1 -1 1 -3 -1 1 3 -1 1 1 3 -1 1 1 -1 3 1 1 -1 3 1 3 1 1 -1 3
Pattern 1 1 -1 -1 1 -3 -1 -1 1 -3 -1 1 3 -1 1 1 3 -1 1 1 -1 3 1 1 -1 3 1 3 1
1 -1 3 1 1 -1
Receiver Side
Mobile Code Decode Binary

Station Interference Pattern Data(1Byte)
1 1 1 -3 -1 -1 1 -3 -1 1 3 11111111 8 8 8 8 -8 8 8 01110111
-1 1 1 3 -1 1 1 -1 3 1 8
1 -1 3 1 3 1 1 -1 3 1 1
-1 -1 1 -3 -1 -1 1 -3 -1 1
3 -1 1 1 3 -1 1 1 -1 3
1 1 -1 3 1 3 1 1 -1 3 1 1
-1
2 1 1 -3 -1 -1 1 -3 -1 1 3 1 -1 1 -1 1 -1 1 - -8 -8 8 8 -8 - 8 8 00110011
-1 1 1 3 -1 1 1 -1 3 1 1 8
1 -1 3 1 3 1 1 -1 3 1 1
-1 -1 1 -3 -1 -1 1 -3 -1 1
3 -1 1 1 3 -1 1 1 -1 3
1 1 -1 3 1 3 1 1 -1 3 1 1
-1
3 1 1 -3 -1 -1 1 -3 -1 1 3 1 1 -1 -1 1 1 -1 - 8 8 -8 8 8 8 - 11011101
-1 1 1 3 -1 1 1 -1 3 1 1 8 8
1 -1 3 1 3 1 1 -1 3 1 1
-1 -1 1 -3 -1 -1 1 -3 -1 1
3 -1 1 1 3 -1 1 1 -1 3
1 1 -1 3 1 3 1 1 -1 3 1 1
-1
337
9.5.37 Time Division Multiple Access
This section guides the user to link his/her own code for Time Division Multiple Access to
NetSim.
Pre - Conditions
txt which is in Temporary Directory.
„Output’ with extension txt in Temporary Directory.
Note:The Temporary Directory is navigated through the following step.
File Format
The “Input.txt” file contains, Guard Interval =Value>Bandwidth=Value>start

time=Value >end time=Value>nouser=Value>
Bandwidth=Value>No. of
time slots=Value>Time slot channel no=Value>Bandwidth=Value>start
Length=Value>Guard time=Value>End time=Value>user=Value>
Interval=Value> Guard Interval =Value>Bandwidth=Value>start
Example: time=Value >end time=Value>nouser=Value>
BandWidth=100>TimeSlot= Guard Interval =Value>Bandwidth=Value>start
1>TimeSlotLength=100>Gua time=Value >end time=Value>nouser=Value>
rdInterval=0.0> channel no=Value>Bandwidth=Value>start
time=Value>End time=Value>user=Value>
.
.
and so on.
338
The value of the GuardInterval is -1 and the value of the no
user is 0
Example:
GuardInterval=-
1>Bandwidth=100>StartTime=0.0>EndTime=0.0>nouser=
0>
Channelno=1>Bandwidth=100>StartTime=0.0>EndTime=
100.0>user=1>
GuardInterval=-
1>Bandwidth=100>StartTime=100.0>EndTime=100.0>no
user=0>
Interface source code written in C is given.Using this, the user can write only the function
fnTDMA(), using the variables already declared. To view the interface source code, go to
NetSim Installation path / src / Programming/ TDMA.c
Sample Scenarios:
Objective - To study the working of Time Division Multiple Access technique.
exercise available, under programming user has to select Multiple Access Technology 
Time Division Multiple Access.
 Enter the Value of the Bandwidth.
 Enter the Value of the No. of Time Slots.
 Enter the Value of the TimeSlotLength.
 Enter the Value of the GuardInterval
Note:
The Values entered should be within the range.
339
Bandwidth(kHz) 200
No. of TimeSlots 3
TimeSlotLength(µs) 100
GuardInterval(µs) 10
 Then Run button need to be clicked. Refresh button can be used, if new
Output -The Output for the above sample is as follows,
 Bandwidth is divided into Time slots called channel.
 The first channel is allocated to first mobile station, second channel is

allocated to second mobile station and so on.
 The first Mobile Station will access the medium in first channel time slot.
 The Second Mobile Station will access the medium in second channel
time slot, and so on.
 During the guard interval, No mobile station will access the medium. This
is used to avoid the collision or interference.
Finally the table will be showed.
 Channel no. is obtained.
 Bandwidth value is obtained.

 Start Time and End Time of the Guard Interval is obtained
 Start Time and End Time of the channel is obtained.
340
 Which Mobile Station is accessing the allocated time slot is obtained.
Channel number Bandwidth(kHz) Time(µs) Mobile Station
0 200 0.0 – 5.0 0
1 200 5.0 – 95.0 1
0 200 95.0 – 100.0 0
0 200 100.0 – 105.0 0
2 200 105.0 – 195.0 2
0 200 195.0 – 200.0 0
0 200 200.0 – 205.0 0
3 200 205.0 – 295.0 3
0 200 295.0 – 300.0 0
0 200 300.0 – 305.0 0
1 200 305.0 – 395.0 1
341
9.5.38 Orthogonal Frequency Division Multiple Access
This section guides the user to link his/her own code for Orthogonal Frequency Division
Multiple Access to NetSim.
Pre-conditions
txtwhich is in Temporary Directory.
„Output’ with extension txtin Temporary Directory.
The following lines will be Parallel Data Conversion

in Input.txt file. User 1
Number of users = Value Value
User1 =Value User 2
User2 =Value Value
User3 =Value User 3
User4 =Value Value
Number of sub carrier per User 4
user = Value
Value
Bit Mapping
Example:
User 1
Number of users = 4
Value
User1 =111111111111
User 2
User2 =010101010101
Value
342
User3 =101010101010 User 3
User4 =000000000000 Value
Number of sub carrier per User 4
user = 4 Value
SubCarrier Mapping
User 1
Value
User 2
-Value
User 3
Value
User 4
Value
SubCarrier Addition
User 1
Value
User 2
Value
User 3
Value
User 4
Value
Example:
Parallel Data Conversion
User 1
1 1 1 1
1 1 1 1
1 1 1 1
User 2
0 1 0 1
0 1 0 1
0 1 0 1
User 3
1 0 1 0
343
1 0 1 0
1 0 1 0
User 4
0 0 0 0
0 0 0 0
0 0 0 0
Bit Mapping
User 1
1 1 1 1
1 1 1 1
1 1 1 1
User 2
-1 1 -1 1
-1 1 -1 1
-1 1 -1 1
User 3
1 -1 1 -1
1 -1 1 -1
1 -1 1 -1
User 4
-1 -1 -1 -1
-1 -1 -1 -1
-1 -1 -1 -1
SubCarrier Mapping
User 1
sin(2PIf0t) sin(2PIf1t) sin(2PIf2t) sin(2PIf3t)
User 2
-sin(2PIf4t) sin(2PIf5t) -sin(2PIf6t) sin(2PIf7t)
User 3
sin(2PIf8t) -sin(2PIf9t) sin(2PIf10t) -sin(2PIf11t)
344
User 4
-sin(2PIf12t) -sin(2PIf13t) -sin(2PIf14t) -sin(2PIf15t)
SubCarrier Addition
User 1
sin 2PI(f0+f1+f2+f3)t
User 2
sin 2PI(-f4+f5-f6+f7)t
User 3
sin 2PI(f8-f9+f10-f11)t
User 4
sin 2PI(-f12-f13-f14-f15)t
sin 2PI(-f12-f13-f14-f15)t
sin 2PI(-f12-f13-f14-f15)t
Interface Source code written in C is given. Using this, the user can writeonly the
fnOFDMA() and fnSubcarrierAddition() functions, using the variables already declared.To
view the interface source code, go to
NetSim Installation path/src/Programming/OFDMA.c
 Open file location in Windows 7/8/10
345
Sample Scenarios:
Objective - To study the working of Orthogonal Frequency Division Multiple Access

technique
exercise available. Under programming select Multiple Access Technology OFDMA
Sample Inputs - In the Input panel,

 The value of Number of Users needs to be selected.
 Enter the Binary Datafor each user.
 Number of SubCarriers per User needs to be selected.
 Then Run button needs to be clicked. Refresh button can be used if new Inputs have to
be given.
Output - The following steps are done internally by NetSim
 The values of each userBinary Data, Parallel Conversion, Bit Mapping, SubCarrier
Mapping&SubCarrier Addition and Transmission will be shown in the right hand side
of the screen by animation.
 Once the sample experiment is done Refresh button can be clicked to create new
samples.
346
9.5.39 PC to PC Communication - Socket Programming TCP
This section guides the user to link his/her own code for PC to PC Communication – Socket
programming to NetSim.
Pre – Conditions
txt.
Coding Pre Requisites:
The prerequisite for the creation of sockets in the Windows-based C complier is they must
have winsock.h header file in its standard header file folder. In order to use the commands of
the winsock.h, there must be wsock32.lib library file present in the C complier. To link
wsock32.lib, different steps have to be followed for different compilers as shown:
 For Visual Studio complier 2010 (10.0 versions), the library file linkage must be
made in the following way:
347
a. Click Project Menu in the workspace.
b. Select properties in the pull-down menu or press Alt + F7
c. Then click Linker.
d. Select Input
d. Type ws2_32.lib file in the Additional Dependencies text box area.
e. Click OK to confirm the changes in the workspace.
 If you have an eclipse complier, the library linkage must be in the following way
348
b. Select properties in the pull-down menu
c. Then click C/C++ Build.
d. Select Setting.
e. Select Libraries under MinGW C Linker
f. Press add button in the Libraries (-l) window
d. Type ws2_32 file in the text box area.
 If gcc compiler is used via command prompt:
a. Set the path to Socket program location.
b. Create output file (.o file) using below command.
gcc -C Filename.c
349
c. Create exe file (.exe file) using below command
 If using Dev C++ IDE, go to Toolscompiler options and add -lws2_32 as follows
before executing:

The data format in the input file is as follows, Write the received message
Server Input Ex:192.168.0.2:- Requesting for the
Protocol=TCP connection
Operation=Server
Client
Protocol=TCP
Operation=Client
Destination IP=192.168.0.132
<Client IP:-Message>
Ex: 192.168.0.2:- Requesting for the
connection
350
Interface source code written in C is given using this the user can write only the TCP Client ()
function. To view the interface source code, go to
NetSim Installation path / src / Programming/ SocketTCP.c
351
9.5.40 PC to PC Communication - Socket Programming UDP
Pre – Conditions`
352
d. Select Input
353
d. Select Setting.
gcc -C Filename.c
354
before executing:
The data format in the input file is as follows,. Write the received message
Server Input Ex:192.168.0.2:- Requesting for the
Protocol= UDP connection
Operation=Server
Client
Protocol=UDP
Operation=Client
Destination IP=192.168.0.132
<Client IP:-Message>
Ex: 192.168.0.2:- Requesting for the connection
355
Interface source code written in C is given using this the user can write only the UDP ()
functions. To view the interface source code, go to
NetSim Installation path / src / Programming/ SocketUDP.c
Sample Scenarios:
Objective - Send and Receive the data using PC to PCCommunication - SocketProgramming
How to Proceed? -Two Systems are required to perform this experiment. When one System
is in the ServerMode other should be in the Client Mode. The objective can be executed in
NetSim using the programming exercise available. In the Programming menu selectPC to
PC Communication  Socket Programming.
 Select a Protocol from the following,
o TCP
o UDP
 Under Operation, Server or Client should be selected.
 On the Right hand side panel there is an InputField “Enter Data to be
Transmitted”, where Data needs to be typed in. This Data is later sent to the
ReceiverSystem. Here Type “Hello”.
 Under Input there are two things,
o When Operation is Client, then the Server’sIPAddress (192.168.1.2)
should be given in the Server IP Address field.
o When Operation is Server, then the Server’sIPAddress (192.168.1.1)
would be automatically filled in the Local IP Address field.
Sample Output:
 On the Right hand side panel there is an InputField “ReceivedData”, where Data
would get displayed. “Hello” is the Data that is received from the ClientSystem.
356
TCP
 First the Server should click on the Run button after which the Client should
click on the Run button to Create the socket
 Client should click on the Connect button to establish the connection with
server.
 The Client should click on the Send button to transmit the data to the Server.
 The Client should click on the Close button to terminate the Connection with
Server.
 If the Data is successfully transmitted then the SentData would be Received in
the ServerSystem.
UDP
 First the Server should click on the Run button after which the Client should
click on the Run button to Create the socket
 The Client should click on the Send button to transmit the data to the Server.
 The Client should click on the Close button to terminate the Connection with
Server.
 If the Data is successfully transmitted then the SentData would be Received in
the ServerSystem.
357
9.5.41 PC to PC Communication – Chat Application TCP
Pre – Conditions
txt.
358
d. Select Input
359
d. Select Setting.
gcc -C Filename.c
360
before executing:
The data format in the input file is as Write the received message
follows, Ex:
Receive Input Tetcos:-Hello!!!!!!!!!!!!!!!
Protocol=TCP
Local User Name=Tetcos
Send
Protocol=TCP
Number of Users=2
1=192.168.0.1
2=192.168.0.2
Tetcos:-Hello!!!!!!!!!!!
361
Interface source code written in C is given using this the user can write the TCP chat
functions. To view the interface source code, go to
NetSim Installation path / src / Programming/ ChatTCP.c
362
9.5.42 PC to PC Communication – Chat Application UDP
Pre – Conditions`
txt.
For Visual Studio complier 2010 (10.0 versions), the library file linkage must be made in the
following way:
363
d. Select Input
364
d. Select Setting.
gcc -C Filename.c
365
before executing:
The data format in the input file is as Write the received message
follows,. Ex:
Receive Input 192.168.0.2:- Requesting for the
Protocol=UDP connection
Local User Name=Tetcos
Send
Protocol=TCP
Number of Users=2
1=192.168.0.1
2=192.168.0.2
Tetcos:-Hello!!!!!!!!!!!
366
Interface source code written in C is given using this the user can write UDP Chat functions.
NetSim Installation path / src / Programming/ ChatUDP.c
Sample Scenarios:
Objective - Send and Receive the data using PC to PCCommunication – Chat Application
How to Proceed? -Two to Ten Systems are required to perform this experiment.
The objective can be executed in NetSim using the programming exercise available. In the
Programming menu selectPC to PC Communication  Chat Application.
 Select a Protocol from the following,
o TCP
o UDP
 On the Right hand side panel there is an InputField “Send Data”, where Data
needs to be typed in. This Data is later sent to the ReceiverSystem. Here Type
“Hello”.
 On the Right hand side panel there is “Receive Data”, where data is received
from user. Ex. “Hello”
 Under Input there are two things,
o Number of users must be select between one to ten
o Enter the IP address of the data where needs to be in all the column in the
input pane.
367
Sample Output:
 On the Right hand side panel there is an InputField “ReceivedData”, where Data
would get displayed. “Hello” is the Data that is received from the users.
TCP
 Click Run button to create the socket and start Receive Data from the users.
 Click Send button to transmit the data to the users.
 Click Refresh button to terminate the connection.
UDP
 Click Run button to create the socket and start Receive Data from the users.
 Click Send button to transmit the data to the users.
368
9.5.43 Scheduling - First In First Out (FIFO)
This section guides the user to link his/her own code for Scheduling - FIFO to NetSim.
Pre - Conditions
The program should read the data from „Input.txt‟ file that is available in the temporary
directory.
The program should write the output data to „Output.txt’ file that is available in the
temporary directory.
Methodology screen
File Format
Output_Link_Capacity=100 Output.txt file format is as follows,

Node‟s_Priority=8,7,6,5,4,3,2,1, Seconds>no of bits transmitted in node
1>Transmission sequence of node 1>... no of bits
Node‟s_Capacity=0,0,500,0,0,0,0,0,
transmitted in node 8>Transmission sequence of
node 8>
Sample Output File
1>0>0>0>0>100>1>0>0>0>0>0>0>0>0>0>0>
2>0>0>0>0>100>1>0>0>0>0>0>0>0>0>0>0>
3>0>0>0>0>100>1>0>0>0>0>0>0>0>0>0>0>
4>0>0>0>0>100>1>0>0>0>0>0>0>0>0>0>0>
5>0>0>0>0>100>1>0>0>0>0>0>0>0>0>0>0>
369
Interface source code written in C is given using this the user can write only the Scheduling
inside the function fnFIFO() using the variables already declared. To view the interface
source code, go to
NetSim Installation path / src / Programming/ FIFO.c
Sample Scenarios:
Objective - The objective is to allocate the output capacity among the various input
capacities using First In First Out (FIFO) Scheduling algorithm.
exercise available. In the Programming menu selectScheduling.
Sample Input - By using the InputPanel that is available on the left hand side a
 Algorithm should be selected as FirstIn First Out (FIFO).
 Under Input field,
0. EnterOutputLinkCapacity which is in MBPS. The options that are
available for selecting are 100, 200, 300, …………… 1000 MBPS. Select
400 MBPS.
1. EnterBits / Node for one second (limit 0 - 9999) in the fields available.
i.e. Node1 - “100” , Node2 - “100”, ………………….., Node8 - “100”.
o The Priority for the Node needs to be given. Click to Select or Deselect
the Priority of a Node. In this Sample the Priorities are as follows,
Node Priority
Number Given
1 7
2 6
3 8
4 3
370
5 2
6 1
7 5
8 4
 Click on the Run button.
Output
Note: The Transmission of the data takes place in the following sequence. The Bits /
Node are represented in different colors. These colors indicate the order in which the
transmission takes place.
The Transmission Sequence  1 2 3 4 5 6 7 8.

Seconds 1 2
Node1 0 100
Node2 0 100
Node3 100 0
Node4 0 100
Node5 0 100
Node6 100 0
Node7 100 0
Node8 100 0
371
9.5.44 Scheduling - Max - Min Fair (MMF)
This section guides the user to link his/her own code for Scheduling - MMF to NetSim.
Pre - Conditions
The program should read the data from „Input.txt‟ file that is available in the application
path.
application path.
Methodology screen
File Format
Output_Link_Capacity „Output.txt‟ file format is as follows.

=100 1st second >Output rate of node 1 >Priority of Node 1>………..>Output
Node‟s_Capacity=0,0, rate of node 8.Priority of Node8
300,0,0,0,0,0, 2nd second >Output rate of node 1 >Priority of Node 1>………..>Output
rate of node 8.Priority of Node8
Nth second >Output rate of node 1 >Priority of Node 1>………..>Output
rate of node 8.Priority of Node8
Sample File data
1>0.00>0>0.00>0>100.00>1>0.00>0>0.00>0>0.00>0>0.00>0>0.00>0>
2>0.00>0>0.00>0>100.00>1>0.00>0>0.00>0>0.00>0>0.00>0>0.00>0>
3>0.00>0>0.00>0>100.00>1>0.00>0>0.00>0>0.00>0>0.00>0>0.00>0>
372
inside the function fnMMFA () using the variables already declared. To view the interface
source code, go to
NetSim Installation path / src / Programming/ MMF.c
Sample Scenarios:
Objective - The objective is to allocate the output capacity among the various input
capacities using Max-Min Fare(MMF) Scheduling algorithm.
exercise available. In the Programming menu selectScheduling.
 Algorithm should be selected as Max - Min Fair (MMF).
 Under Input field,
0. EnterOutputLinkCapacity which is in MBPS. The options that are available
for selecting are 100, 200, 300, …………… 1000 MBPS. Select100MBPS.
1. EnterBits / Node for one second (limit 0 - 9999) in the fields available.
i.e. Node1 - “100” , Node2 - “100”, ………………….., Node8 - “100”.
 Click on the Run button.
Output
The Transmission of the data takes place in the following sequence. The Bits / Node
are represented in different colors. These colors indicate the order in which the
transmission takes place.
373
The Transmission Sequence  1 2 3 4 5 6 7 8.
Seconds 1 2 3 4 5 6 7 8
Node1 12.50 12.50 12.50 12.50 12.50 12.50 12.50 12.50
Node2 12.50 12.50 12.50 12.50 12.50 12.50 12.50 12.50
Node3 12.50 12.50 12.50 12.50 12.50 12.50 12.50 12.50
Node4 12.50 12.50 12.50 12.50 12.50 12.50 12.50 12.50
Node5 12.50 12.50 12.50 12.50 12.50 12.50 12.50 12.50
Node6 12.50 12.50 12.50 12.50 12.50 12.50 12.50 12.50
Node7 12.50 12.50 12.50 12.50 12.50 12.50 12.50 12.50
Node8 12.50 12.50 12.50 12.50 12.50 12.50 12.50 12.50
374
9.5.45 Shortest Path - Floyd’s
This section guides the user to link his/her own code for shortest path – Floyd‟s to NetSim.
Pre - Conditions
directory.
The program should write the output data to „Output.txt‟ file that is available in the temporary
directory.
File Format
Algorithm=Floyd‟s Consider the source node is 1

No_of_Router=3 Distance>0>1>2>1>2>1>
Distance: Path>0>1>2>1>4>1>
999>5>1> The first line has the all the distance
5>999>10> values from the source node to all the
other connected nodes.
1>10>999>
The second line has the path values from
Source_Router=1 the source node to all the other nodes.
Destination_Router=3 The first line contains the values stored in
Note: the distance array (single dimensional
array) used in the algorithm.
„>‟ is the delimiter symbol, which is used
to separate each input. The second line contains the values stored
in the path array (single dimensional
array) used in the algorithm.
375
Sample Output:
1>2>3>
1>2>
1>3>
1>
>>>
path_FS>
0>0>0>
0>0>1>
0>1>0>
distance_FS>
0>5>1>
5>0>6>
1>6>0>
Note:
The string Distance and Path in the file is
compulsory. The output must be stored in
the same format
inside the function fnFloyd() using the variables already declared. To view the interface
source code, go to
NetSim Installation path / src / Programming/ Floyds.c
Sample Scenarios:
Objective - The objective is to find the Shortest Path between the two Routers using the
Floyds algorithm.
How to Proceed? - The objective can be executed in NetSim using the Programming
exercise available. Under Programming Menu select Shortest Path.
376
 Select the Algorithm as Floyd’s.
 Number of Routers needs to be selected. Minimum of 3Routers and Maximum
of 8Routers can be selected. Let us consider 4 Routers are selected.
 Source Router needs to be given. Let Router 4 be the Source Router.
 Destination Router also needs to be given. Let Router 1 be the Destination
Router.
 Click on 2 Routers to give the distance between those 2 Routers. A blue arrow
would be pointing from the Source Node to the Destination Node. The Distances
between the Routers that needs to be given are as follows,
1. Router 4 and Router 1  67 Km,
4. Router 3 and Router 2  56 Km, and
5. Router 1 and Router 2  70 Km.
 Click on Run button to view the output in the Routing Table.
Output - The Output for the above Scenario is as follows,

 Click the Run button to view program output.
 The Output is obtained in a Routing Table. All possible Routes and the
corresponding Distance are obtained. Below is a Routing Table for the above
Inputs,
Routing Table
Route Distance[KM]
4>1> 67
4>3>1> 64
4>3>2> 102
4>3> 46
4> 0
 The ShortestPath would be highlighted in green color.

 Click on Refresh Button to Refresh the screen and create fresh Scenarios.
377
9.5.46 Shortest Path - Link State
This section guides the user to link his/her own code for shortest path - Link State Routing to
NetSim.
Pre - Conditions
directory.
temporary directory.
Input.txt contains the distance matrix given Consider the source node is 1
by the user, along with the source node, Distance>0>1>2>1>2>1>
destination node and the total number of
nodes. Here, we have the input as a Path>0>1>2>1>4>1>
SYMMETRIC matrix. The format of The first line has the all the distance values
input.txt is, for example, from the source node to all the other
Algorithm=Link_State connected nodes.
No_of_Router=3 The second line has the path values from
the source node to all the other nodes.
Distance:
The first line contains the values stored in
999>6>5>
the distance array (single dimensional array)
6>999>7> used in the algorithm.
5>7>999> The second line contains the values stored
in the path array (single dimensional array)
Source_Router=1
used in the algorithm.
Destination_Router=2
Sample Output:
Note:
378
„>‟ is the delimiter symbol, which is used to 1>2>
separate each input. 1>3>2>
1>3>
1>
>>>
Distance>0>6>5>
Path>1000>1>1>
Note:
The string Distance and Path in the file is
compulsory. The output must be stored in
the same format.
inside the function fnDijkstra() using the variables already declared. To view the interface
source code, go to
NetSim Installation path / src / Programming/ LinkState.c
Sample Scenarios:
Objective - The objective is to find the Shortest Path between the two routers using the
Link State algorithm.
How to Proceed? - Under ProgrammingMenu select ShortestPath.

 Select the Algorithm as RunedState.
 Number of Routers needs to be selected. Minimum of 3Routers and Maximum
of 8Routers can be selected. Select 5 Routers.
 SourceRouter needs to be given. Let Router 5 be the SourceRouter.
 DestinationRouter also needs to be given. Let Router 3 be the
DestinationRouter.
379
 Click on 2 Routers to give the distance between those 2 Routers. A blue Line
would be pointing from the SourceNode to the DestinationNode. The Distances
between the Routers that needs to be given are as follows,
1. Router 1 and Router 2  35,
5. Router 4 and Router 5  67, and
6. Router 5 and Router 2  58.
 Click on Run button to view the output in the RoutingTable.
Output - The Output for the above Scenario is as follows,

 Click the Run button to view program output.
 The Output is obtained in a RoutingTable. All possible Routes and the
corresponding Distance are obtained. Below is a RoutingTable for the above
Inputs,
 The ShortestPath would be highlighted in Green color in the RoutingTable.
 Click on RefreshButton to Refresh the screen and create fresh Scenarios.
Routing Table
Route Distance[KM]
5>2>1>4>3> 173
5>2>1>4> 113
5>2>1> 93
5>2>3> 88
5>2> 58
5>4>1>2>3> 152
5>4>1>2> 122
5>4>1> 87
5>4>3> 127
5>4> 67
5> 0
380
9.5.47 Sliding Window Protocol - Go Back N
This section guides the user to link his/her own code for Go Back N to NetSim.
Pre - Conditions
txt.
Window Size:
The Window Size for Go Back N is 7
Algorithm=Go_Back_N Value1>Value2>Value3>Value4>
Data_File=C:\Users\P.Sathishkumar\D Types:
ocuments\1 Th.txt> There are five types of formats of writing in
Bit_Error_Rate=6 the output file.
Sequence_Number=3 Each format is written in specific condition,
the types are explained below.
Window_Size=7
The condition of writing the types is
explained in the algorithm.
Type1:
Value1 - "CNT",
Value 2 -output of the slidingcount function
Value 3 - "FRAMES"
381
Value 4 - "TRANSMIT"
Type2:
Value1 - "DT",
Value 2 -Frame number,
Value 3 - Frame‟s Source address,
Value 4 - Frame‟s Destination address.
Type3:
Value 1 - "EV",
Value 2 - Output of the intro_error function,
Value 3 - Frame‟ Source address,
Type4:
Value 1 - "ACK",
Value 2 - "POS",
Value 3 - Acknowledgement frame‟s Source
Address,
Value 4 - Acknowledgement frame‟s
Destination Address.
Type5:
Value 1 - "DEL"
Value 2 - count of frames being deleted
Value 3 - "FRAME"
Value 4 - "DELETED"
„Output.Txt‟ ismandatory.
Values in Quotes"" to be written into file
„Output.Txt‟ as it is including Case.
DT>Frame No>node1>node2> (DT denotes
Data from node 1 to node 2)
EV>Error Flag>node1>node2> (EV denotes
Error Value - i.e If the above frame has error
then set the error flag as 1 else set the flag as
0)
ACK>POS>node2>node1>
(Acknowledgement for that above frame
received is sent to node 2 to node 1)
Ex:
CNT>1>FRAMES>TRANSMIT>
382
DT>1>node1>node2>
EV>0>node1>node2>
Interface source code written in C is given using this the user can write only the Sliding
Window Protocols - Go Back N inside the function GoBackN () using the variables already
declared. To view the interface source code, go to
NetSim Installation path / src / Programming/ GobackN_SW.c
Sample Scenarios:
Objective - Send and receive the data using Sliding Window Protocol - Go BackN.
exercise available. Under ProgrammingMenu select Sliding WindowProtocolGo Back
N.
 SelectGoBackN as Algorithm.
 Create a “Datafile (.txt)” and save it on the disk.
 Select the path of the above created “Datafile (.txt)” which could be Maximum
of 100000bytes.
 SelectBit Error Rate (BER) as “10^-5” from the drop down menu.
 SelectSequencenumber (Bits) as “3” from the drop down menu.
 A default value is entered for WindowSize as “7”.
1. Then Run button need to be clicked.
383
2. An OutputTable is obtained when Run button is clicked. In the OutputTable,
Transmittedframe (Data and Acknowledgement) and their corresponding Counts is
obtained. The TotalCount is also obtained. The table is given below,
Output
Total data frames to be transmitted - 24
Transmitted frame Count
Data 30
Acknowledgement 5
Total = 35
Note - The “Total data frames to be transmitted” and “Total count” in the Output
table depends on size of the “.txt” file.
3. The details of the DataFrames flowing from Node1 to Node 2 are obtained on the
right hand side panel. Below are the details that is obtained in the tool,
o Data Frame 1 is flowing from Node1 to Node2 with no error.
o Data Frame 4 is flowing from Node1 to Node2 with error.
o Acknowledgement from Node2 to Node1.
384
 Once the sample experiment is done, then Refresh button can be clicked to create
new samples.
385
9.5.48 Sliding Window Protocol - Selective Repeat
This section guides the user to link his/her own code for Selective Repeat to NetSim.
Pre - Conditions
txt.
Window Size:
The Window Size for Selective Repeat is 7
Algorithm=Selective_Repeat Value1>Value2>Value3>Value4>
Data_File=C:\Users\P.Sathishkumar Types:
\Documents\1 Th.txt> There are five types of formats of writing in
Bit_Error_Rate=5 the output file.
Sequence_Number=3 Each format is written in specific condition,
Window_Size=4
Type1:
Value1 - "CNT",
Value 2 - output of the slidingcount
function
Value 3 - "FRAMES"
386
Type2:
Value1 - "DT",
Value 2 - Frame number,
Type3:
Value 1 - "EV",
Type4:
Value 1 - "ACK",
Value 2 - "POS",
Source Address,
Type5:
Value 1 - "DEL"
Value 3 - "FRAME"
Value 4 - "DELETED"
Note: The above convention to write into
the „Output.Txt‟ ismandatory.
Error Value - i.e If the above frame has
error then set the error flag as 1 else set the
flag as 0)
Ex:
387
DT>1>node1>node2>
EV>0>node1>node2>
Interface source code written in C is given using this the user can write only the Sliding
Window Protocol - Selective Repeat inside the function SelectiveRepeat () using the
variables already declared. To view the interface source code, go to
NetSim Installation path / src / Programming/ SelectiveRepeat_SW.c
Sample Scenarios:
Objective - Send and receive the data using Sliding Window Protocol - Selective Repeat.
exercise available. Under Programming Menu select Sliding WindowProtocolSelective
Repeat.
 Select Selective Repeat as Algorithm.
 Create a “Data file (.txt)” and save it on the disk.
 Select the path of the above created “Data file (.txt)” which could be Maximum
of 100000 bytes.
 Select Bit Error Rate (BER) as “10^-5” from the drop down menu.
 Select Sequence number (Bits) as “3” from the drop down menu.
 A default value is entered for Window Size as “4”.
388
2. An Output Table is obtained when Run button is clicked. In the Output Table,
Transmitted frame (Data and Acknowledgement) and their corresponding Counts
is obtained. The Total Count is also obtained. The table is given below,
Output
Data 26
Acknowledgement 7
Total = 33
Note - The “Total data frames to be transmitted” and “Total count” in the
Output table depends on size of the “.txt” file.
3. The details of the Data Frames flowing from Node 1 to Node 2 are obtained on the
right hand side panel. Below are the details that is obtained in the tool,
o Data Frame 1 is flowing from Node1 to Node2 with no error
o Data Frame 4 is flowing from Node1 to Node2 with error
o Acknowledgement from Node2 to Node1
o Data Frame 6 is flowing from Node1 to Node2 with error
389
new samples.
390
9.5.49 Sorting Technique - Bubble Sort
This section guides the user to link his/her own code for Sorting Algorithm to NetSim.
Pre - Condition
Methodology screen
File Format
Ascending Order type>index 1>index 2>

Sorting_Type=Bubble type 0 : specifies Positioning the data value
index that ha
Sorting_Order=Ascending
type 1 : specifies the two index following it
Total_Number=3
are being compared
Number_to_Sort=5,4,3
type 2 : specifies the two index following it
Descending Order are being swapped
Sorting_Type=Bubble The following types are used in Quick Sort :
Sorting_Order=Descending type 3 : specifies the two index, where index
Total_Number=3 1 value is copied to index 2 value.
Number_to_Sort=4,5,6 type 4 : specifies the two index, where
Position data index value of index1 is copied
391
to the index 2 value.
index 1 : index 1 is the index of array that
points to the first data that is being swapped
or compared.
index 2 : index 2 is the index of array that
points to the second data that is being
swapped or compared.
Sample Output:
Ascending Order:
1>0>1>
2>0>1>
1>1>2>
2>1>2>
1>0>1>
2>0>1>
Descending Order:
1>0>1>
2>0>1>
1>1>2>
2>1>2>
1>0>1>
2>0>1>
Interface source code written in C is given using this the user can write only the Sorting
Algorithm inside the function fnBubblesort () using the variables already declared. To view
NetSim Installation path / src / Programming/ BubbleSort.c
Sample Scenarios:
392
Objective - To study the working of Sorting Techniques.
How to Proceed? -
The objective can be executed in NetSim using the programming exercise available, under
programming user has to select Sorting Techniques.
 Select the Bubble Sort as Sorting Type.
 Select the Sorting Order as either Ascending or Descending.
 Select the total number that has to be sorted. The values available are from 3
to 25.
 Enter the Number Value in the field provided. The value entered should be
within the range of 1 to 9999.
 According to the Sorting Type selected the Output would vary.
 Number of Comparison would be obtained.
 Number of Swapping would be obtained.
 A table with the values tabulated would be obtained.
create New Samples.
393
9.5.50 Sorting Technique - Insertion Sort
Pre - Condition
Methodology screen
File Format

Sorting_Type=Insertion type 0 : specifies Positioning the data
value index that ha
type 1 : specifies the two index
Total_Number=3
following it are being compared
following it are being swapped
Descending Order The following types are used in Quick
Sorting_Type=Insertion Sort :
Sorting_Order=Descending type 3 : specifies the two index, where

index 1 value is copied to index 2 value.
Total_Number=3
type 4 : specifies the two index, where
394
Number_to_Sort=1,9,3 Position data index value of index1 is
copied to the index 2 value.
index 1 : index 1 is the index of array
that points to the first data that is being
that points to the second data that is
being swapped or compared.
Sample Output:
Ascending Order:
1>0>1>
2>0>1>
1>1>2>
2>1>2>
1>0>1>
2>0>1>
Descending Order:
1>0>1>
2>0>1>
1>1>2>
2>1>2>
1>0>1>
Algorithm inside the function fnInsertsort () using the variables already declared. To view the
NetSim Installation path / src / Programming/ InsertionSort.c
Sample Project:
395
How to Proceed? -
 Select the Insertion Sort as Sorting Type.
to 25.
create New Samples.
396
9.5.51 Sorting Technique - Quick Sort
Pre - Condition
Methodology screen
File Format

Sorting_Type=Quick type 0 : specifies Positioning the data
value index that ha
Total_Number=3
Sorting_Type=Quick Sort :

Total_Number=3
397
Number_to_Sort=22,33,44 type 4 : specifies the two index, where
Position data index value of index1 is
Sample Output:
Ascending:
0>0>0>
1>0>2>
3>1>0>
4>0>1>
0>2>2>
0>0>0>
Descending:
0>0>0>
3>2>0>
1>0>1>
4>0>2>
0>0>0>
1>0>1>
4>0>0>
0>1>1>
Algorithm inside the function fnQuicksort () using the variables already declared. To view
NetSim Installation path / src / Programming/ QuickSort.c
398
Sample Scenarios:
How to Proceed? -
 Select the Quick Sort as Sorting Type.
to 25.
create New Samples.
9.5.52 Sorting Technique - Selection Sort
399
Pre - Condition
Executing the required concept and the results of the program should be written into the
Methodology screen
File Format

Sorting_Type=Selection type 0 : specifies Positioning the data
value index that ha
Total_Number=3
Sorting_Type=Selection Sort :

Total_Number=3
type 4 : specifies the two index, where
Number_to_Sort=55,11,22 Position data index value of index1 is
400
Sample Output:
Ascending:
0>0>0>
1>1>0>
0>1>1>
1>2>1>
0>2>2>
2>0>2>
0>1>1>
1>2>1>
Descending:
0>0>0>
1>1>0>
1>2>0>
0>1>1>
1>2>1>
0>2>2>
2>1>2>
Algorithm inside the function select() using the variables already declared. To view the
NetSim Installation path / src / Programming/ SelectionSort.c
 Open file location in Windows 7

 Open file location in Windows Vista
 Properties  find target in Windows XP.
401
Sample Scenarios:
How to Proceed? -
 Select the Selection Sort as Sorting Type.
to 25.
create New Samples.
402
9.5.53 Spanning Tree – Borovska
This section guides the user to link his/her own code for Spanning Tree using Borovska
algorithm to NetSim.
Pre - Conditions
txt.
Algorithm=Borovska „Output.txt ‟ file has the edges in the

spanning tree, which is selected from
No_of_Switches=3
the input edges.
No_of_Edges=3
Node1>Node2>Cost>
Source_Switch=3,Destination_Switch=1,
Example:
Distance=11,
1>2>22>
Distance=22, 1>3>11>
Distance=33,
Interface source code written in C is given .Using this the user can write only the Borovska
algorithm inside the function fnBorovska() using the variables already declared. To view the
403
NetSim Installation path / src / Programming/ Boruvska.c
Sample Scenarios:
Objective - To find a SpanningTree for a network using Borovska’s algorithm.
exercise available. In the Programming Menu selectSpanning Tree.
Sample Input
 SelectBorovska as Algorithm from the list available.
 Select the Number of Switches. Select 4 Switches as an Input.
 Click on 2 Switches to give the distance between them. Similarly connect all the
Switches that are available in the network. The Distances between the Routers
that needs to be given are as follows,
o Switch 1 and Switch 2  67 Km
 Click on Run button to execute. Refresh button can be used if new Inputs have
to be given.
Sample Output
 The SpanningTreeTable with the Path (Source Switch and Destination Switch)
and Distance is obtained. Below is the Table that is obtained for the above inputs,
404
Spanning Tree Table
Path Distance[KM]
1 2 67
3 4 56
1 4 46
 The “Length of the SpanningTree (KM)” would be given below in the output
panel. The SpanningTreePath consists of green lines, whereas the Non-
SpanningTree consists of red lines. Here in this Sample, “Length of the
Spanning Tree (KM)  169”.
new samples.
405
9.5.54 Spanning Tree – Kruskal
This section guides the user to link his/her own code for Spanning Tree using Kruskal
Pre - Conditions
txt.
Algorithm=Kruskal's „Output.txt ‟ file has the edges

in the spanning tree, which is
No_of_Switches=3
selected from the input edges.
No_of_Edges=3
Node1>Node2>Cost>
Source_Switch=3,Destination_Switch=1,Distance=23,
Example:
3>1>23>
1>2>34>
Interface source code written in C is given .Using this the user can write only the Kruskal
algorithm inside the function fnKruskal() using the variables already declared. To view the
NetSim Installation path / src / Programming/ Kruskal.c
406
Sample Scenarios:
Objective - To find the SpanningTree for a network by using Kruskal algorithm.
Sample Input
 SelectKruskal as Algorithm from the list available.
to be given.
Sample Output
 The SpanningTreeTable with the Path (Source Switch and Destination Switch)
Spanning Tree Table
Path Distance[KM]
1 4 46
407
4 3 56
1 2 67
panel. The SpanningTree Path consists of green lines, whereas the Non-
SpanningTree (KM)  169”
new samples.
408
9.5.55 Spanning Tree – Prims
This section guides the user to link his/her own code for Spanning Tree using Prims
Pre - Conditions
txt.
Algorithm=Prim's „Output.txt‟ file has the edges in the

spanning tree, which is selected
No_of_Switches=3
from the input edges.
No_of_Edges=3
Node1>Node2>Cost>
Source_Switch=1
Example:
1>3>44>
1>2>55>
Interface source code written in C is given .Using this the user can write only the Prim‟s
algorithm inside the function fnPrims() using the variables already declared. To view the
409
NetSim Installation path / src / Programming/ Prims.c
Sample Scenarios:
Objective - To find a SpanningTree for a network using Prims algorithm.
Sample Input
 SelectPrim’s as Algorithm from the list available.
 SourceSwitch can be any 1 from list.Here, SourceSwitch is selected as”3”.
to be given.
410
Sample Output
 The SpanningTreeTable with the Path (SourceSwitch and Destination Switch)

SpanningTreeTable
Path Distance[KM]
3 4 56
4 1 46
1 2 67
panel. The SpanningTree Path consists of green lines, whereas the Non-
Spanning Tree (KM)  169”.
New Samples.
411
9.5.56 Transmission Flow Control - Go Back N
This section guides the user to link his/her own code for Go Back N to NetSim.
Pre - Conditions
extension txt.
Window Size:
The Window Size for Go Back N is 7
Algorithm=Go_Back_N Value1>Value2>Value3>Value4>
Data_File=C:\Users\P.Sathishkumar\ Types:
Documents\1 Th.txt> There are five types of formats of writing in
BER=0 the output file.
Each format is written in specific condition,
Type1:
Value1 - "CNT",
Value 2 - output of the slidingcount function
Value 3 - "FRAMES"
412
Type2:
Value1 - "DT",
Type3:
Value 1 - "EV",
Type4:
Value 1 - "ACK",
Value 2 - "POS",
Address,
Type5:
Value 1 - "DEL"
Value 3 - "FRAME"
Value 4 - "DELETED"
„Output.Txt‟ is mandatory.
0)
Ex: CNT>1>FRAMES>TRANSMIT>
DT>1>node1>node2>
413
EV>0>node1>node2>
DEL>1>FRAME>DELETED>
Interface source code written in C is given using this the user can write only the Transmission
Flow Control - Go Back N inside the function GoBackN () using the variables already
NetSim Installation path / src / Programming/ GoBackN_TFC.c
Sample Scenarios:
Objective - Send and receive the data using Transmission Flow Control - Go BackN.
exercise available. Under ProgrammingMenu select Transmission Flow ControlGo
Back N.
 SelectGoBackN as Algorithm.
 Create a “Datafile (.txt)” and save it on the disk.
 Select the path of the above created “Datafile (.txt)” which could be Maximum
of 100000bytes.
 SelectBit Error Rate (BER) as “10^-5” from the drop down menu.
414
2. An OutputTable is obtained when Run button is clicked. In the OutputTable,
Transmittedframe (Data and Acknowledgement) and their corresponding
Counts is obtained. The TotalCount is also obtained. The table is given below,
Output
Data 30
Acknowledgement 5
Total = 35
Note - The “Total data frames to be transmitted” and “Total count” in the Output
table depends on size of the “.txt” file.
new samples.
415
9.5.57 Transmission Flow Control - Selective Repeat
This section guides the user to link his/her own code for Selective Repeat to NetSim.
Pre - Conditions
extension txt.
Window Size:
The Window Size for Selective Repeat is 7
Output File Format

Input File Format
Algorithm=Selective_Repeat Value1>Value2>Value3>Value4>
Documents\1 Th.txt> There are five types of formats of writing in the
BER=0 output file.
Each format is written in specific condition, the
types are explained below.
The condition of writing the types is explained
in the algorithm.
Type1:
Value1 - "CNT",
Value 3 - "FRAMES"
416
Type2:
Value1 - "DT",
Type3:
Value 1 - "EV",
Type4:
Value 1 - "ACK",
Value 2 - "POS",
Address,
Type5:
Value 1 - "DEL"
Value 3 - "FRAME"
Value 4 - "DELETED"
then set the error flag as 1 else set the flag as 0)
ACK>POS>node2>node1> (Acknowledgement
for that above frame received is sent to node 2
to node 1)
Ex:
417
DT>1>node1>node2>
EV>0>node1>node2>
DEL>1>FRAME>DELETED>
Flow Control -Selective Repeat inside the function SelectiveRepeat () using the variables
already declared. To view the interface source code, go to
NetSim Installation path / src / Programming/ SelectiveRepeat_TFC.c
Sample Scenarios:
Objective - Send and receive the data using Transmission Flow Control - Selective Repeat.
exercise available. Under Programming Menu select Transmission Flow
ControlSelective Repeat.
 Select Selective Repeat as Algorithm.
 Create a “Data file (.txt)” and save it on the disk.
 Select the path of the above created “Data file (.txt)” which could be Maximum
of 100000 bytes.
 Select Bit Error Rate (BER) as “10^-5” from the drop down menu.
2. An Output Table is obtained when Run button is clicked. In the Output Table,
Transmitted frame (Data and Acknowledgement) and their corresponding
Counts is obtained. The Total Count is also obtained. The table is given below,
418
Output
Total data frames to be transmitted -
Data
Acknowledgement
Total =
Note - The “Total data frames to be transmitted” and “Total count” in the Output table
depends on size of the “.txt” file.
new samples.
419
9.5.58 Transmission Flow Control - Stop and Wait
This section guides the user to link his/her own code for Stop and Wait to NetSim.
Pre - Conditions
extension txt.
Output File Format

Input File Format
Algorithm=Stop_and_Wait Value1>Value2>Value3>Value4>
Documents\1 Th.txt> There are five types of formats of writing in
BER=0 the output file.
Each format is written in specific condition,
The condition of writing the types is explained
in the algorithm.
Type1:
Value1 - "CNT",
Value 3 - "FRAMES"
Type2:
Value1 - "DT",
420
Type3:
Value 1 - "EV",
Type4:
Value 1 - "ACK",
Value 2 - "POS",
Address,
Type5:
Value 1 - "DEL"
Value 3 - "FRAME"
Value 4 - "DELETED"
0)
Ex:
DT>1>node1>node2>
EV>0>node1>node2>
421
Flow Control - Stop and Wait inside the function stopandwait() using the variables already
NetSim Installation path / src / Programming/ StopandWait.c
Sample Scenarios:
Objective - Send and receive the data using Transmission Flow Control– Stop and wait.
exercise available. Under Programming Menu select Transmission Flow Control Stop
and wait.
 Stop and Wait needs to be selected for Algorithm.
 The path of the “Data file (.txt)” should be entered.
 Bit Error Rate (BER) should be selected.

 When the Run Button is clicked the Tool generates the Output in the following
format,
422
Output
Total data frames to be transmitted
Data
Acknowledgement
Total =
create New Samples.
423
9.6 Programming exercise - How to practice without NetSim
Step 1: Copy Interface Source Code

Click on Interface Source Code and save the code in a text file.
For Example:
As an example, Shortest Path programming

exercise is being considered.
Open the programming exercise and select

Interface Source Code.
Save the Interface source code in another txt

file.
Step 2: Create Input.txt file

Create a new text file with the name Input.txt.
The contents of the file will vary for each programming exercises and are specified in NetSim
User Manual under programming topic.
For Example:
Copy the input file contents from NetSim user manual and save it in a file called Input.txt
424
Sample:
Algorithm=Link_State
No_of_Router=3
Distance:
999>6>5>
6>999>7>
5>7>999>
Source_Router=1
Destination_Router=2
Save it in some other location. In this example, it is saved at D:\New.
Step 3: Create .exe file

Open C editor and write the Interface source code which was saved in the first text file. Also
add the code to be written by the user in the specific sections and compile it. Keep the .exe
file.
For Example:
Now in C editor (Dev C++ IDE is used here), copy the interface source code. In the interface
source code, void fnDijkstra() is not implemented.
425
After writing the code for the function void fnDijkstra(), create .exe file. The procedure to
create .exe file is explained in Section 9.2 of NetSim User Manual.
In this example, the exe file created is LinkState.exe
Step 4: Run in command prompt

Open command prompt, and go to the folder where the .exe file is saved.
There type
<EXE Name> “<blank>“ “<Path where Input.txt is saved>”;
For Example:
In this example, the exe file LinkState.exe and Input.txt is present at “D:\New”. So in
command prompt go to the folder where exe file is saved.
426
NOTE: For Chat programming exercise, type
For Sender: <EXE Name> “<blank>“ “<Path where Input.txt is saved>” “send”
For Receiver: <EXE Name> “<blank>“ “<Path where Input.txt is saved>” “receive”
Step 5: Check the output.txt file

After running in the command prompt, Output.txt file will be created at the same location
where Input.txt file is saved. User can compare and check the content of Output.txt file with
the NetSim user manual.
For Example: Here according to this example, the Output.txt file will be created at
“D:\New” folder. User can open the file and compare the content with NetSim user manual.
427
10 NetSim Emulator
NOTE: Emulator will be featured in NetSim only if Licenses for Emulator Add-on is available
10.1 Introduction
A network simulator mimics the behavior of networks but cannot connect to real networks.
NetSim Emulator enables users to connect NetSim simulator to real hardware and interact
with live applications.
10.1.1 Emulation: How Simulation interacts with the real world
A real PC (running NetSim Emulation Client) sends live traffic to the PC (running NetSim
Emulation Server). Whenever a packet arrives at the interface of server, this packet is
“modulated” into a simulation packet and sent from a source node (user selectable) in the
simulated network (user configurable) to a destination node (again user selectable). Upon
receipt of this packet at the destination, the packet is then “de-modulated” and sent back to a
real PC destination node (running NetSim Emulation Client). The real packet thus undergoes
network effects such as delay, loss, error etc. created virtually by NetSim Simulator.
428
10.2 Emulation Set-up:
The ideal set-up to run emulation would be to have a minimum of three (3) PC‟s. One would
be the real source, the second would run NetSim emulation server, and the third would be the
real destination.
Alternately, this set-up can also be managed where the two (2) PC's are running client
applications that communicate with the central server, where NetSim Emulation server is
running.
10.2.1 Setting up the NetSim Server:
 Run NetSim in Administrative Mode (Right Click on NetSim.exe  Run as

Administrator).
 User has to open any Stack based Network (Any network except Legacy Networks,
Wireless Sensor Network, Zigbee Network and Cellular Network) in NetSim with
Emulation.
 Create a network scenario of your choice (refer application examples provided) and
set the Application properties.
429
 In the Application Properties, set Application Type as “EMULATION”.
Assign real Source IP address and Destination IP address in the respective fields.
Then Click Accept.
 Set the Simulation Time as how long you want to perform the Emulation in
Real World. Do not run the simulation until setting up Emulation in the Client
system.
NOTE: If the Emulation Server is located in a different subnet from clients
 User has to configure the router settings of the real-world network so as to allow the
packets to be transmitted to the Emulation Server
For Example, if we consider a sample real world network scenario where the
Emulation clients and server are located in different subnets
Before Router C re-configuration
After Router C re-configuration
 Routing table of router C needs to be configured such that any packet having Source
Address as IP Address of Node 6 (Client Source) and Destination Address as IP
Address of Node 8 (Client Destination) must be routed to Emulation Server. NetSim
configuration will the ensure that the packet is re-injected with destination set to the
appropriate IP Address (set in the application properties)
10.2.2 Setting up the NetSim Client:
 Open command prompt in administrative mode.
430
 Type command,
route delete <Network Address>
then press Enter key. You will get “OK”. For example if your IP address is
192.168.0.4 and the subnet mask is 255.255.255.0 then the network address is
192.168.0.0 (Got by performing a bitwise AND of the IP Address and the subnet
mask)
 Type command
route add <Network Address>mask 255.255.255.0 <IP Address where

NetSim Emulation server is running> metric 1
here the subnet mask is taken as 255.255.255.0). After execution, you will get “OK”.
 Type command
netstat –r
To check if the IP configuration is done or not.
Note that in the above screenshot, for the network 192.168.0.0, the gateway address assigned
is 192.168.0.87 (Address of the system where NetSim Emulation Server is running).
431
10.2.3 Setting multiple Virtual Machines (VM) to act as Nodes for
Emulation
NOTE - VM enabled license are required
10.2.3.1 VMs sharing the same network as the host.
A computer on which one or more virtual machines are running is defined as a Host Machine.
Each virtual machine is called a Guest Machine. In this scenario, we have 3 VMs running in a
Host Machine – VM1, VM2 and VM3. Users can run NetSim License server in any system
connected to the network in which Host Machine is running.
Now right click on each VM and select Settings. Click on Network Adapter, and select
“Bridged: Connected directly to the physical network”. Also enable the “Replicate
Physical network connection state”.
An advantage of this technique is that, if the license server is running in another system,
connected to the same network as the original host, then NetSim running in the VM can
obtain the licenses.
432
10.2.3.2 VMs sharing a network but insulated from the host network.
A computer on which one or more virtual machines are running is defined as a Host Machine.
Each virtual machine is called a Guest Machine. In this scenario, we have 3 VMs running in a
Host Machine – VM1, VM2 and VM3. NetSim License server is running in one of these 3
VMs.
If user needs to create an internal network which is segregated from host network, follow the
steps
1. Right click on each VM and select Settings

2. Click on Network Adapter, and select “Custom: Specific Virtual network”
3. Select “VMnet8 (NAT)”
By default, a network address is assigned to this segregated network by VMware. To

configure this IP address, go to EDIT  Virtual Network Editor
433
User can modify the Subnet IP and Subnet Mask to suit their own preference.
The disadvantage of this technique is that, if the license server must compulsorily run in the
VM for NetSim to obtain the licenses.
434
10.3 Emulation examples in NetSim
10.3.1 Example Application 1 – PING (One way Communication)

10.3.1.1 Steps at Emulation Server:
I. Run NetSim in Administrative Mode and create a basic network Scenario in any stack
based protocol (Any network except Legacy Networks, Wireless Sensor Network,
Zigbee Network and Cellular Network) in NetSim. Screenshot of a sample scenario in
Internetworks is shown below
II. Go to Properties of Link1 and Link2 and set Uplink and Downlink Delay to 5000.
Click and drop the Application. Right click Application  select Properties.
III. In the Application Type select Emulation.
IV. Select Source and Destination ID according to the network scenario and change the
Source and Destination IP address according to the IP address of the real system.
435
V. Provide the Simulation Time as how long you want the Emulation to be performed.
Make sure client system(s) are ready and then click Run Simulation.
10.3.1.2 Steps at Source PC:
1. Before running simulation, start pinging the Destination from Source using command
“ping <Destination_IP> –t” and note down the time duration.
2. Follow steps as provided before in “Emulation Set-up: Setting up the NetSim

Client”.
3. Perform the steps at Emulation Server as provided and simulate. During simulation,
ping the destination system. You will notice that the present time duration is higher
than the earlier ping results. This is because the network created in NetSim has link
propagation delay. Also Wireshark (if installed) will automatically start capturing the
packets as soon as Emulation Server starts simulation.
(NOTE: In case if no ping messages can be sent from source to destination, disable
windows firewall and try again.)
4. The impact of the link propagation delay in NetSim Emulator is seen on a real packet.
436
10.3.2 Example Application 1 – PING (Two way Communication)
In PING (Two way communication), almost all the steps are same as PING (One way
communication), except that in NetSim Emulation server there will be two application
instead of one. One Application will be directed from Source to Destination node, while the
other application will be directed from Destination to Source node.
The difference caused in the network behavior is that in the first case (PING -One way
communication), the PING reply packets were not routed via NetSim Emulator. But in the
second case (PING -Two way communication), the PING reply packets will be routed via
NetSim Emulator, thereby the total delay will be approximately 21millisecond.
437
10.3.3 Example Application 2 – Video (One way Communication)
10.3.3.1 Steps at NetSim Emulation Server:
I. Run NetSim in Administrative Mode and create a basic network Scenario in any stack
II. Click and drop the Application. Right click Application  select Properties.
III. In the Application Type select Emulation.
IV. Select Source and Destination ID according to the network scenario and change the
Source and Destination IP address according to the IP Address of the real system and
click accept.
438
V. Provide the Simulation Time as how long you want the Emulation to be performed.
During Simulation you will notice a change in the quality of the video being played in the
destination PC. This is because the network created in NetSim has errors / delays etc in the
links. The impact of this loss / jitter / delay etc in NetSim Emulator is seen on a real video
stream.
1. Follow steps as provided before in “Running Emulation via GUI  Setting up the
NetSim Client”. Then open VLC Media player  Click Media menu  Select Stream
Option.
2. Click add button then select the video which you want to play
3. Click on Stream Option. Then click next button
4. Enable the display locally checkbox. Then select the RTP / MPEG Transport Stream from
the drop down list as shown in the below screen shot
439
5. Click on Add Button. Then enter the Destination IP address in the Address field and enter
a stream name (user defined) and click next button.
6. Select Video –MPEG-2 + MPGA (TS) option from the drop down list as shown in the
below screen shot. Then click next button
440
7. Perform all the steps at Emulation Server and then click on Stream button. Also Wireshark
(if installed) will automatically start capturing the packets as soon as Emulation Server starts
simulation.
10.3.3.3 Steps at Destination PC:
1. Follow steps as provided before in “Running Emulation via GUI–Setting up the

NetSim Client”. After performing all the steps at Source PC and NetSim Emulation Server,
open VLC Media Player Click on Toggle Playlist icon as shown in the below screenshot.
441
Toggle button is circled in red at the bottom of the screen shot
2. Double click on Network Stream (SAP) under local network. Then right click and play on
the stream name that appears on the screen.
3. In the streamed video, you will notice a change in the quality of the video being played in
the destination PC. Also Wireshark (if installed) will automatically start capturing the packets
as soon as Emulation Server starts simulation.
442
10.3.4 Example Application 3 – File Transfer using FileZilla (One
way Communication)

Client”. Run FileZilla Server software. Create a group by going to Edit  Groups 
Select “General” under Page:  Click Add in Groups  Give Any Name (Ex:
Admin) and click ok.
2. Go to Edit  User  General  Click Add in User  Give Any Name (Ex: User1)
and Select Group what you given in Group Setting (In this case, we provide “Admin”)
and click ok.
3. In Account Setting, select Enable account and set password and click ok.
443
4. Go to Shared folder  Add Folder to share (EX: FTP_FILES from Desktop) 
Select all the Files and Directories Permissions and set that folder as Home Directory
by selecting “Set as Home Dir”. Click Ok.

Client”. Run FileZilla Client software.
2. Enter the Host Name(Server System ip (EX: 192.168.0.133)) and Give the User,
Password that we created in Server side and give Port No = 21. Run Emulation server
and click Quick Connect. Drag and drop files from Local Site to Remote Site.
1. Run NetSim in Administrative Mode and create a basic network Scenario in any stack
based protocol (Any network except Legacy Networks) in NetSim. A sample scenario
in Internetworks is performed as shown with link speed set to 1 Mbps.
444
2. Click and drop the Application. Right click Application  select Properties.
3. In the Application Type select Emulation.
4. Select Source and Destination ID according to the network scenario and change the
click accept.
5. Provide the Simulation Time as how long you want the Emulation to be performed.
10.3.4.4 Results:
Transfer speed from client without emulation:
Transfer speed from client with emulation:
445
10.3.5 Example Application 4 –Skype (Two way Communication)
Internetworks is shown below.
2. Click and drop Application button. Right click Application  select Properties. As it
is two way communication, add and create two applications.
3. In both the Application Type select Emulation.
4. In one Application, select Source ID and Destination ID according to the network
scenario and change the Source and Destination IP address according to the IP
Address of the real system. In the second application, set the opposite of first
application, i.e. Source ID and IP address will be exchanged with Destination ID and
IP address. (Refer the IP settings in the screen-shot to get a clear picture)
446
1. Follow steps as provided before in “Emulation Set-up: Setting up the NetSim Client”.
2. Run Skype and make a call to the destination system (Make sure that Skype is running in
Destination PC).
3. Wireshark (if installed) will automatically start capturing the packets as soon as Emulation
Server starts simulation.
After performing all the steps at Source PC and NetSim Emulation Server, open Skype.
2. Wireshark (if installed) will automatically start capturing the packets as soon as Emulation
447
10.3.6 Example Application 5 – JPerf Network performance
measurement graphical tool (One way Communication)
2. Click and drop the Application. Right click Application  select Properties.
3. In the Application Type select Emulation.
4. Select Source and Destination ID according to the network scenario and change the
click accept.
448
Run JPerf and select Client and set Server Address as 192.168.0.145. User can edit the
Application Layer options, Transport Layer options and IP Layer options depending on the
type of data they want to transmit in the network.
2. Do not click “Run IPerf” until all the steps at NetSim Emulation Server are done. Also
Wireshark (if installed) will automatically start capturing the packets as soon as Emulation
449
Run JPerf and select Server.
2. Click on “Run IPerf” after the Source PC starts running JPerf.
450
11 Troubleshooting in NetSim
11.1 CLI mode
While running NetSim via CLI for the scenarios described in the Configuration file, you may
bump into few problems.
Note: While running NetSim via CLI, try to ensure that there are no errors in the
Configuration.xml file. The file, ConfigLog.txt, written to the windows temp path would
show errors, if any, found by NetSim’s config parser.
This section discusses some common issues and solutions:
Possible errors when running NetSim via CLI
11.1.1 I/O warning displayed in CLI mode:
Reason: While typing the CLI command if you enter wrong I/O Path, or if there is no
Configuration.xml file then the following error is thrown
Solution: Please check the I/O path.
451
11.1.2 Connection refused at server<-111> error displayed:
Wrong License information
Reason: If the license information is wrong then the following message will be shown.
Solution: In this example, license server IP address is 192.168.0.185 but it is given as

192.168.0.180. Here server IP address is wrong.Same error message is shown for wrong port
number, wrong tag name like–apppath,-iopath,-license. For example, if –appppath is typed
instead of –apppath then this message will be shown. So, check those details.
11.1.3 Unable to load license config dll(126) problem:
Apppath and I/O path have white spaces
Solution: If the folder name contains white space, then mention the folder path within double
quotes while specifying the folder name in the command prompt. For example, if app path
contains white space, then the app path must be mentioned within double quotes in the
command prompt.
452
11.1.4 “Error in getting License” error in CLI mode:
Simulation does not commence. “No license for product (-1)” is displayed in the command
prompt.
Example:
453
Solution:
NetSim is based on the client-server architecture. When NetSim runs in the client machine, it
will check for the license in the same machine, first. If license is not available in the same
machine, then “No license for product (-1)” will be displayed in the command prompt and the
server machine will be checked for the availability of license. If no license is available in the
server machine also, then again “No license for product (-1)” will be displayed in the
command prompt.
So, if ”No license for product(-1)” is displayed in the command prompt two times, then check
in the NetSim license server to know about the availability of license and adjust the number
of current users of NetSim, in order to get the license.
11.1.5 Unable to load license config dll displayed:
Reason: If the command/iopath provided by the user is first written in MS Word and then
copy pasted to Command prompt, some special characters(not visible in command prompt)
gets inserted and on execution, license config dll is not found.
Solution: Type the command manually or copy paste the command/iopath from notepad.
454
11.2 Configuration.xml
11.2.1 Blue zigzag lines in configuration file attributes:
Specific attributes in the Configuration file are highlighted with zigzag lines
Reason: If invalid input is given in the Configuration file, then the corresponding attribute is
highlighted in zigzag lines as shown in the figure given below.
Solution:
To resolve this issue mouse over the corresponding attribute, in order to get the tool tip that
furnishes the details about the valid input for that attribute.
Note: If the schema file and the configuration file are not present in the same folder, the
zigzag lines won‟t appear. So place the Configuration file and Schema File in the same
location or change the path of schema file in the configuration file.
11.2.2 Red zigzag lines in configuration file attributes:
Simulation does not commence and error is displayed at the command prompt. Also, Zigzag
lines appearing at the tag specifying the Layer in the Configuration file
Reason: This issue arises mainly when the closing tag is not specified correctly for a
particular layer in the Configuration file.
Example: If the closing tag is not specified for the Data link Layer, then the zigzag lines
appear at the starting tags of Data link Layer and the Network Layer.
455
When NetSim is made to run through CLI, then the following error gets displayed in the
command prompt.
Solution: The bug can be fixed by setting the closing tag correctly in the Configuration file
11.2.3 Zigzag lines appearing at configuration.xsd in the

Configuration file:
Zigzag lines appearing at configuration.xsd in the Configuration file
Reason: This issue arises when the schema and the configuration file are not in the same
folder.
456
Solution: The bug can be fixed by placing the Configuration file and schema in the same
folder.
11.2.4 Simulation terminates and “NetSim Backend has stopped

working” displayed:
Simulation terminates and exhibits unpredictable behavior. An error message stating, “An
exe to run NetSim backend has stopped working” is thrown
Example:
This problem arises if there is any flaw in the Configuration.xml or in the dll.
Solution: Check whether the desired scenario has been configured properly in the
Configuration.xml.
457
11.2.5 Monitor screen resolution is less than 1024X768:
While starting NetSim, error shows the monitor screen resolution is less than 1024 X 768.
Reason: This error will come if monitor resolution is less than 1024 and 768. For example,
1260 X 720 will also show this error
Solution: Change your monitor resolution to 1024 X 768 or above.
11.3 Licensing
11.3.1 No License for product (-1) error
NetSim dongle is running in the server system. When running the NetSim in the Client
system showing “No License for product (-1)” error.
Possible Reasons
1. Firewall in the client system is blocking the Network traffic.

2. No network connection between Client and Server.
3. License Server is not running in the Server system.
Solution
1. The installed firewall may block traffic at 5053 port used for licensing. So either the
user can stop the firewall, or may configure it to allow port 5053.
2. Contact the Network-in-charge and check if the Server system can be pinged from
client.
3. Check whether License Server is running in the Server system or not.
458
12 Known Issues in NetSim v9
12.1 User modified parameters in device properties will not
reflect in newly dropped devices
After dropping nodes on the environment, modification of protocols/ global properties (like
Physical Layer parameters, Data Link Layer parameters and others) in one node will reflect
in all other nodes. But after modification, if any new node is dropped, the modifications will
not be reflected in the newly dropped nodes
Solution: After dropping new nodes, open the properties of any old wireless node and click
accept.
12.2 Dynamic metrics not updated on modifying scenario

After designing a network scenario and enabling the Dynamic Metrics, if the user
modifies the scenario by adding new Links or Application and simulate, these new Link and
Application properties will not be plotted.
Solution: After making modification and just before simulating the scenario, Click on
Dynamic Metrics and click OK.
After opening a network scenario where Dynamic Metrics is enabled, if the user
modifies the scenario by adding new Links or Application and simulate, these new Link and
Application properties will not be plotted.
Solution: After making modification and just before simulating the scenario, Click on
Dynamic Metrics and click OK.
12.3 Packet animation in map view does not show node

mobility
In NetSim, if a network scenario is created in Map View and mobility is enabled in Nodes,
then packet animation will not display any node movement due to mobility, even in high
zoom.
459
12.4 Device properties does not revert to default values
User modifies the default values in a parameter, which is exclusive to a specific
protocol/codec, and then changes the protocol/codec using the provided combo box. If the
user reverts the combo box value again to the old protocol/codec, then the modified
parameter values will be shown instead of the default ones.
12.5 Incumbent ID in network and metrics not matching

Users may face issue when checking Incumbent Metrics in Cognitive Radio network after
simulation as the Incumbent ID may not match the one displayed during network scenario
creation.
12.6 BGP link speed issues

In a BGP Scenario, if OSPF protocol is running and the link speed between Internal and BGP
routers is 100,000 mbps and the rest are set to default, then application throughput obtained is
zero.
12.7 Dynamic Metrics limit is 500 graphs

If Dynamic Metrics is enabled for a network scenario containing more than 500 links or
application, then all the graphs may not be displayed in the Performance Metrics Window.
Reason: This is because windows has a limit of 512 on the max number of files that can be
open simultaneously
12.8 Running Application between unconnected nodes

Users can create multiple isolated networks in NetSim. But if an application is set having
source as a node of an isolated network and destination as a node of another isolated network,
NetSim may crash or display zero application throughput.
460
12.9 RIP Hop count
As per RIP routing protocol, the maximum number of hops/routers it can work from one end
to another is 16. But in NetSim, RIP protocol can work across more than 16 routers.
12.10 Default gateway can’t be empty

When user manually provides a value in a blank “Default Gateway” parameter in any device,
then it cannot be made blank again, which in turn may lead NetSim to crash.
Solution: Users should not enter any value in a blank “default gateway” field in UI.
12.11 Packet size limit in TDMA(Military Radio)

High packet sizes will lead to zero throughputs.
where SLOT_DURATION is in millisecond and DATA_RATE = 25kbps
12.12 Removing link between switches leads to IP addressing

issue.
User connects 3 or more switches serially with a router on one side and wired node on the
other side. Due to this, the node is assigned default gateway value. But on removing an
intermediate link, the default gateway value still remains in the node properties, which may
lead to crashing of the network scenario.
12.13 Packet animation simulation time bar is not

functioning properly in WSN, IOT
During Packet animation of Wireless Sensor Network and Internet of Things, the simulation
time bar, when dragged to a longer time duration, automatically returns back to a lower value.
461
13 NetSim Videos
In order to have a better understanding of NetSim, users can access YouTube channel of
Tetcos at www.youtube.com/tetcos and check out the various videos available
462

User Manual

Uploaded by

Copyright:

Available Formats

User Manual

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

User Manual

Uploaded by

Copyright:

Available Formats

NetSim User Manual

1 NetSim – Introduction ......................................................................... 11

2 Getting Started in NetSim ................................................................... 16

3 Simulating different networks in NetSim ............................................ 41

4 Traffic generator in NetSim (Application Models) ............................. 106

5 Running simulation via CLI ................................................................ 121

6 Analysis ............................................................................................ 130

7 Custom code in NetSim ..................................................................... 159

8 Advanced Features ........................................................................... 192

9 Programming Exercises ..................................................................... 221

10 NetSim Emulator ............................................................................... 428

11 Troubleshooting in NetSim................................................................ 451

12 Known Issues in NetSim v9 ............................................................... 459

13 NetSim Videos .................................................................................. 462

1.1 Introduction to modeling and simulation of networks

Some examples of applications of network simulators are

 Protocol performance analysis

The key features essential to any network simulation are -

Features Academic Standard Pro

Component No Networks / Protocols International Standards

Advanced Wireless Networks IETF RFC 4728, 3561, 3626

Cellular Networks 3GPP, ETSI, IMT-MC, IS-95

Cognitive Radio Networks

Long Term Evolution

Military Radio (Only in PRO

Network Network Emulator – Connect real

Click on Yes button to install the software.

Setup prepares the installation wizard and

Click on the Next button

In the next screen, License agreement will

Click on the Next button.

Note: Select all the supporting applications

In the next screen, you will be requested to

Select the path in which the software needs

Note: In the case of 64 bit machine, ensure

In the next screen, you will be requested to

The installation process begins.

After the installation of required files, the

The below screen will appear to choose the

After selecting English language, next screen is

Click on the Next button to install gnuplot

In the next screen, you will be requested to enter

Set the Start Menu Folder name.

Select Next when the additional tasks

After completion of the installation of the

Click on the Finish button to complete the

Select all the components and click on Next.

Click on Next to go to Install Location window

Select Install WinPcap and click on Install.

After the installation of the software, you will

To start Python software installation,

Select the Python directory and

Click on Finish. This completes the installation

Select “Run NetSim” and then click on the

This completes the installation of NetSim

 Insert the CD-ROM disc in the CD drive.

Click on the Next button

Note: Any other program running during the