IoT: Technology and Applications Reg.

no: 19MCS0055

CSE6009 – IoT: Technology and Applications LAB

ASSESSMENT – 3

INDIVIDUAL

REGISTER NUMBER NAME

19MCS0055 M. Akram Sharieff
IoT: Technology and Applications Reg.no: 19MCS0055

Program1: Simple simulator program:

The below code creates 4 nodes (n0, n1, n2, n3). The duplex links between n0 and n2, and
n1 and n2 have 2 Mbps of bandwidth and 10 ms of delay. The duplex link between n2 and n3 has
1.7 Mbps of bandwidth and 20 ms of delay. Each node uses a DropTail queue, of which the maxi-
mum size is 10. A "tcp" agent is attached to n0, and a connection is established to a tcp "sink" agent
attached to n3. As default, the maximum size of a packet that a "tcp" agent can generate is 1KByte.
A tcp "sink" agent generates and sends ACK packets to the sender (tcp agent) and frees the received
packets. A "udp" agent that is attached to n1 is connected to a "null" agent attached to n3. The "cbr"
is set to start at 0.1 sec and stop at 4.5 sec, and "ftp" is set to start at 1.0 sec and stop at 4.0 sec.

Source Code:

#Create a simulator object

set ns [new Simulator]

#Define different colors for data flows (for NAM)

$ns color 1 Blue
$ns color 2 Red

#Open the NAM trace file

set nf [open out.nam w]
$ns namtrace-all $nf

#Define a 'finish' procedure

proc finish {} {
global ns nf
$ns flush-trace
#Close the NAM trace file
close $nf
#Execute NAM on the trace file
exec nam out.nam &
exit 0
}

#Create four nodes

set n0 [$ns node]
set n1 [$ns node]
set n2 [$ns node]
set n3 [$ns node]

#Create links between the nodes

$ns duplex-link $n0 $n2 2Mb 10ms DropTail
$ns duplex-link $n1 $n2 2Mb 10ms DropTail
$ns duplex-link $n2 $n3 1.7Mb 20ms DropTail

#Set Queue Size of link (n2-n3) to 10

$ns queue-limit $n2 $n3 10

#Give node position (for NAM)

$ns duplex-link-op $n0 $n2 orient right-down
$ns duplex-link-op $n1 $n2 orient right-up
$ns duplex-link-op $n2 $n3 orient right

#Monitor the queue for link (n2-n3). (for NAM)

$ns duplex-link-op $n2 $n3 queuePos 0.5
IoT: Technology and Applications Reg.no: 19MCS0055

#Setup a TCP connection

set tcp [new Agent/TCP]
$tcp set class_ 2
$ns attach-agent $n0 $tcp
set sink [new Agent/TCPSink]
$ns attach-agent $n3 $sink
$ns connect $tcp $sink
$tcp set fid_ 1

#Setup a FTP over TCP connection

set ftp [new Application/FTP]
$ftp attach-agent $tcp
$ftp set type_ FTP

#Setup a UDP connection

set udp [new Agent/UDP]
$ns attach-agent $n1 $udp
set null [new Agent/Null]
$ns attach-agent $n3 $null
$ns connect $udp $null
$udp set fid_ 2

#Setup a CBR over UDP connection

set cbr [new Application/Traffic/CBR]
$cbr attach-agent $udp
$cbr set type_ CBR
$cbr set packet_size_ 1000
$cbr set rate_ 1mb
$cbr set random_ false

#Schedule events for the CBR and FTP agents

$ns at 0.1 "$cbr start"
$ns at 1.0 "$ftp start"
$ns at 4.0 "$ftp stop"
$ns at 4.5 "$cbr stop"

#Detach tcp and sink agents (not really necessary)

$ns at 4.5 "$ns detach-agent $n0 $tcp ; $ns detach-agent $n3 $sink"

#Call the finish procedure after 5 seconds of simulation time

$ns at 5.0 "finish"

#Print CBR packet size and interval

puts "CBR packet size = [$cbr set packet_size_]"
puts "CBR interval = [$cbr set interval_]"
IoT: Technology and Applications Reg.no: 19MCS0055

Output:
IoT: Technology and Applications Reg.no: 19MCS0055

Program 2: VEHICULAR ADHOC NETWORKS

Vehicular Ad hoc Network (VANET) are treated as mobile sensor networks and
characterized with special characteristics such as high node mobility and rapid topology changes.
VANET nodes can sense a variety of data in its surrounding area to offer several services including
traffic monitoring, speed controlling, lost vehicle locating and environmental monitoring as it
covers permanently a wide geographical region. Nodes are configured with different
communication. Vehicles moves within the specified network boundary. Nodes in VANET can
communicate in two ways: vehicle-to-vehicle (V2V) communication and Vehicle-to-infrastructure
(V2I) communication. In V2I communication model, vehicles communicate to Road-Side-Unit
(RSU) through Road-Side-Routers.

Source Code:
# Define options
set val(chan) Channel/WirelessChannel ;# channel type
set val(prop) Propagation/TwoRayGround ;# radio-propagation model
set val(netif1) Phy/WirelessPhy ;# network interface type
set val(netif2) Phy/WirelessPhy ;# network interface type
set val(mac) Mac/802_11 ;# MAC type
set val(ifq) Queue/DropTail/PriQueue ;# interface queue type
set val(ll) LL ;# link layer type
set val(ant) Antenna/OmniAntenna ;# antenna model
set val(ifqlen) 50 ;# max packet in ifq
set val(nn) 46 ;# number of mobilenodes
set val(rp) AODV ;# routing protocol
set val(x) 200 ;# X dimension of topography
set val(y) 200 ;# Y dimension of topography
set val(stop) 10.0 ;# time of simulation end
# Simulator Instance Creation
set ns [new Simulator]
# set up topography object
set topo [new Topography]
$topo load_flatgrid $val(x) $val(y)
# general operational descriptor- storing the hop details in the
network
create-god $val(nn)
# For model 'TwoRayGround'
set dist(20m) 4.80696e-07
set dist(26m) 2.84435e-07
set dist(27m) 2.63756e-07
set dist(28m) 2.45253e-07
set dist(25m) 3.07645e-07
set dist(30m) 2.13643e-07
set dist(35m) 1.56962e-07
set dist(50m) 7.69113e-08
set dist(75m) 3.41828e-08
set dist(60m) 5.34106e-08
set dist(70m) 3.92405e-08
IoT: Technology and Applications Reg.no: 19MCS0055

# unity gain, omni-directional antennas

# set up the antennas to be centered in the node and 1.5 meters
above it
Antenna/OmniAntenna set X_ 0
Antenna/OmniAntenna set Y_ 0
Antenna/OmniAntenna set Z_ 1.5
Antenna/OmniAntenna set Gt_ 1.0
Antenna/OmniAntenna set Gr_ 1.0
# Initialize the SharedMedia interface with parameters to make
# it work like the 914MHz Lucent WaveLAN DSSS radio interface
$val(netif1) set CPThresh_ 10.0
$val(netif1) set CSThresh_ $dist(70m)
$val(netif1) set RXThresh_ $dist(75m)
$val(netif1) set Rb_ 2*1e6
$val(netif1) set Pt_ 0.2818
$val(netif1) set freq_ 914e+6
$val(netif1) set L_ 1.0
$val(netif2) set CPThresh_ 10.0
$val(netif2) set CSThresh_ $dist(75m)
$val(netif2) set RXThresh_ $dist(75m)
$val(netif2) set Rb_ 2*1e6
$val(netif2) set Pt_ 0.2818
$val(netif2) set freq_ 914e+6
$val(netif2) set L_ 1.0
# set up topography object
set topo [new Topography]
$topo load_flatgrid $val(x) $val(y)
# Create God
set god_ [create-god $val(nn)]
set chan_1_ [new $val(chan)]
# configure node
$ns node-config -adhocRouting $val(rp) \
-llType $val(ll) \
-macType $val(mac) \
-ifqType $val(ifq) \
-ifqLen $val(ifqlen) \
-antType $val(ant) \
-propType $val(prop) \
-phyType $val(netif1) \
-topoInstance $topo \
-agentTrace ON \
-routerTrace ON \
-macTrace OFF \
-movementTrace ON \
-channel $chan_1_ \
IoT: Technology and Applications Reg.no: 19MCS0055

for {set i 0} {$i < 1 } {incr i} {

set node_($i) [$ns node]
$node_($i) color black
$node_($i) random-motion 0 ;# disable random motion
}
$ns node-config -adhocRouting $val(rp) \
-llType $val(ll) \
-macType $val(mac) \
-ifqType $val(ifq) \
-ifqLen $val(ifqlen) \
-antType $val(ant) \
-propType $val(prop) \
-phyType $val(netif2) \
-topoInstance $topo \
-agentTrace ON \
-routerTrace ON \
-macTrace OFF \
-movementTrace ON \
-channel $chan_1_ \
for {set i 1} {$i < 4 } {incr i} {
set node_($i) [$ns node]
$node_($i) color black
}

Output:
IoT: Technology and Applications Reg.no: 19MCS0055

Program 3:

TCL script to display packets transfer information using annotation

Description:
This network consists of 8 nodes (Client1, Client2, Client3, Router1, Router2, Router3, Router4, and
Endserver1). The duplex links between Client1, Client2, Client3 and Router1 have 5 Mbps of bandwidth and
50 ms of delay. The duplex link between Router1 and Router2 has 5Mbps of bandwidth and 50 ms of delay.
The duplex link between Router2 and Router3 has 150Kbps of bandwidth and 50 ms of delay. The duplex link
between Router3 and Router4, Router4 and Router5, Router5 and Router6, Router6 and Endserver1 has
300Kbps of bandwidth and 50 ms of delay. Each link uses a DropTail queue. A "TCP" agent is attached to
Client1, Client2, Client3, Client4 and a connection is established to a “TCPSink" agent attached to
Endserver1. As default, the maximum size of a packet that a "TCP" agent can generate is 1000bytes. A
“TCPSink” agent generates and sends ACK packets to the sender (tcp agent) and frees the received packets.
Link failure and recovery model is created at various times. Here we will generate the trace-annotate file. It
will provide the information about the packet transfer event at the bottom of the simulation window. The ftp
starts at .50 sec and ends at 28.5sec

Source Program:

set ns [ new Simulator]

# ----------- CREATING NAM OBJECTS ------------#

set nf [open trace2.nam w]

$ns namtrace-all $nf

#Open the trace file

set nt [open trace2.tr w]
$ns trace-all $nt

set proto rlm

$ns color 1 red

$ns color 2 blue
$ns color 3 yellow
$ns color 4 cyan
$ns color 5 maroon

# --------- CREATING CLIENT - ROUTER -ENDSERVER

NODES-----------#

set Client1 [$ns node]

set Client2 [$ns node]
set Client3 [$ns node]
set Client4 [$ns node]
set Router1 [$ns node]
set Router2 [$ns node]
set Router3 [$ns node]
set Router4 [$ns node]
set Router5 [$ns node]
set Router6 [$ns node]
IoT: Technology and Applications Reg.no: 19MCS0055

set Endserver1 [$ns node]

#set Endserver2 [$ns node]

# --------------CREATING DUPLEX LINK -----------------------#

$ns duplex-link $Client1 $Router1 5Mb 50ms DropTail

$ns duplex-link $Client2 $Router1 5Mb 50ms DropTail
$ns duplex-link $Client3 $Router1 5Mb 50ms DropTail
$ns duplex-link $Client4 $Router1 5Mb 50ms DropTail
$ns duplex-link $Router1 $Router2 5Mb 50ms DropTail
$ns duplex-link $Router2 $Router3 150Kb 50ms DropTail
$ns duplex-link $Router3 $Router4 300Kb 50ms DropTail
$ns duplex-link $Router4 $Router5 100Kb 50ms DropTail
$ns duplex-link $Router5 $Router6 300Kb 50ms DropTail
$ns duplex-link $Router6 $Endserver1 300Kb 50ms DropTail
#$ns duplex-link $Router6 $Endserver2 300Kb 50ms DropTail

#-----------CREATING ORIENTATION -------------------------#

$ns duplex-link-op $Client1 $Router1 orient down-right

$ns duplex-link-op $Client2 $Router1 orient right
$ns duplex-link-op $Client3 $Router1 orient up-right
$ns duplex-link-op $Client4 $Router1 orient up
$ns duplex-link-op $Router1 $Router2 orient right
$ns duplex-link-op $Router2 $Router3 orient down
$ns duplex-link-op $Router3 $Router4 orient right
$ns duplex-link-op $Router4 $Router5 orient up
$ns duplex-link-op $Router5 $Router6 orient right
$ns duplex-link-op $Router6 $Endserver1 orient up-right
#$ns duplex-link-op $Router6 $Endserver2 orient right

# --------------LABELLING -----------------------------#

$ns at 0.0 "$Client1 label Client1"

$ns at 0.0 "$Client2 label Client2"
$ns at 0.0 "$Client3 label Client3"
$ns at 0.0 "$Client4 label Client4"
$ns at 0.0 "$Router1 label Router1"
$ns at 0.0 "$Router2 label Router2"
$ns at 0.0 "$Router3 label Router3"
$ns at 0.0 "$Router4 label Router4"
$ns at 0.0 "$Router5 label Router5"
$ns at 0.0 "$Router6 label Router6"
$ns at 0.0 "$Endserver1 label Endserver"
#$ns at 0.0 "$Endserver2 label Endserver2"

# --------------- CONFIGURING NODES -----------------#

$Endserver1 shape hexagon

$Router1 shape box
$Router2 shape square
$Router3 shape square
$Router4 shape square
IoT: Technology and Applications Reg.no: 19MCS0055

$Router5 shape square

$Router6 shape square

# ----------------ESTABLISHING QUEUES -------------#

$ns duplex-link-op $Client1 $Router1 queuePos 0.1

$ns duplex-link-op $Client2 $Router1 queuePos 0.1
$ns duplex-link-op $Client3 $Router1 queuePos 0.5
$ns duplex-link-op $Client4 $Router1 queuePos 0.5
$ns duplex-link-op $Router1 $Router2 queuePos 0.1
$ns duplex-link-op $Router2 $Router3 queuePos 0.1
$ns duplex-link-op $Router3 $Router4 queuePos 0.1
$ns duplex-link-op $Router4 $Router5 queuePos 0.1
$ns duplex-link-op $Router5 $Router6 queuePos 0.5
$ns duplex-link-op $Router6 $Endserver1 queuePos 0.5

# ----------------ESTABLISHING COMMUNICATION -------------#

#--------CLIENT1 TO ENDSERVER -------------#

set tcp0 [new Agent/TCP]

$tcp0 set maxcwnd_ 16
$tcp0 set fid_ 4
$ns attach-agent $Client1 $tcp0

set sink0 [new Agent/TCPSink]

$ns attach-agent $Endserver1 $sink0

$ns connect $tcp0 $sink0

set ftp0 [new Application/FTP]

$ftp0 attach-agent $tcp0

$ns add-agent-trace $tcp0 tcp

$tcp0 tracevar cwnd_

$ns at 0.5 "$ftp0 start"

$ns at 28.5 "$ftp0 stop"

# ----------------CLIENT2 TO ENDSERVER1 -------------#

set tcp1 [new Agent/TCP]

$tcp1 set fid_ 2
$tcp1 set maxcwnd_ 16
$ns attach-agent $Client2 $tcp1

set sink1 [new Agent/TCPSink]

$ns attach-agent $Endserver1 $sink1

$ns connect $tcp1 $sink1

set ftp1 [new Application/FTP]

$ftp1 attach-agent $tcp1

$ns add-agent-trace $tcp1 tcp1

IoT: Technology and Applications Reg.no: 19MCS0055

$tcp1 tracevar cwnd_

$ns at 0.58 "$ftp1 start"

$ns at 28.5 "$ftp1 stop"

# ---------------- CLIENT3 TO ENDSERVER -------------#

set tcp2 [new Agent/TCP]

$tcp2 set fid_ 0
$tcp2 set maxcwnd_ 16
$tcp2 set packetsize_ 100
$ns attach-agent $Client3 $tcp2
set sink2 [new Agent/TCPSink]
$ns attach-agent $Endserver1 $sink2
$ns connect $tcp2 $sink2

set ftp2 [new Application/FTP]

$ftp2 attach-agent $tcp2
$ns add-agent-trace $tcp2 tcp2
$tcp2 tracevar cwnd_

$ns at 0.65 "$ftp2 start"

$ns at 28.5 "$ftp2 stop"

#--------------------CLIENT4 TO ENDSERVER----------------#

set tcp3 [new Agent/TCP]

$tcp3 set fid_ 3
$tcp3 set maxcwnd_ 16
$tcp2 set packetsize_ 100
$ns attach-agent $Client4 $tcp3

set sink3 [new Agent/TCPSink]

$ns attach-agent $Endserver1 $sink3

$ns connect $tcp3 $sink3

set ftp3 [new Application/FTP]

$ftp3 attach-agent $tcp3

$ns add-agent-trace $tcp3 tcp3

$tcp3 tracevar cwnd_

$ns at 0.60 "$ftp3 start"

$ns at 28.5 "$ftp3 stop"

$ns rtmodel-at 2.880511 down $Router3 $Router4

$ns rtmodel-at 2.880511 up $Router3 $Router4

$ns rtmodel-at 7.299242 down $Router5 $Router6

$ns rtmodel-at 7.299242 up $Router5 $Router6

#-------------Trace file creation---------#

IoT: Technology and Applications Reg.no: 19MCS0055

$ns at 1.1025 "$ns trace-annotate \"Time: 1.1025 Pkt Transfer Path

thru node_(1)..\""
$ns at 2.1025 "$ns trace-annotate \"Time: 2.1025 Pkt Transfer Path
thru node_(1)..\""
$ns at 2.880511 "$ns trace-annotate \"Time: 2.880511 node_(3) drop
and block pkt transfer..\""
$ns at 7.299242 "$ns trace-annotate \"Time: 7.299242 node_(3) drop
and block pkt transfer..\""

# ---------------- FINISH PROCEDURE -------------#

proc finish {} {

global ns nf nt

$ns flush-trace
close $nf
puts "running nam..."
exec nam trace2.nam &
exit 0
}

#Calling finish procedure

$ns at 15.0 "finish"
$ns run

Output:
IoT: Technology and Applications Reg.no: 19MCS0055