[ns] NS2 installation problem
-- Forwarded message -- From: haider alhashmiy Date: Wed, Sep 15, 2010 at 2:10 PM Subject: NS2 installation problem To: ns-users@isi.edu Hi all below is the problem that I am facing with the installation of NS2.29: and I need to install this version because its the only version that supports Proxy Mobile IPv6 (PMIPv6) and IEEE 802.21 (MIH). g++ -c -Wall -DUSE_802_21 -DTCP_DELAY_BIND_ALL -DNO_TK -DTCLCL_CLASSINSTVAR -DNDEBUG -DLINUX_TCP_HEADER -DUSE_SHM -DHAVE_LIBTCLCL -DHAVE_TCLCL_H -DHAVE_LIBOTCL1_11 -DHAVE_OTCL_H -DHAVE_LIBTK8_4 -DHAVE_TK_H -DHAVE_LIBTCL8_4 -DHAVE_TCL_H -DHAVE_CONFIG_H -DNS_DIFFUSION -DSMAC_NO_SYNC -DCPP_NAMESPACE=std -DUSE_SINGLE_ADDRESS_SPACE -Drng_test -I. -I/home/haider/Downloads/ns-allinone-2.29/tclcl-1.17 -I/home/haider/Downloads/ns-allinone-2.29/otcl-1.11 -I/home/haider/Downloads/ns-allinone-2.29/include -I/home/haider/Downloads/ns-allinone-2.29/include -I/usr/include/pcap -I./tcp -I./sctp -I./common -I./link -I./queue -I./adc -I./apps -I./mac -I./mobile -I./trace -I./routing -I./tools -I./classifier -I./mcast -I./diffusion3/lib/main -I./diffusion3/lib -I./diffusion3/lib/nr -I./diffusion3/ns -I./diffusion3/filter_core -I./asim/ -I./qs -I./diffserv -I./satellite -I./bluetooth -I./hsntg -I./hsntg/802_21 -I./wimax -I./interference -I./myevalvid -I./wpan -I./pmip6 -o queue/red.o queue/red.cc In file included from ./common/flags.h:45, from queue/red.cc:68: ./common/packet.h: In constructor ‘p_info::p_info()’: ./common/packet.h:215: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:216: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:217: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:218: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:219: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:220: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:221: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:222: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:223: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:224: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:225: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:226: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:227: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:228: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:229: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:230: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:231: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:232: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:233: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:234: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:236: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:237: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:238: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:239: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:240: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:241: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:243: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:244: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:245: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:246: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:247: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:248: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:249: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:250: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:251: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:252: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:253: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:254: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:255: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:256: warning: deprecated conversion from string constant to ‘char*’ ./common/packet.h:258: warning: deprecated conversion from stri
Re: [ns] handover between umts and wimax
Hi, You can go through MIRACLE , a cross platform module for ns2, and it supports multiple phy at nodes (if I am not wrong). Then you can go for Eurane and ns umts extension based on eurane. I hope here you will be able to study the handover between umts and wimax. Please make me know, if will get those things work in your environment. Thanks and Regards, Ashwini www.ashwinipatankar.com | www.wirelesscafe.wordpress.comThanks and Regards, On Wed, Sep 15, 2010 at 5:30 AM, wrote: > [ns] handover between umts and wimax
[ns] Adding 2 Simple Wireless Node
Hi, Thanks for previous replay, but I want now to ask about other thing. I'm work now to test the behavior of cwnd on TCP variants, but I use a standard topology with bottleneck and 3 nodes.My problem is to separates this 3 nodes to , wired, wireless, and wireless with handover scenario. My question, how can I change to node 1 to node with wireless link and node 2 to wireless node with handover. node 0 \ \ \ \ node 1 -- node 3 --- node 4 / / / / node 2 node 1 must change to wireless node link with node 3 and node 2 change to wireless with handover. Regards
[ns] handover between umts and wimax
hello : i have to study the handover between umts and wimax , but i don't new the module that i need to install, also i don't knew how i can configure a mobile node with two interfaces umts and wimax. and i need any document that can help me . and thank you in advance -- - BADDI YOUSSEF Master de Recherche en Génie Informatique ENSIAS, RABAT Tel: +212 672 43 54 15 ---
[ns] Fwd: How to monitor TCP three way handshaking in NS2?
Hi,
I got the answer to both of my questions.Now I want to
prevent the receiver from sending ACK packets to see
if the sender send the packets again or not.
I've added the corrected script to the end of this mail, as
an example for other who might have the same problem.
Thanks,
Mobin
A sample for TCP connection simulation in NS2:
set ns [new Simulator]
# NAM file
set nf [open outtcp1.nam w]
$ns namtrace-all $nf
# finish procedure
proc finish {} {
global ns nf
$ns flush-trace
close $nf
exec nam outtcp1.nam &
exit 0
}
# create nodes
set n0 [$ns node]
set n1 [$ns node]
$ns duplex-link $n0 $n1 1Mb 100ms DropTail
# create TCP agents
set src [new Agent/TCP/FullTcp]
set sink [new Agent/TCP/FullTcp]
$ns attach-agent $n0 $src
$ns attach-agent $n1 $sink
$src set fid_ 0
$src set fid_ 0
$ns connect $src $sink
# set up TCP-level connections
$sink listen
$src set window_ 100
# create traffic generator
set ftp0 [new Application/FTP]
$ftp0 attach-agent $src
# run NS
$ns at 0.5 "$ftp0 start"
$ns at 5.0 "finish"
$ns run
-- Forwarded message --
From: Mobin Yazarlou
Date: Tue, Sep 14, 2010 at 9:44 AM
Subject: How to monitor TCP three way handshaking in NS2?
To: ns-users@isi.edu
Hi,
Based on what I read in NS manual, FullTcp agent supports TCP
three way handshaking but I don't know if it is possible to
monitor this process or not.
And also, I've got a problem with this agent.Could you take
a look at the following script and tell me why it gives an
error on "new Agent/TCP/FUllTcp" ? I am using ns-2.34 all in
one package.
Thanks,
Mobin
[1]set ns [new Simulator]
[2]
[3]# NAM file
[4]set nf [open outtcp1.nam w]
[5]$ns namtrace-all $nf
[6]
[7]# finish procedure
[8]proc finish {} {
[9] global ns nf
[10] $ns flush-trace
[11] close $nf
[12] exec nam outtcp1.nam &
[13] exit 0
[14]}
[15]
[16]
[17]# create nodes
[18]set n0 [$ns node]
[19]set n1 [$ns node]
[20]
[21]$ns duplex-link $n0 $n1 1Mb 100ms DropTail
[22]
[23]# create TCP agents
[24]set src [new Agent/TCP/FUllTcp]
[25]set sink [new Agent/TCP/FullTcp]
[26]
[27]$ns attach-agent $n0 $src
[28]$ns attach-agent $n1 $sink
[29]
[30]$src set fid_ 0
[31]$src set fid_ 0
[32]
[33]$ns connect $src $sink
[34]
[35]# set up TCP-level connections
[36]$sink listen
[37]$src set window_ 100;
[38]
[39]
[40]
[41]
[42]# run NS
[43]$ns at 0.5 "$src start"
[44]$ns at 5.0 "finish"
[45]$ns run
r...@ubuntu:~/NS234/mycodes# ns tcp1.tcl
invalid command name "Agent/TCP/FUllTcp"
while executing
"Agent/TCP/FUllTcp create _o36 "
invoked from within
"catch "$className create $o $args" msg"
invoked from within
"if [catch "$className create $o $args" msg] {
if [string match "__FAILED_SHADOW_OBJECT_" $msg] {
delete $o
return ""
}
global errorInfo
error "class $..."
(procedure "new" line 3)
invoked from within
"new Agent/TCP/FUllTcp"
invoked from within
"set src [new Agent/TCP/FUllTcp]"
(file "tcp1.tcl" line 24)
r...@ubuntu:~/NS234/mycodes#
[ns] How to monitor TCP three way handshaking in NS2?
Hi,
Based on what I read in NS manual, FullTcp agent supports TCP
three way handshaking but I don't know if it is possible to
monitor this process or not.
And also, I've got a problem with this agent.Could you take
a look at the following script and tell me why it gives an
error on "new Agent/TCP/FUllTcp" ? I am using ns-2.34 all in
one package.
Thanks,
Mobin
[1]set ns [new Simulator]
[2]
[3]# NAM file
[4]set nf [open outtcp1.nam w]
[5]$ns namtrace-all $nf
[6]
[7]# finish procedure
[8]proc finish {} {
[9] global ns nf
[10] $ns flush-trace
[11] close $nf
[12] exec nam outtcp1.nam &
[13] exit 0
[14]}
[15]
[16]
[17]# create nodes
[18]set n0 [$ns node]
[19]set n1 [$ns node]
[20]
[21]$ns duplex-link $n0 $n1 1Mb 100ms DropTail
[22]
[23]# create TCP agents
[24]set src [new Agent/TCP/FUllTcp]
[25]set sink [new Agent/TCP/FullTcp]
[26]
[27]$ns attach-agent $n0 $src
[28]$ns attach-agent $n1 $sink
[29]
[30]$src set fid_ 0
[31]$src set fid_ 0
[32]
[33]$ns connect $src $sink
[34]
[35]# set up TCP-level connections
[36]$sink listen
[37]$src set window_ 100;
[38]
[39]
[40]
[41]
[42]# run NS
[43]$ns at 0.5 "$src start"
[44]$ns at 5.0 "finish"
[45]$ns run
r...@ubuntu:~/NS234/mycodes# ns tcp1.tcl
invalid command name "Agent/TCP/FUllTcp"
while executing
"Agent/TCP/FUllTcp create _o36 "
invoked from within
"catch "$className create $o $args" msg"
invoked from within
"if [catch "$className create $o $args" msg] {
if [string match "__FAILED_SHADOW_OBJECT_" $msg] {
delete $o
return ""
}
global errorInfo
error "class $..."
(procedure "new" line 3)
invoked from within
"new Agent/TCP/FUllTcp"
invoked from within
"set src [new Agent/TCP/FUllTcp]"
(file "tcp1.tcl" line 24)
r...@ubuntu:~/NS234/mycodes#
[ns] help needed for AOMDV simulation
Hi all, I want to know that to run AOMDV in ns2.35 we just need to change the routing protocol to AOMDV and rest all things will be same as like in AODV or is there any other changes need to made in AODV tcl file to run the AOMDV protocol. Thanks, Ankur
[ns] Nodes are on a different frequency but can still communicate?
Dear all,
I'm trying to test the following scenario and I would appreciate your feedback.
I have three wireless nodes in a row, 0, 1 and 2. Each node supports multiple
interfaces, but for this scenario the nodes are configured with one interface
communicating over 802.15.4. A cbr connection is set between 0 and 2, so that
packets would flow between 0->1 and 1->2.
When I configure all the nodes with the following code, the network communicates
as expected.
for {set i 0} {$i < 3 } {incr i} {
$ns_ add-channel 0 $chan_(0) # associate channel with interface 0
[$node_($m) set netif_(0)] set Pt_ 0.003162
[$node_($m) set netif_(0)] set freq_ 2.45e+9
set dist(-90dbm) 1e-12
[$node_($m) set netif_(0)] set CPThresh_ 10.0
[$node_($m) set netif_(0)] set CSThresh_ $dist(-90dbm)
[$node_($m) set netif_(0)] set RXThresh_ $dist(-90dbm)
[$node_($m) set netif_(0)] set channel_number_ 20 # freq 2.45e+9 is on channel
20
}
However, when I configure nodes 0 and 2 to use the same frequency but node 1 to
use
a different frequency, the network still operates and gives exactly the same
results as previously.
$ns_ add-channel 0 $chan_(0) # this is configured for each node
# $m = 0,1,2
[$node_($m) set netif_(0)] set Pt_ 0.003162
set dist(-90dbm) 1e-12
[$node_($m) set netif_(0)] set CPThresh_ 10.0
[$node_($m) set netif_(0)] set CSThresh_ $dist(-90dbm)
[$node_($m) set netif_(0)] set RXThresh_ $dist(-90dbm)
#
[$node_(0) set netif_(0)] set freq_ 2.45e+9
[$node_(0) set netif_(0)] set channel_number_ 20
[$node_(1) set netif_(0)] set freq_ 2.48e+9
[$node_(1) set netif_(0)] set channel_number_ 26
[$node_(2) set netif_(0)] set freq_ 2.45e+9
[$node_(2) set netif_(0)] set channel_number_ 20
Since node 1 is set on a different frequency I would expect that the nodes
could
not communicate.
Is this a bug or am I doing something wrong?
Thank you in advance,
Lup.
