[ns] DYMO Protocol,
I m trying to simulate DYMO protocol in ns-2.34 can anyone help me by sending the DYMO routing protocol simulation program and its trace files. Very urgent pls.
Re: [ns] Ns-users Digest, Vol 87, Issue 8
How do you create the text file? If you create it with w option, you'll get only one record (actually, the last one), because you overwrite the existing one. You must open it with a option, this way you append the record to the file every time. Hope it helps! Leo Sánchez. El 09/03/2011 3:05, ranjana pathak escribió: Dear frds, I m adding one function in aodv, and it is called whenever a link get down and writing the output of this function to a text file. but in this text file only one record is written, Is this possible that in case of aodv, rt_down function called only once. Regards, Ranjana
[ns] Implementation of VBR MPEG-1 traffic source in ns
hello thiis is khan. I have done the simulation according to your steps from the the site http://www.isi.edu/nsnam/archive/ns-users/webarch/2001/msg05051.html but i was unable to configure that completely it showing like as follows config.status: creating indep-utils/webtrace-conv/ucb/ Makefile config.status: creating indep-utils/webtrace-conv/dec/Makefile config.status: creating indep-utils/webtrace-conv/nlanr/Makefile config.status: creating indep-utils/webtrace-conv/epa/Makefile config.status: creating indep-utils/cmu-scen-gen/setdest/Makefile config.status: creating autoconf.h config.status: autoconf.h is unchanged sadaq@ubuntu:~/ns-allinone-2.34/ns-2.34$ sudo make make: *** No rule to make target `tools/VBR_traffic.o', needed by `ns'. Stop. sadaq@ubuntu:~/ns-allinone-2.34/ns-2.34$ could you please help me how to sort out this problem
[ns] Problems in installation of tools/Analysers
While making Analysers from tools/analyser( http://www.michele-mastrogiovanni.net/software/download/tools.tar.gz) directory ,Error prompted: src/gzstream.h:35:18: error: zlib.h: No such file or directory In file included from src/analyzer_degree.h:9, from src/analyzer_degree.cpp:1: src/gzstream.h:50: error: ‘gzFile’ does not name a type Has anybody come across the same problem,if yes then please help.Thank you. -- Thanks Regards Nikhil Agarwal Senior Undergraduate Computer Science Engineering, National Institute Of Technology, Durgapur,India http://tech-nikk.blogspot.com http://beta.freshersworld.com/communities/nitd
[ns] Metric troubles
I am sure that this has been answered before, but I, for the life of me,
couldn't find what I think I need. I have been trying to figure this
out for a day or two now.
I am trying to create graphs for RTT and throughput. I have seen links
mentioned to a university website (
//http://www-mash.cs.berkeley.edu/dist/archive/ns-users/0002/0030.html)//
, but those pages aren't there anymore. I have found numerous
Throughput calculations, but they all seem to be about overall
throughput. (We are modeling random traffic, so are more interested in
a more instantaneous throughput. Not EXACTLY instantaneous, but over a
smaller window than the entire simulation.)
For RTT, I am kind of stuck. Yes, I have traced 'cwnd_' and 'rtt_' and
looked at the file. (Curiously, my RTT trace file (different from my
cwnd_ trace file) only has one line in it.)
Here is a clip (1st 10 lines) from the file, plus some headers that I am
guessing at:
TimeTypeValue
0.0 -1 -1 -1 -1 cwnd_ 1.000
1.29029 5 0 1 3 rtt_ 0.050
1.29029 5 0 1 3 cwnd_ 2.000
1.35309 5 0 1 3 rtt_ 0.070
1.35309 5 0 1 3 cwnd_ 3.000
1.35986 5 0 1 3 cwnd_ 4.000
1.40282 5 0 1 3 rtt_ 0.050
1.40282 5 0 1 3 cwnd_ 5.000
1.40959 5 0 1 3 cwnd_ 6.000
1.41635 5 0 1 3 cwnd_ 7.000
Here's the corresponding overall out.tr (1st 30 or so lines):
+ 0.004717 2 0 tcp 40 --- 1 2.0 1.0 0 0
- 0.004717 2 0 tcp 40 --- 1 2.0 1.0 0 0
r 0.005749 2 0 tcp 40 --- 1 2.0 1.0 0 0
+ 0.005749 0 1 tcp 40 --- 1 2.0 1.0 0 0
- 0.005749 0 1 tcp 40 --- 1 2.0 1.0 0 0
r 0.026206 0 1 tcp 40 --- 1 2.0 1.0 0 0
+ 0.026206 1 0 ack 40 --- 1 1.0 2.0 0 1
- 0.026206 1 0 ack 40 --- 1 1.0 2.0 0 1
r 0.046663 1 0 ack 40 --- 1 1.0 2.0 0 1
+ 0.046663 0 2 ack 40 --- 1 1.0 2.0 0 1
- 0.046663 0 2 ack 40 --- 1 1.0 2.0 0 1
r 0.047695 0 2 ack 40 --- 1 1.0 2.0 0 1
+ 0.047695 2 0 tcp 592 --- 1 2.0 1.0 1 2
- 0.047695 2 0 tcp 592 --- 1 2.0 1.0 1 2
+ 0.047695 2 0 tcp 592 --- 1 2.0 1.0 2 3
- 0.048169 2 0 tcp 592 --- 1 2.0 1.0 2 3
r 0.049169 2 0 tcp 592 --- 1 2.0 1.0 1 2
+ 0.049169 0 1 tcp 592 --- 1 2.0 1.0 1 2
- 0.049169 0 1 tcp 592 --- 1 2.0 1.0 1 2
r 0.049643 2 0 tcp 592 --- 1 2.0 1.0 2 3
+ 0.049643 0 1 tcp 592 --- 1 2.0 1.0 2 3
- 0.055935 0 1 tcp 592 --- 1 2.0 1.0 2 3
r 0.075935 0 1 tcp 592 --- 1 2.0 1.0 1 2
+ 0.075935 1 0 ack 40 --- 1 1.0 2.0 1 4
- 0.075935 1 0 ack 40 --- 1 1.0 2.0 1 4
r 0.0827 0 1 tcp 592 --- 1 2.0 1.0 2 3
+ 0.0827 1 0 ack 40 --- 1 1.0 2.0 2 5
In the cwnd_ trace file, type = CWND isn't too hard figure out: that is
the size of the window at that time. But what is RTT and how is it
calculated? Is it simply for that one packet? Does it actually
calculate the return ACK to the sender as part of the RTT (which is what
we would like, I suppose)?
And why the drastic difference in the time fields? What units is the
'cwnd_' time field in? It doesn't seem to match up too closely with the
packets from the full trace file.
Here's a clip from my TCL file. (This script uses FOR loops to assign
multiple/variable numbers of sources.)
#TCP sources
for {set j 1} {$j=$NumbSrc} {incr j} {
set tcp_src($j) [new Agent/TCP/Reno];
$tcp_src($j) set window_ 8000;
# tracing TCP rtt variables
set rtt_trace [open rtt_trace.out w];# trace file
$tcp_src($j) attach $rtt_trace;# attach to TCP Agent
$tcp_src($j) tracevar rtt_;# trace rtt
#END Justin's RTT tracing
# tracing TCP congestion window variables
set cwnd_trace [open cwnd_trace.out w];# trace file
$tcp_src($j) attach $cwnd_trace;# attach to TCP Agent
$tcp_src($j) tracevar cwnd_;# trace rtt
#END Justin's cong. window tracing
}
Any advice would be appreciated.
-- Justin
Re: [ns] signal strength
hey, i wanna know how to get the signal strength in ns2 and if there is a possibility to use this information to make a routing protocol in ns2 working better??!! please if any one has ever try a succeful attempt concerning this experience ,if he can post all the possible details . thanks
[ns] Some oddities
Hello all again,
In looking further at my cwnd_ trace file, I noticed that some of
the congestion window values are not integers. They start out as
integers and then somehow become non-integers. Also, there are spots in
the file that have erroneous lines; there will parts of two lines
together on one line, there will be lines with only 3 items in them,
etc. Anyone else seen that before and know what is going on?
(Yes, as you can tell, fairly new at this and shooting in the dark here
somewhat.)
Here is a snippet of the TCL again:
#TCP sources
for {set j 1} {$j=$NumbSrc} {incr j} {
set tcp_src($j) [new Agent/TCP/Reno];
$tcp_src($j) set window_ 8000;
#Justin's additions to try and get an RTT trace...
# tracing TCP rtt variables
set rtt_trace [open rtt_trace.out w];# trace file
$tcp_src($j) attach $rtt_trace;# attach to TCP Agent
$tcp_src($j) tracevar rtt_;# trace rtt
# tracing TCP congestion window variables
set cwnd_trace [open cwnd_trace.out w];# trace file
$tcp_src($j) attach $cwnd_trace;# attach to TCP Agent
$tcp_src($j) tracevar cwnd_;# trace cwnd
(which also tracks RTT?)
=
And the output file I get:
1.45695 5 0 1 3 cwnd_ 9.000
1.46371 5 0 1 3 cwnd_ 10.000
1.48401 5 0 1 3 cwnd_ 5.000
1.54051 5 0 1 3 cwnd_ 5.200
1.74051 5 0 1 3 cwnd_ 1.000
1.79023 5 0 1 3 cwnd_ 2.000
1.83996 5 0 1 3 cwnd_ 2.500
1.88969 5 0 1 3 cwnd_ 2.900
1.93942 5 0 1 3 cwnd_ 3.245
1.94619 5 0 1 3 cwnd_ 3.553
1.95295 5 0 1 3 cwnd_ 3.834
==
And some odd lines:
5.08033 5 0 1 3 cwnd_ 4.723
5.08710 5 0 1 3 cwnd_ 4.935
1
4.89089 3 0 1 1 cwnd_ 5.789
4.89766 3 0 1 1 cwnd_ 5.962
OR
13.13830 3 0 1 1 cwnd_ 5.463
13.14506 3 0 1 1 cwnd_ 5.646
13.15859 3 0 1 1 cwnd_ 5.8 1 0 cwnd_ 5.012
11.35215 2 0 1 0 cwnd_ 5.212
11.45363 2 0 1 0 cwnd_ 5.404
OR
16.47379 2 0 1 0 cwnd_ 7.442
16.48056 2 0 1 0 cwnd_ 7.576
16.57528 2 5.126
15.89871 3 0 1 1 rtt_ 0.110
15.89871 3 0 1 1 cwnd_ 5.321
==
Thanks,
J
[ns] FW: Interference-aware Multipath Routing protocol
Hello, I need to use a multipath routing protocol that consider interference intra-path and inter-path in wireless mesh networks. Do you know where I can have any implementation available to NS-2? Thanks in advance, Elisabete Reis
[ns] help to find completed connection per sec
Hi
I am new to ns2. Does anyone know how do I plot a graph to find number of
completed connection per sec?
I have attached snippets of my codes over here, can I know whether I am on the
correct track?
Thanks in advance.
#Setup a TCP connection
for {set i 0} {$i 5} {incr i} {
set tcp1 [new Agent/TCP]
$ns attach-agent $n0 $tcp1
set sink1 [new Agent/TCPSink/DelAck]
$ns attach-agent $n1 $sink1
$ns connect $tcp1 $sink1
$tcp1 set fid_ 1
$tcp1 set window_ 8000
$tcp1 set packetSize_ 200
$tcp1 set class_ $i
#Setup a FTP over TCP connection
set ftp1 [new Application/FTP]
$ftp1 attach-agent $tcp1
$ftp1 set type_ FTP
}
proc record {} {
global sink1 sink2 sink3 tcpTahoe tcpReno tcp793
#Get an instance of the simulator
set ns [Simulator instance]
#Set the time after which the procedure should be called again
set time 1.0
#How many bytes have been received by the traffic sinks?
set bw0 [expr [$sink1 set bytes_]+1]
set bw1 [expr [$sink2 set bytes_]+1]
set bw2 [expr [$sink3 set bytes_]+1]
#Get the current time
set now [$ns now]
#Calculate the bandwidth (in MBit/s) and write it to the files
#puts $tcpTahoe $now [expr $bw0/$time*8/10]
#puts $tcpReno $now [expr $bw1/$time*8/10]
#puts $tcp793 $now [expr $bw2/$time*8/10]
puts $tcpTahoe $now $bw0
puts $tcpReno $now $bw1
puts $tcp793 $now $bw2
#Reset the bytes_ values on the traffic sinks
$sink1 set bytes_ 0
$sink2 set bytes_ 0
$sink3 set bytes_ 0
#Re-schedule the procedure
$ns at [expr $now+$time] record
}
$ns at 0.0 record
$ns at 0.0 $ftp1 start
$ns at 30.0 $ftp2 stop
$ns at 30.0 finish
$ns run
[ns] SPAN protoccol
Hi all, Anyone aware of SPAN protocol in ns2? I am using this with ns2.28... After run my tcl script, cbr packets are not received. Can anyone please help me? -- Regards, Subha
