[ns] simulation in ns2 !
Hi friends, I have a simulated model as follow : CN HA \ / 100 Mbps \ / 100 Mbps 20 ms \ / 20 ms \ / N1 | | 100 Mbps | 150 ms | MAP / \ 10 Mbps /\ 10 Mbps // bandwidth 50 ms / \ 50 ms // delay /\ N2 N3 | | 1 Mbps | | 1 Mbps 50 ms | |50 ms PARNAR MN> Anyone explain for me parameters above. Why we choose them instead another one. In delays 50 ms, have any formula or choose arbitarily. I want to know that how do we explain about choosing delay 50 ms instead of 20 ms or 2 ms... Thank you very much ! Best regards, phathienhung.
Re: [ns] [Ns-developers] cbrgen generates more nodes than stated
Original Message Subject: Re: [Ns-developers] cbrgen generates more nodes than stated Date: Sun, 01 May 2011 13:11:59 -0700 From: Tom Henderson To: Hanqiang Shan CC: ns-users@ISI.EDU, ns-develop...@isi.edu On 04/13/2011 01:26 AM, Hanqiang Shan wrote: > Hi all, > When I was using the cbrgen.tcl to create data stream, I found that > the file created more nodes than I was stated. For example, when I > stated "-nn 10", the file actually created stream from node_(0) to > node_(10). And thus cause problems of the future simulation. > > When I look into the source code, I found that the code "set dst [expr > ($i+1) % [expr $opt(nn) + 1] ]" in line 166 could have caused the > problem. Why should $opt(nn) plus 1? > > I am looking forward to your reply. Thanks. > I added an issue in the bug tracker for this: http://mailman.isi.edu/pipermail/ns-developers/2011-April/008873.html If you would like to propose a patch and test it, please add it to the tracker. - Tom
[ns] Call For Papers: International Journal "Network Protocols and Algorithms"
* Call for Papers * Network Protocols and Algorithms ISSN 1943-3581 http://www.macrothink.org/journal/index.php/npa/ Network Protocols and Algorithms is a free-access online international journal, peer-reviewed and published by Macrothink Institute. It publishes papers focused on the design, development, manage, optimize or monitoring any type of network protocol, communication system, algorithm for communication and any protocol and algorithm to communicate network devices. The scope of the journal include, but are not limited to, the following topic areas: - Synchronization Protocols and Algorithms - Security Protocols and Algorithms - QoS Protocols and Algorithms - Ad-Hoc and Sensor Network Protocols and Algorithms - Content Delivery Networks Protocols and Algorithms - P2P Protocols and Algorithms - Cluster-Based Protocols and Algorithms - Real-Time Protocols and Algorithms - Wireless Protocols and Algorithms - MAC Protocols and Algorithms for Wired Networks - Mobile wireless internet protocols and algorithms - Delay Tolerant protocols and algorithms - Mesh network protocols and algorithms - Protocols and algorithms for Voice over IP delivery - Cognitive Radio Network Protocols and Algorithms - Monitoring and management protocols and algorithms - optical networking protocols and algorithms - Scalable Network Protocols and Algorithms - Protocols and algorithms for Green Computing and Resource Allocation - Routing Protocols and Algorithms - Tree-based Protocols and Algorithms - Distributed/Decentralized Algorithms for Networks - Fault tolerant Protocols and Algorithms - Protocols and algorithms for Mobile and Dynamic Networks - Cross-Layer Collaborative Protocols and Algorithms - Formal methods and cryptographic algorithms for communication - Power Efficient and Energy Saving Network Protocols and Algorithms - Multimedia Network Protocols and Algorithms - Network Protocols and Algorithms for Context-Aware and Semantic Networks - Localized Network Protocols and Algorithms - Transport Layer Protocols - Smart Grids protocols and algorithms Network Protocols and Algorithms has linked its papers to references by DOI (Digital Object Identifier) numbers. Network Protocols and Algorithms appears in the next search engines: Google Scholar, Bing, Yahoo and Ask. Network Protocols and Algorithms is added and indexed in Index Copernicus, ProQuest, EBSCO, Ulrichsweb.com, Directory of Open Access Journals (DOAJ), Open J-Gate, Gale, Socolar, io-port Database, NewJour - Electronic Journals and Newsletters, Public Knowledge Project metadata harvester, Ovid LinkSolver, Genamics JournalSeek and PublicationsList.org. It is also requested to be included in other major Indexing Databases. You are welcome to submit a paper or forward this call for papers to any people working in Network Protocols and Algorithms that may be interested in submitting a paper. The topics suggested by the journal can be discussed in term of concepts, state of the art, standards, implementations, running experiments and applications. Proposals and deployments are also welcome. Submission Information: Only original and unpublished research papers will be considered in this journal. Manuscripts must be writen in English. All submissions will be reviewed based on technical merit and relevance. Instructions for authors and submissions can be found in http://www.macrothink.org/journal/index.php/npa/about/submissions Jaime Lloret Mauri Editor in Chief of the International Journal of Network Protocols and Algorithms Associate Professor Department of Communications Polytechnic University of Valencia, Spain
Re: [ns] Segmentation fault (core dumped)
debug it with eclipse. http://wcms1.rz.tu-ilmenau.de/fakia/NS2-for-Eclipse.6025.0.html or http://hi.baidu.com/karashun/blog/item/cc4038d0f47db2359a50276d.html On Mon, May 2, 2011 at 12:02 AM, fauzan prasetyo eka putra wrote: > > Hi, my friend > my Tcl code for a NS-2 simulation link error model when i run TCL file i get > > > $ns script-olsr.tcl > Segmentation fault (core dumped) > > > > Please advice.what i must to do.. > > > Regards > > n0mad > >
[ns] Segmentation fault (core dumped)
Hi, my friend my Tcl code for a NS-2 simulation link error model when i run TCL file i get $ns script-olsr.tcl Segmentation fault (core dumped) Please advice.what i must to do.. Regards n0mad
[ns] Implementing flooding routing protocol (my own version)
Hi,
I'm new in NS2, I hope you can help me, I really need it. I have to implement a
routing protocol:
if there is a packet to send, it will be flooded
when a node receives a packet it will be dropped if the node had received it
before
When destination address of the incoming packet is the node itself i use the
node’s dmux to accept the incoming packet
I have to use cbr to generate traffic.
My problem is:
When destination address of the incoming packet is the node itself i can't do
anything the node always accepts the packet.
I use a cache to know what packets a nodes has received but it doesn't work in
the case of destination address of the
incoming packet is the node itself in all other cases it works.
My code is the next:
void Protoname::recv(Packet* p, Handler* h)
{
struct hdr_cmn* ch = HDR_CMN(p);
struct hdr_ip* ih = HDR_IP(p);
struct hdr_protoname_pkt *ph = HDR_PROTONAME_PKT(p);
if (message_cache.find(ih->saddr(), ch->uid())) { //Check if i have already
received
drop(p, DROP_RTR_ALREADY_RECEIVED);//So drop the packet
return;
}
else message_cache.add(ih->saddr(), ch->uid()); //If i hadn't already
received i add to the cache
if (ih->saddr() == ra_addr()) {
// If there exists a loop, must drop the packet
if (ch->num_forwards() > 0) {
drop(p, DROP_RTR_ROUTE_LOOP);
return;
}
// else if this is a packet I am originating, must add IP header
else if (ch->num_forwards() == 0){
ch->size() += IP_HDR_LEN;
}
}
ih->ttl_--;
if (ih->ttl_ == 0) {
drop(p, DROP_RTR_TTL);
return;
}
forward_data(p);
}
void Protoname::forward_data(Packet* p)
{
struct hdr_cmn* ch = HDR_CMN(p);
struct hdr_ip* ih = HDR_IP(p);
struct hdr_protoname_pkt *ph = HDR_PROTONAME_PKT(p);
if ( ih->daddr() == ra_addr()) {
dmux_->recv(p, (Handler*)0);
return;
}
else {
ch->direction() = hdr_cmn::DOWN;
ch->addr_type() = NS_AF_INET;
ch->next_hop() = IP_BROADCAST;
Scheduler::instance().schedule(target_, p, 0.0);
}
}
My simulation:
set udp [new Agent/UDP]
$ns_ attach-agent $node_(4) $udp
set null [new Agent/Null]
$ns_ attach-agent $node_(0) $null
$ns_ connect $udp $null
set cbr [new Application/Traffic/CBR]
$cbr set interval_ 1
$cbr attach-agent $udp
$ns_ at 1 "$cbr start"
$ns_ at 1.4 "$cbr stop"
Trace:
1.0 _4_ AGT --- 0 cbr 210 [0 0 0 0] --- [4:0 0:0 32 0] [0] 0 0
r 1.0 _4_ RTR --- 0 cbr 210 [0 0 0 0] --- [4:0 0:0 32 0] [0] 0 0
s 1.0 _4_ RTR --- 0 PROTONAME 230 [0 0 0 0] --- [4:0 0:0 31 0]
r 1.002864000 _10_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
31 0]
f 1.002864000 _10_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
30 0]
r 1.002864005 _5_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
31 0]
r 1.002864005 _11_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
31 0]
f 1.002864005 _5_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
30 0]
f 1.002864005 _11_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
30 0]
r 1.002864007 _3_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
31 0]
r 1.002864007 _9_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
31 0]
f 1.002864007 _3_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
30 0]
f 1.002864007 _9_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
30 0]
r 1.002864030 _8_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
31 0]
r 1.002864030 _2_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
31 0]
f 1.002864030 _8_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
30 0]
f 1.002864030 _2_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
30 0]
r 1.002864054 _6_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
31 0]
r 1.002864054 _0_ AGT --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
31 0]
f 1.002864054 _6_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
30 0]
r 1.002864058 _7_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
31 0]
r 1.002864058 _1_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
31 0]
f 1.002864058 _7_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
30 0]
f 1.002864058 _1_ RTR --- 0 PROTONAME 230 [0 4 800] --- [4:0 0:0
30 0]
r 1.005268007 _9_ RTR --- 0 PROTONAME 230 [0 3 800] --- [4:0 0:0
30 0]
D 1.005268007 _9_ RTR ALREADY_RECEIVED 0 PROTONAME 230 [0 3 800]
--- [4:0 0:0 30 0]
r 1.005268011 _5_ RTR --- 0 PROTONAME 230 [0 3 800] --- [4:0 0:0
30 0]
D 1.005268011 _5_ RTR ALREADY_RECEIVED 0 PROTONAM
[ns] PUMA out of order RTP packets
Hi , I am sending RTP traffic over PUMA but the packets arrive at the destinations out of order. for example if i send 4 packets at time X , they will arrive in random order and not considering their sequence number. Is there a solution to this as in order to evaluate the video trace i need them in correct order. Fivos.
[ns] sending complex packets
hi, my project in tcp performance over wireless MIMO channels with ARq in which i have to send complex conjugate packets over channel in a time interval how can we realise complex packets in TCL pls reply.its urgent -- View this message in context: http://old.nabble.com/sending-complex-packets-tp31518122p31518122.html Sent from the ns-users mailing list archive at Nabble.com.
Re: [ns] LEACH Implementation
Hello Sachin, Following link may be of some help: http://www.internetworkflow. com/resources/ns2leach.pdf Hope it helps. Regards, Mohit P. Tahiliani
Re: [ns] instant awk script old trace format
Dear Mike, Some AWK scripts are available on the following link: http://www.reti.polito.it/fiore/trace2stats_v05b.tgz and other on: http://www.megaupload.com/?f=0211SAG1 Hope it helps. Regards, Mohit P. Tahiliani
Re: [ns] NS2& EvalVid urgent
yes you can run them. Check http://www.tcl.tk/man/tcl8.5/tutorial/Tcl26.html On Sun, May 1, 2011 at 11:06 AM, Tami Nesher wrote: > > Hi, > I am asking about the example in the link: > http://140.116.72.80/~smallko/ns2/myevalvid2.htm > I want to know if I can run the commands like ./etmp4 etc in the tcl > file? > I need that the correct video will be the *output* of the *tcl* file. > Thanks. >
[ns] NS2& EvalVid urgent
Hi, I am asking about the example in the link: http://140.116.72.80/~smallko/ns2/myevalvid2.htm I want to know if I can run the commands like ./etmp4 etc in the tcl file? I need that the correct video will be the *output* of the *tcl* file. Thanks.
