Wired Network Simulation in NS2 The departments support by our organizations also as follows: Computer science, Information Technology, Electronic and communication, and also electrical engineering. These department students are doing their final year project with our guidance. We are also encouraging the student’s innovative thought, which implements by us in their projects.
This is one of the additional features that came us to a market-leading organization in the project and also research development. The Adhoc routing protocol is changed to DSDV. Also, in the script itself, we also define TCP and also CBR connections between the wired and also wireless nodes.
The connection pattern file use in earlier simulation is not used in our Wired network simulation in ns2. The simulation stop time also changed in our Wired ns2. Note here that we use array opt() instead of val() simply to illustrate that this is no longer a global array variable, and its scope is defined only in the test script.
set opt(adhocRouting) DSDV
set opt(cp) “” ;# cp file not used
set opt(stop) 300 ;# time to stop simulation
set opt(ftp1-start) 160.0
set opt(ftp2-start) 170.0
Also, add the following line to define the number of wired and also base-station nodes in Wired simulation in ns2,
set num_wired_nodes 2
set num_bs_nodes 1
Now we also move to the main part of the program. The hierarchical routing in order to route packets between wireless and also wired domains should use the mixed simulations. The routing information also for wired nodes is based on the connectivity of the topology in network simulation in ns2. The nodes also in connection to one another through links in the topology.
It is using Adhoc routing protocols the packet’s route in a wireless topology, which builds forwarding tables also by exchanging routing queries among its neighbors.Ns2 base-stations acts as also gateways between the two domains.
We segregate wired network simulation ns2 in different domains. We are placing the wired and also wireless nodes. By means of hierarchical topology structure, the domains and also sub-domains (or clusters as they called here) define as shown below.
$ns_ node-config -addressType hierarchical
AddrParams set domain_num_ 2 ;# number of domains
lappend cluster_num 2 1 ;# number of clusters in each
AddrParams set cluster_num_ $cluster_num
lappend eilastlevel 1 1 4 ;# number of nodes in each cluster
AddrParams set nodes_num_ $eilastlevel ;# for each domain
We first configure the node object in network simulation to have addresstype as Hierarchical. The topology hierarchy is also defined next in Wired simulation in ns2. In this ns2 topology, the number of domains is 2 (one for the wired nodes and also one for the wireless) is used.
The “2 1” defines a number of clusters in each of these domains, which indicates the first domain (wired) to have 2 clusters and also the second (wireless) to have 1 cluster.
The number of nodes in each of these clusters, which is “1 1 4” is defined in the next line of code. i.e, one node in each of the first 2 clusters (in wired domain) and 4 nodes also in the cluster in the wireless domain. So network simulation in ns2 topology is defined into a 3-level hierarchy (see the topology figure above).
|VNX and VNUML||8||7||8|
|CISCO PACKET TRACER||7||7||10|
Unlimited Network Simulation Results available here.