tag:old.nabble.com,2006:forum-15582Nabble - Network Simulator ns-22009-11-21T05:51:24Z<a href="http://www.isi.edu/nsnam/ns/" target="_top" rel="nofollow">NS</a> is a discrete event simulator targeted at networking research. Ns provides substantial support for simulation of TCP, routing, and multicast protocols over wired and wireless (local and satellite) networks.tag:old.nabble.com,2006:post-26456765Implementing algorithms in NS22009-11-21T05:51:24Z2009-11-21T05:51:24ZRip van WinkleHi.
<br>I've just started using NS2.29 for my wireless sensor networks project. Now the problem is that I have to implement a spanning tree algorithm for a set of nodes. How do I do it? Should I first code it in C++ and then add it? If so, should there be any changes in the C++ code so as to be compatible with NS2. I am really new to this whole world of Simulators <img class='smiley' src='http://old.nabble.com/images/smiley/anim_confused.gif' /> Could someone please post some links of some good ns2 tutorials.
<br><br>Also there is some problem with my nam. Its not running.
<br><br>Please help<p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>tag:old.nabble.com,2006:post-26460334REPLY Pure Wireless networking with a BS and two mobile nodes2009-11-21T02:36:31Z2009-11-21T02:36:31ZSoftware Quality Center<br><br><br><br><br>----- Forwarded Message ----
<br>From: Software Quality Center <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26460334&i=0" target="_top" rel="nofollow">softwarequalitycenter@...</a>>
<br>To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26460334&i=1" target="_top" rel="nofollow">ns-users@...</a>
<br>Sent: Wed, November 18, 2009 3:17:15 PM
<br>Subject: Pure Wireless networking with a BS and two mobile nodes
<br><br><br>Hi,
<br><br> I tried to send a packet from one mobile station to another using a base station.
<br>It is received by the BS but not received by the second MS.
<br>Can you write a few line script to do the same ?
<br><br>Thanks:
<br><br><br>details of my work:
<br><br>$ns node-config -adhocRouting $opt(adhocRouting) \
<br> -llType $opt(ll) \
<br> -macType $opt(mac) \
<br> -ifqType $opt(ifq) \
<br> -ifqLen $opt(ifqlen) \
<br> -antType $opt(ant) \
<br> -propType $opt(prop) \
<br> -phyType $opt(netif) \
<br> -channel [new $opt(chan)] \
<br> -topoInstance $topo \
<br> -wiredRouting OFF \
<br> -agentTrace ON \
<br> -routerTrace OFF \
<br> -macTrace OFF \
<br> -movementTrace OFF
<br><br><br>Then I created bs, attached two ms to bs.
<br>UDP agent to one ms, null agent to another ms(sink node).
<br>start application.
<br>Sends properly upto the bs, but the sink node doesn't receive.
<br><br>I use DSDV routing as my adhocRouthing protocol , and it is heirarchical.
<br><br><br>
<br><p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>tag:old.nabble.com,2006:post-26444734Re: Buildbots failures/Deprecated PeekData/AODV example test failing2009-11-20T06:58:29Z2009-11-20T06:58:29ZMathieu LacageOn Fri, 2009-11-20 at 15:42 +0100, Faker Moatamri wrote:
<div class='shrinkable-quote'><br>> Hi all,
<br>> We have a buildbot errors for g++-3.4.6,4.0.4,4.1.2 under linux, for
<br>> OSX-PPC g++-4.0 and for Mingw:
<br>>
<br>> [397/917] cxx: src\common\packet.cc -> build\debug\src\common\packet_1.o
<br>> ..\src\common\packet.cc: In member function `virtual bool ns3::PacketTest::DoRun()':
<br>>
<br>> ..\src\common\packet.cc:929: warning: `PeekData' is deprecated (declared at ..\src\common\packet.cc:339)
<br>>
<br>> ..\src\common\packet.cc:1089: warning: `PeekData' is deprecated (declared at ..\src\common\packet.cc:339)
</div><br>I am waiting for the ipv6 stuff to be merged before fixing this. If it's
<br>a problem anyone can go ahead and remove the NS_DEPRECATED in packet.h
<br><br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26444406Buildbots failures/Deprecated PeekData/AODV example test failing2009-11-20T06:42:17Z2009-11-20T06:42:17ZFaker MoatamriHi all,
<br>We have a buildbot errors for g++-3.4.6,4.0.4,4.1.2 under linux, for
<br>OSX-PPC g++-4.0 and for Mingw:
<br><br>[397/917] cxx: src\common\packet.cc -> build\debug\src\common\packet_1.o
<br>..\src\common\packet.cc: In member function `virtual bool ns3::PacketTest::DoRun()':
<br><br>..\src\common\packet.cc:929: warning: `PeekData' is deprecated (declared at ..\src\common\packet.cc:339)
<br><br>..\src\common\packet.cc:1089: warning: `PeekData' is deprecated (declared at ..\src\common\packet.cc:339)
<br><br><br>This is simply a warning taken as an error.
<br><br>For Cygwin, there is a testing crash:
<br><br>---------- begin standard err ----------
<br>pure virtual method called
<br>terminate called without an active exception
<br><br>---------- end standard err ----------
<br>CRASH: Example routing/aodv
<br>Launch examples/stats/wifi-example-sim
<br>Synchronously execute /home/mathieu/buildslave/full-cygwin-g++/build/build/debug/examples/stats/wifi-example-sim
<br>Return code = 0
<br>stderr =
<br>returncode = 0
<br><br>It seems like there is a pure virtual method called??? =-O
<br><br>Any fixes/suggestions are welcome.
<br><br>Best regards
<br>Faker Moatamri
<br><br><br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26439159RSVP in NS-2.2009-11-20T03:25:59Z2009-11-20T03:25:59ZTurin36Hi all,
<br><br>I want to patch RSVP in NS-2. Can anyone help me how i can do it?
<br>The commands, in which folders e.t.c...and with which version of Cygwin?
<br><br>Regards
<br>Constantine.<p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>tag:old.nabble.com,2006:post-26435370question regarding LAN2009-11-19T14:35:49Z2009-11-19T14:35:49Zsashtari<br>Hi every body
<br><br>I have a question about the LANs:
<br>I have some nodes in a LAN, a udp agent is attached to one of them.
<br>Now I'm looking for a way that all of the other nodes receives the packets
<br>form the udp agent attached to the first node.
<br>I've attached Null/Agents to the other nodes but I don't know how these
<br>Null/Agents should be connected to the same UDP agent.
<br><br>Thanks for reply
<br>Saeideh
<br><br><p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>tag:old.nabble.com,2006:post-26427745Bug #4732009-11-19T06:58:32Z2009-11-19T06:58:32ZFaker MoatamriHi Tom & Francesco,
<br>I took a look at the bug #473 which deals with ns-2 mobility files.
<br><a href="http://www.nsnam.org/bugzilla/show_bug.cgi?id=473" target="_top" rel="nofollow">http://www.nsnam.org/bugzilla/show_bug.cgi?id=473</a><br>Mathieu said that we should have a mode variable which will check the
<br>manner in which we will interpret ns-2 mobility files.
<br>Francesco did you do anything about this?
<br>Does anyone of you have test files to test that this is actually working?
<br>Best regards
<br>Faker Moatamri
<br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26426223Buildbot/Bazaar/PyBindgen2009-11-19T05:26:57Z2009-11-19T05:26:57ZFaker MoatamriHi all,
<br>Since PyBindgen is not working properly in buildbot I fixed some issues:
<br>- Updated the bazaar binary in Mingwin (bazaar is used to download
<br>PyBindgen)
<br>- Updated the bazaar binary in Mac OS ppc build slave
<br>- Changed the script in buildbot master to get the right version of pybingen
<br>- Changed the script in buildbot master to generate the version file in
<br>pybindgen using waf included in the pybindgen distribution
<br>Now updating pybindgen and generating the version should be ok.
<br>Best regards
<br>Faker Moatamri
<br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26421327how to modify some field value in IP Packet Header ?2009-11-19T05:07:26Z2009-11-19T05:07:26ZmhmdodehDear Sir,
<br><br>
<br>How are you? Hope you have a nice day…
<br><br>I am a master student, interesting in Routing Path Authentication schemes, and using NS2 simulator for my thesis simulation.
<br><br>Would you please help me to do the following in NS2 simulator:
<br><br>
<br>How can a router modify some field at IP packets header? e.g. how to set the value of TTL or Flags Field to a new value?
<br><br>
<br>As I know, it's easy to set the packet size value (set packet_size_ 500)
<br><br>
<br>Similarly, how to set any field in IP Packet header by TCL commands? Or using any appropriate method?
<br><br>
<br>I am very grateful for your help….
<br><br>
<br>Sincerely yours.
<br><br><p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>tag:old.nabble.com,2006:post-26425755Tracegraph availability2009-11-19T04:55:03Z2009-11-19T04:55:03ZJoel Bermúdez<br>Hi all:
<br><br>Someone is currently using this program? I would ask you to tell me the
<br>latest version to download or send me the link.
<br><p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>tag:old.nabble.com,2006:post-26425221Multicasting over Broadcast LAN, problem2009-11-19T04:12:59Z2009-11-19T04:12:59ZHameed Abdul<br>Dear All,
<br><br> I want to use multicasting on Broadcast LAN. my topology is
<br>given below,
<br><br> n0 n1 n3 n4
<br> | | | |
<br> -----------------------------------------------------------
<br> | | | |
<br> n5 n6 n7 n8
<br><br>there is only multicast group containing three nodes i.e mcastGroup1 = n0,
<br>n3, n6. Node n0 is the sender on this group. All the tree nodes of the
<br>group join the group and then the sender n0 start sending the data. Since
<br>the media is Broadcast so the all the nodes drop the packet. What i want
<br>here is that nodes n3 and n6 should not drop but should shows receive "r"
<br>event in the trace. I use PIM DM (Dense Mode) as multicasting protocol. the
<br>trace is given below,
<br>------------------------------------------------------------------------------------------------------------
<br>v 1 eval {set sim_annotation {1 0 join-group -2147483648}}
<br>v 1 eval {set sim_annotation {1 3 join-group -2147483648}}
<br>v 1 eval {set sim_annotation {1 6 join-group -2147483648}}
<br>h 1.1 0 9 cbr 210 ------- 0 0.2 -2147483648.0 0 0
<br>+ 1.102 0 9 cbr 210 ------- 0 0.2 -2147483648.0 0 0
<br>- 1.102 0 9 cbr 210 ------- 0 0.2 -2147483648.0 0 0
<br>d 1.102004 8 9 cbr 210 ------- 0 0.2 -2147483648.0 0 0
<br>d 1.102004 7 9 cbr 210 ------- 0 0.2 -2147483648.0 0 0
<br>d 1.102004 6 9 cbr 210 ------- 0 0.2 -2147483648.0 0 0
<br>d 1.102004 5 9 cbr 210 ------- 0 0.2 -2147483648.0 0 0
<br>d 1.102004 4 9 cbr 210 ------- 0 0.2 -2147483648.0 0 0
<br>d 1.102004 3 9 cbr 210 ------- 0 0.2 -2147483648.0 0 0
<br>d 1.102004 2 9 cbr 210 ------- 0 0.2 -2147483648.0 0 0
<br>d 1.102004 1 9 cbr 210 ------- 0 0.2 -2147483648.0 0 0
<br> -----------------------------------------------------------------------------------------------------------------------------
<br>the multicast configuration script is
<br>set mrthandle [$ns mrtproto DM {}] ;# setting multicast routing algo as PIM
<br>with Dense mode
<br>set mcastGroup1 [Node allocaddr]
<br>set mcastCbr0 [new Application/Traffic/CBR]
<br>set mcastUdp0 [new Agent/UDP]
<br>$mcastCbr0 attach-agent $mcastUdp0
<br>$ns attach-agent $node(0) $mcastUdp0
<br>$mcastUdp0 set dst_addr_ $mcastGroup1
<br>$mcastUdp0 set dst_port_ 0
<br>set rcvr [new Agent/LossMonitor]
<br>$ns attach-agent $node(3) $rcvr
<br>#// mcast testing script
<br>$ns at 1.0 "$node(0) join-group $rcvr $mcastGroup1"
<br>$ns at 1.0 "$node(3) join-group $rcvr $mcastGroup1"
<br>$ns at 1.0 "$node(6) join-group $rcvr $mcastGroup1"
<br>$ns at 1.1 "$mcastCbr0 start"
<br>$ns at 1.1 "$mcastCbr0 stop"
<br>$ns at 3.0 "simFinished"
<br># Now start the simulator.
<br>$ns run
<br>-------------------------------------------------------------------------------
<br>I am suspected that if i attach a router to the LAN in the simultation then
<br>the problem could be solved. But i wonder if there is a default LanRouter
<br>with each lan node? and how to use it?.
<br> Wanted an urgent help... ... please
<br><p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>tag:old.nabble.com,2006:post-26424656Re: GetObject in DoStart2009-11-19T03:28:28Z2009-11-19T03:28:28ZMathieu LacageOn Thu, 2009-11-19 at 13:42 +0300, Pavel Boyko wrote:
<br><br>> Am I wrong in using DoStart() and/or GetObject() or this is an Object's bug?
<br><br>This is a bug in Object. I will try to fix it asap.
<br><br>thanks for this helpful testcase,
<br>Mathieu
<br><br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26424615Re: Python bindings failure2009-11-19T03:23:57Z2009-11-19T03:23:57ZMathieu LacageOn Thu, 2009-11-19 at 11:20 +0000, Gustavo Carneiro wrote:
<div class='shrinkable-quote'><br>>
<br>> Ok, fair enough for me. However, it would be nice to add a
<br>> temporary
<br>> hack to nstime.h if we can to make it easier for developers to
<br>> rescan
<br>> the bindings when needed and remove the hack once the fix is
<br>> merged in
<br>> gccxml.
<br>>
<br>>
<br>> Done.
</div><br>thanks a bunch !
<br><br>Mathieu
<br>>
<br><br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26424579Re: Python bindings failure2009-11-19T03:20:40Z2009-11-19T03:20:40ZGustavo Carneiro2009/11/18 Mathieu Lacage <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26424579&i=0" target="_top" rel="nofollow">mathieu.lacage@...</a>>
<br><div class='shrinkable-quote'><br>> On Wed, 2009-11-18 at 12:48 +0000, Gustavo Carneiro wrote:
<br>>
<br>> >
<br>> > I had already updated the required gccxml version in the wiki page,
<br>> > see:
<br>> >
<br>> <a href="http://www.nsnam.org/wiki/index.php/NS-3_Python_Bindings#The_semi-automatic_way" target="_top" rel="nofollow">http://www.nsnam.org/wiki/index.php/NS-3_Python_Bindings#The_semi-automatic_way</a><br>> >
<br>> > I had started to use that gccxml snapshot from september, with
<br>> > pygccxml 1.0, and updated the wiki page, but I guess I forgot to
<br>> > notify the ns-developers list. Sorry about that.
<br>> >
<br>> > No, we cannot stick to old versions. Newer pygccxml does not work
<br>> > well with old gccxml, we have to move forward or we stagnate and
<br>>
<br>> Ok, that might explain some crazy warnings/errors I get on some systems
<br>> I use.
<br>>
<br>> > die. I have today updated to gccxml HEAD and it works fine, apart
<br>> > from that bug I reported. I don't like constantly using bleeding
<br>> > edge (you know well how I like things stable), but I think about once
<br>> > a year is reasonable to request that people upgrade their tools, don't
<br>> > you think?
<br>>
<br>> Ok, fair enough for me. However, it would be nice to add a temporary
<br>> hack to nstime.h if we can to make it easier for developers to rescan
<br>> the bindings when needed and remove the hack once the fix is merged in
<br>> gccxml.
<br>>
<br>>
</div>Done.
<br><br>--
<br>Gustavo J. A. M. Carneiro
<br>INESC Porto, Telecommunications and Multimedia Unit
<br>"The universe is always one step beyond logic." -- Frank Herbert
<br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26424053GetObject in DoStart2009-11-19T02:42:38Z2009-11-19T02:42:38ZPavel Boyko Hi,
<br><br> I encounter a problem using DoStart () to find companion objects aggregated
<br>to the same node via GetObject () method. Attached start-get.cc program
<br>illustrates this. It's expected output is
<br><br>A::DoStart ()
<br>B::DoStart ()
<br><br> which means that both aggregated objects are started. Instead of this I have
<br><br>A::DoStart ()
<br>A::DoStart ()
<br><br> which means that object a is started two times and object b is never stared.
<br>The behavior returns to normal if GetObject<B>() call is commented (try this).
<br><br> Am I wrong in using DoStart() and/or GetObject() or this is an Object's bug?
<br><br> Best regards,
<br> Pavel
<br><br /><tt>[start-get.cc]</tt><br /><hr align="left" width="300" /><tt>#include "ns3/object.h"
<br>#include "ns3/node.h"
<br>#include "ns3/simulator.h"
<br>#include <iostream>
<br><br>using namespace ns3;
<br><br>struct B;
<br><br>struct A : public Object
<br>{
<br> static TypeId GetTypeId ()
<br> {
<br> static TypeId tid = TypeId ("A").SetParent<Object>().AddConstructor<A>();
<br> return tid;
<br> }
<br>
<br> void DoStart ()
<br> {
<br> std::cerr << "A::DoStart ()\n";
<br>
<br> // Comment 3 lines below to get correct DoStart() behavior
<br> NS_ASSERT (node);
<br> Ptr<B> b = node->GetObject<B> ();
<br> NS_ASSERT (b);
<br> }
<br>
<br> Ptr<Node> node;
<br>};
<br>NS_OBJECT_ENSURE_REGISTERED (A);
<br><br>struct B : public Object
<br>{
<br> static TypeId GetTypeId ()
<br> {
<br> static TypeId tid = TypeId ("B").SetParent<Object>().AddConstructor<B>();
<br> return tid;
<br> }
<br><br> void DoStart ()
<br> {
<br> std::cerr << "B::DoStart ()\n";
<br> }
<br>};
<br>NS_OBJECT_ENSURE_REGISTERED (B);
<br><br>int main ()
<br>{
<br> Ptr<Node> node = CreateObject<Node> ();
<br>
<br> Ptr<A> a = CreateObject<A> ();
<br> a->node = node;
<br> node->AggregateObject (a);
<br>
<br> Ptr<B> b = CreateObject<B> ();
<br> node->AggregateObject (b);
<br>
<br> Simulator::Stop (Seconds (1));
<br> Simulator::Run ();
<br> Simulator::Destroy ();
<br>
<br> return 0;
<br>}
<br></tt><hr align="left" width="300" /><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26423483Re: NS-3.7 new feature merge period expired2009-11-19T01:49:28Z2009-11-19T01:49:28ZFaker MoatamriTom Henderson wrote:
<div class='shrinkable-quote'><br>> Faker Moatamri wrote:
<br>>> Hi all,
<br>>> As of today, Wednesday November 18^th , the new feature merge period
<br>>> is finished and the small feature development and bug fixing started.
<br>>> During this period you can:
<br>>>
<br>>> * Submit limited, small, self contained changes/features to ns-3-dev
<br>>> and to merged new features. As specified before, no more new
<br>>> feature merges are accepted
<br>>
<br>> Can you please comment on whether the patch that Antti is working on
<br>> for bug 742 (implementation of SO_BINDTODEVICE), and bug 671
<br>> (RecvIfIndex) are acceptable to you as small features (and other
<br>> things like this)?
<br>>
</div>Yes, they are acceptable as small features.
<div class='shrinkable-quote'><br>>> * Submit code for review, this is very useful as this will make it
<br>>> easier to merge your code early in the next release
<br>>> * Cleanup the ns-3-dev bug tracker, solve as much bugs as possible
<br>>
<br>> How would you like bug marking/prioritizing to work for the next
<br>> phase? We have a number of bugs that are just in the tracker as
<br>> default P5 but we could try to assign them as P1/P2 and
<br>> Blocker/Critical-- do you want to do this or should the maintainers
<br>> take a pass through them? As new bugs come in, should we receive an
<br>> ack from you before we mark P1/Blockers?
</div>It would be very helpful if the maintainers take a pass on the bugs and
<br>assign priorities and notify me if a bug is marked P1/Blocker and why he
<br>did that so that I can keep track of critical bugs.
<br><br>My bug policy now is to solve as many bugs as we can, starting with the
<br>most critical but not forgetting bugs who are in the bug tracker since
<br>2007 and bugs with patches waiting to be reviewed. We have nearly two
<br>months for that and I think we can do it.
<br>>
<br>> Ongoing, do you want us to update the ns-3.7 wiki page on "Bugs for
<br>> 3.7" or do you want to use the tracker for this only?
<br>>
<br>I think keeping track of the bug on the wiki page might be of interest
<br>to have an overview of the release status.
<br>> - Tom
<br><br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26422013Re: Test regression2009-11-18T23:54:53Z2009-11-18T23:54:53ZTom Henderson-2Faker,
<br><br>I went through the traces tonight to compare against ns-3.6 traces.
<br>These tests were failing:
<br><br>1) test-csma-broadcast
<br>2) test-csma-ping
<br>3) test-dynamic-global-routing
<br>4) test-global-routing-slash32
<br>5) test-simple-error-model
<br>6) test-simple-global-routing
<br>7) test-simple-point-to-point-olsr
<br>8) test-static-routing-slash32
<br>9) tcp-large-transfer
<br><br>Sebastien made an ascii trace format change for PPP (from hex to
<br>decimal) and then reverted it. Since on Sunday night, I aligned
<br>ns-3-dev-ref-traces with Sebastien's intermediate ascii format, these
<br>traces had to be reverted. Only the ascii traces of these files
<br>changed. With this checkin, I double checked each one that they have
<br>not changed since ns-3.6 version.
<br><br>3) test-dynamic-global-routing
<br>4) test-global-routing-slash32
<br>5) test-simple-error-model
<br>6) test-simple-global-routing
<br>8) test-static-routing-slash32
<br>9) tcp-large-transfer
<br><br>The above reverts were committed in one changeset to ns-3-dev-ref-traces
<br> (rev 94)
<br><br>The remaining traces are expected to have changed since ns-3.6, due to
<br>Pavel's changes:
<br><br>2) test-csma-ping
<br><br>These have changed due to ping application changes:
<br>- default length of ping changed
<br>- pings now repeat after every interval seconds
<br><br>I fixed this with rev 95 in ns-3-dev-ref-traces
<br><br><br>1) test-csma-broadcast
<br>7) test-simple-point-to-point-olsr
<br>The two fields that have changed in these traces are the TTL of
<br>broadcast messages (from 1 to 64) and the IP ID. The IP ID field
<br>changed due to the AODV checkin due to this change in UDP:
<br><br>--- a/src/internet-stack/udp-socket-impl.cc
<br>+++ b/src/internet-stack/udp-socket-impl.cc
<br>@@ -373,6 +373,8 @@
<br>// Get the primary address
<br>Ipv4InterfaceAddress iaddr = ipv4->GetAddress (i, 0);
<br>Ipv4Address addri = iaddr.GetLocal ();
<br>+ if (addri == Ipv4Address ("127.0.0.1"))
<br>+ continue;
<br>Ipv4Mask maski = iaddr.GetMask ();
<br>if (maski == Ipv4Mask::GetOnes ())
<br><br>which suppresses broadcast to loopback.
<br><br>I fixed this with ref 96 in ns-3-dev-ref-traces
<br><br><br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26420977Calculation of dymanic bandwidth2009-11-18T22:20:50Z2009-11-18T22:20:50ZhiruI am working on ns2 for the first time.I basically have to calculate the dynamic bandwidth available using admission control that is giving priority to real time flow over non real time.I donot know where to insert the bandwidth calculation code.Can anybody please help me.I am in big trouble.<p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>tag:old.nabble.com,2006:post-26420969Calculation of dymanic bandwidth2009-11-18T22:20:14Z2009-11-18T22:20:14ZhiruI am working on ns2 for the first time.I basically have to calculate the dynamic bandwidth available using admission control that is giving priority to real time flow over non real time.I donot know where to insert the bandwidth calculation code.Can anybody please help me.I am in big trouble.<p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>tag:old.nabble.com,2006:post-26412704Re: Clarification regarding DCF Manager needed2009-11-18T10:01:05Z2009-11-18T10:01:05ZMathieu LacageOn Wed, 2009-11-18 at 16:47 +0100, Jens Mittag wrote:
<br><br>> Does the DCF manager resolve the overlap internally automatically? From
<br>> how I understand the code, I would say yes...
<br><br>Theoretically, yes, but no one can be sure there are no bugs.
<br><br>The relevant piece of code is, I believe, the following from
<br>DcfManager::GetAccessGrantStart
<br><br>Time accessGrantedStart = MostRecent (rxAccessStart,
<br> busyAccessStart,
<br> txAccessStart,
<br> navAccessStart,
<br> ackTimeoutAccessStart,
<br> ctsTimeoutAccessStart,
<br> switchingAccessStart
<br> );
<br><br>Mathieu
<br><br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26411827WiMAX merge2009-11-18T09:14:16Z2009-11-18T09:14:16ZiamineHi Tom and All,
<br><br>I have pushed a new version of the wimax module to
<br><a href="http://code.nsnam.org/iamine/ns-3-wimax-release/" target="_top" rel="nofollow">http://code.nsnam.org/iamine/ns-3-wimax-release/</a>. This new version provides:
<br><br>1) 4 test suites for wimax
<br> - ns3-wimax-qos including 3 test cases
<br> - wimax-phy-layer including 2 test cases
<br> - wimax-bs-mac-layer including 2 test cases
<br> - wimax-ss-mac-layer including 5 test cases
<br>2) Adding more attributes to the following classes:
<br> - wimax-ss-net-device: 17 Attributes
<br> - wimax-bs-net-device: 13 Attributes
<br> - simple-ofdm-wimax-phy: 7 Attributes
<br>3) Aligning trace sources of wimax-ss-net-device, wimax-bs-net-device
<br>and wimax-phy with trace sources of the wifi module
<br><br>The module has been merged with the latest ns-3-dev version (changeset
<br>5754) and has been successfully compiled under g++4.2.4, 4.3.3 and 4.4.0
<br>in both debug and optimized mode. The examples I have developed have
<br>been successfully executed with valgrind which reports 0 error.
<br><br>I would like to ask you kindly to review this module.
<br><br>Thank you
<br>Regards
<br>Amine
<br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26411730Test regression2009-11-18T09:09:28Z2009-11-18T09:09:28ZFaker MoatamriHi Tom & all,
<br><br>Test pavel's patch:
<br>Revision 5534: updated traces to make them work
<br>Revision 5738: got 3 errors after Pavel's patch(test-csma-broadcast,
<br>test-csma-ping, test-simple-point-to-point-olsr)
<br>Revision 5740: No errors (after Pavel fixes)
<br>Revision 5744: using bisect we determine that it's this revision that is
<br>causing the problem, Sebastian's fix (test-dynamic-global-routing,
<br>test-global-routing-slash32, test-simple-error-model,
<br>test-simple-global-routing, test-simple-point-to-point-olsr,
<br>test-static-routing-slash32, test-tcp-large-transfer)
<br><br>Test Sebastian's patch:
<br>Revision 5502: update reference traces to make this works
<br>Revision 5503: doesn't work of course:(test-dynamic-global-routing,
<br>test-global-routing-slash32, test-simple-error-model,
<br>test-simple-global-routing, test-simple-point-to-point-olsr,
<br>test-static-routing-slash32, test-tcp-large-transfer)
<br>Revision 5740: failed (test-csma-broadcast, test-csma-ping,
<br>test-dynamic-global-routing, test-global-routing-slash32,
<br>test-simple-error-model, test-simple-global-routing,
<br>test-simple-point-to-point-olsr, test-static-routing-slash32,
<br>test-tcp-large-transfer)
<br>Revision 5744: failed (test-csma-broadcast, test-csma-ping,
<br>test-simple-point-to-point-olsr)
<br>Revision 5754: failed (test-csma-broadcast, test-csma-ping,
<br>test-simple-point-to-point-olsr)
<br><br>It looks like it is because of Sebastian's patchs or someone else's
<br>patch, assuming that pavel's regression failure is fixed in 5740.
<br><br>Hope this helps
<br><br>Best regards
<br>Faker Moatamri
<br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26410311Clarification regarding DCF Manager needed2009-11-18T07:47:55Z2009-11-18T07:47:55ZJens Mittag-2Hi!
<br><br>I am working on a CCA implementation for Wifi and would like to make
<br>sure that I understand the DCF manager implementation correctly:
<br><br>When I call the following functions
<br><br> NotifyTxStartNow (Time duration);
<br> NotifyMaybeCcaBusyStartNow (Time duration);
<br><br>with the usage of 2 different values for the duration parameter, e.g. I
<br>would call
<br><br> NotifyTxStartNow (2secs); at time t = 1secs
<br><br> and
<br><br> NotifyMaybeCcaBusyStartNow (2secs); at time t = 2secs
<br><br>Does the DCF manager resolve the overlap internally automatically? From
<br>how I understand the code, I would say yes...
<br><br>Thanks for the clarification
<br> Jens
<br><br>--
<br>Dipl.-Inform. Jens Mittag
<br>Karlsruhe Institute of Technology (KIT)
<br>Institute of Telematics
<br>Decentralized Systems and Network Services Research Group
<br><br>Engesserstr. 2, 76131 Karlsruhe, Germany
<br>Building 20.50, Room 112
<br><br>Phone: +49 (721) 608 5768
<br>Fax: +49 (721) 608 6789
<br><br><a href="http://dsn.tm.uni-karlsruhe.de/" target="_top" rel="nofollow">http://dsn.tm.uni-karlsruhe.de/</a><br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26409869Re: NS-3.7 new feature merge period expired2009-11-18T07:24:35Z2009-11-18T07:24:35ZTom Henderson-2Faker Moatamri wrote:
<br>> Hi all,
<br>> As of today, Wednesday November 18^th , the new feature merge period is
<br>> finished and the small feature development and bug fixing started.
<br>> During this period you can:
<br>>
<br>> * Submit limited, small, self contained changes/features to ns-3-dev
<br>> and to merged new features. As specified before, no more new
<br>> feature merges are accepted
<br><br>Can you please comment on whether the patch that Antti is working on for
<br>bug 742 (implementation of SO_BINDTODEVICE), and bug 671 (RecvIfIndex)
<br>are acceptable to you as small features (and other things like this)?
<br><br>> * Submit code for review, this is very useful as this will make it
<br>> easier to merge your code early in the next release
<br>> * Cleanup the ns-3-dev bug tracker, solve as much bugs as possible
<br><br>How would you like bug marking/prioritizing to work for the next phase?
<br> We have a number of bugs that are just in the tracker as default P5
<br>but we could try to assign them as P1/P2 and Blocker/Critical-- do you
<br>want to do this or should the maintainers take a pass through them? As
<br>new bugs come in, should we receive an ack from you before we mark
<br>P1/Blockers?
<br><br>Ongoing, do you want us to update the ns-3.7 wiki page on "Bugs for 3.7"
<br>or do you want to use the tracker for this only?
<br><br>- Tom
<br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26409642Re: Python bindings failure2009-11-18T07:11:14Z2009-11-18T07:11:14ZFaker MoatamriMathieu Lacage wrote:
<div class='shrinkable-quote'><br>> On Wed, 2009-11-18 at 12:48 +0000, Gustavo Carneiro wrote:
<br>>
<br>>
<br>>> I had already updated the required gccxml version in the wiki page,
<br>>> see:
<br>>> <a href="http://www.nsnam.org/wiki/index.php/NS-3_Python_Bindings#The_semi-automatic_way" target="_top" rel="nofollow">http://www.nsnam.org/wiki/index.php/NS-3_Python_Bindings#The_semi-automatic_way</a><br>>>
<br>>> I had started to use that gccxml snapshot from september, with
<br>>> pygccxml 1.0, and updated the wiki page, but I guess I forgot to
<br>>> notify the ns-developers list. Sorry about that.
<br>>>
<br>>> No, we cannot stick to old versions. Newer pygccxml does not work
<br>>> well with old gccxml, we have to move forward or we stagnate and
<br>>>
<br>>
<br>> Ok, that might explain some crazy warnings/errors I get on some systems
<br>> I use.
<br>>
<br>>
<br>>> die. I have today updated to gccxml HEAD and it works fine, apart
<br>>> from that bug I reported. I don't like constantly using bleeding
<br>>> edge (you know well how I like things stable), but I think about once
<br>>> a year is reasonable to request that people upgrade their tools, don't
<br>>> you think?
<br>>>
<br>>
<br>> Ok, fair enough for me. However, it would be nice to add a temporary
<br>> hack to nstime.h if we can to make it easier for developers to rescan
<br>> the bindings when needed and remove the hack once the fix is merged in
<br>> gccxml.
<br>>
<br>> Mathieu
<br>>
<br>>
<br>>
</div>I re-enabled python bindings in buildbot automatic builder.
<br>Faker
<br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26409051Re: Packet data replacement2009-11-18T06:42:17Z2009-11-18T06:42:17ZMathieu LacageOn Wed, 2009-11-18 at 15:30 +0100, Florian Schmidt wrote:
<br><div class='shrinkable-quote'><br>> > Taking a step back, I have to confess that I am not sure what you
<br>> expect
<br>> > an error model which corrupts the content of a packet to really do:
<br>> >
<br>> > 1) if you really corrupts the bits inside the packet, the ns-3
<br>> models
<br>> > are likely to stop working because most (all?) of them were written
<br>> with
<br>> > the assumption that this (bit corruption) does not happen so, they
<br>> will
<br>> > read corrupted headers and will fail to work, or worse.
<br>>
<br>> Actually, I did exactly that, and I already ran into a couple of the
<br>> problems you mentioned. :) However, it is not too bad in the end, I
<br>> tweaked a couple of the internet stack Classes, and it's running fine
<br>> now. I want to create some own models looking into the effect of
<br>> actual corruption, potential repair techniques, etc, potentially
<br>> connecting it to a different in-house simulation environment at some
<br>> point.
</div><br>uh, that is pretty scary :)
<div class='shrinkable-quote'><br>>
<br>> > 2) What the ErrorModel class was designed to model is the ability of
<br>> a
<br>> > checksum to detect that a packet is corrupted: it just looks at the
<br>> > packet and decides whether or not your MAC-level checksum detected
<br>> an
<br>> > error without having to calculate a checksum. (Maybe the doxygen for
<br>> the
<br>> > ErrorModel class is misleading)
<br>>
<br>> Yeah, that might very well be. I mean, the standard way I've known
<br>> such error models to work in other simulators are exactly like that:
<br>> set a flag that marks a packets as "containing errors" when the
<br>> modeling has decided there should be an error in the packet. So I was
<br>> pleasantly surprised when I saw the doxygen mentioning that an error
<br>> model could potentially alter the actual packet data. However, I think
<br>> it fits very well with the ns3 approach of representing packets as
<br>> actual data buffers, and not abstract structures (even if that might
<br>> have been done mostly for easier integration with network emulation?).
</div><br>yes.
<br><br>> Of course, implementing such an error model comes with other issues,
<br>> such as the ones you mentioned above.
<br><br>ok.
<br><br><div class='shrinkable-quote'><br>> >> and creation of a new Packet. The main advantage of that solution
<br>> >> would be that whatever possible tags are in the original packet
<br>> would
<br>> >> be kept. I don't think your solution keeps them? Not that I use
<br>> them
<br>> >
<br>> > my second solution would keep them.
<br>>
<br>> Ah right. I didn't really comment too much on that because it seemed
<br>> to me you weren't very happy with that approach.
</div><br>Yes, I am not too happy with it but I don't see any really cleaner
<br>approach: you want to play with my bytes but I don't want to let you get
<br>too close to them.
<br><br>Mathieu
<br><br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26409097Re: Bug #622, fiendly names for pcap files2009-11-18T06:41:48Z2009-11-18T06:41:48ZTom Henderson-2Faker Moatamri wrote:
<div class='shrinkable-quote'><br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26409097&i=0" target="_top" rel="nofollow">craigdo@...</a> wrote:
<br>>> -1
<br>>>
<br>>> I have a problem with it since it only works on csma and point-to-point,
<br>>> adds the same code in two places (making the current code duplication
<br>>> problem worse since it should really go in 6 places to be consistent, I
<br>>> think) and mow makes these two devices behave differently than the others
<br>>> that use pcap.
<br>>>
<br>>> It's simple, but has problems. I have an enhancement in progress ...
<br>>>
<br>>>
<br>> Please take a look also at the bug 683
<br>> (<a href="http://www.nsnam.org/bugzilla/show_bug.cgi?id=683" target="_top" rel="nofollow">http://www.nsnam.org/bugzilla/show_bug.cgi?id=683</a>) which proposes to
<br>> have an explicit name instead of a somehow generated name. This might be
<br>> useful for some users who would need a specific file name for their pcap
<br>> file. Those two patches change the same places in the code and we need
<br>> to decide which one we will keep or if we merge the two patches
<br>> (allowing the user to have explicit file names and friendly file names).
<br>> What do you guys think?
</div><br>(responding for Craig)
<br><br>Craig is working both of these bugs jointly, as you suggest.
<br><br>- Tom
<br><br><br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26408920Re: Packet data replacement2009-11-18T06:30:48Z2009-11-18T06:30:48ZFlorian Schmidt-5<br>On Nov 18, 2009, at 2:59 PM, Mathieu Lacage wrote:
<br><br>> Taking a step back, I have to confess that I am not sure what you expect
<br>> an error model which corrupts the content of a packet to really do:
<br>>
<br>> 1) if you really corrupts the bits inside the packet, the ns-3 models
<br>> are likely to stop working because most (all?) of them were written with
<br>> the assumption that this (bit corruption) does not happen so, they will
<br>> read corrupted headers and will fail to work, or worse.
<br><br>Actually, I did exactly that, and I already ran into a couple of the problems you mentioned. :) However, it is not too bad in the end, I tweaked a couple of the internet stack Classes, and it's running fine now. I want to create some own models looking into the effect of actual corruption, potential repair techniques, etc, potentially connecting it to a different in-house simulation environment at some point.
<br><br><br>> 2) What the ErrorModel class was designed to model is the ability of a
<br>> checksum to detect that a packet is corrupted: it just looks at the
<br>> packet and decides whether or not your MAC-level checksum detected an
<br>> error without having to calculate a checksum. (Maybe the doxygen for the
<br>> ErrorModel class is misleading)
<br><br>Yeah, that might very well be. I mean, the standard way I've known such error models to work in other simulators are exactly like that: set a flag that marks a packets as "containing errors" when the modeling has decided there should be an error in the packet. So I was pleasantly surprised when I saw the doxygen mentioning that an error model could potentially alter the actual packet data. However, I think it fits very well with the ns3 approach of representing packets as actual data buffers, and not abstract structures (even if that might have been done mostly for easier integration with network emulation?). Of course, implementing such an error model comes with other issues, such as the ones you mentioned above.
<br><br><br>>> and creation of a new Packet. The main advantage of that solution
<br>>> would be that whatever possible tags are in the original packet would
<br>>> be kept. I don't think your solution keeps them? Not that I use them
<br>>
<br>> my second solution would keep them.
<br><br>Ah right. I didn't really comment too much on that because it seemed to me you weren't very happy with that approach.
<br><br>Florian
<br><br><br>--
<br>Florian Schmidt, Ph.D. Student
<br>Distributed Systems Group
<br>Chair for Computer Science IV, RWTH Aachen, Germany
<br><a href="http://ds.cs.rwth-aachen.de/members/schmidt" target="_top" rel="nofollow">http://ds.cs.rwth-aachen.de/members/schmidt</a><br><br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26408174setting data rate for ieee802.11p2009-11-18T06:15:07Z2009-11-18T06:15:07ZiimeneHi,
<br><br>Could you please say to me how can I set the data rate for 802.11p
<br><br>Thanks in advance<p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>tag:old.nabble.com,2006:post-26408588help to get output of mac 802.112009-11-18T06:11:31Z2009-11-18T06:11:31ZTritva jyothi kiran<br>Hi
<br><br>i have to compare performance of mac802.11 with 802.11e(QoS) ,
<br>So plz any body tel me what (nam) output i can get when running the
<br>mac802.11 and in what way it consists of...? i am asking these question bcoz
<br>i have minimum knowledge in NS2.
<br><br>reply for this is a great help to me
<br><br>thanks in advance
<br><br>Jyothi Kiran
<br><p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>tag:old.nabble.com,2006:post-26408269Re: Packet data replacement2009-11-18T05:59:04Z2009-11-18T05:59:04ZMathieu LacageOn Wed, 2009-11-18 at 14:35 +0100, Florian Schmidt wrote:
<br><br>> right now. I was just talking from the view point of someone doing a
<br>> large simulation with an error model. In the buffer implementation,
<br>> for example, so much work went into making it very efficient, that it
<br>> just feels like a shame if we made the simulator do an additional copy
<br>> of each and every packet as soon as somebody applies an error model
<br>> (any error model, really, if we changed ErrorModel itself).
<br><br>Taking a step back, I have to confess that I am not sure what you expect
<br>an error model which corrupts the content of a packet to really do:
<br><br>1) if you really corrupts the bits inside the packet, the ns-3 models
<br>are likely to stop working because most (all?) of them were written with
<br>the assumption that this (bit corruption) does not happen so, they will
<br>read corrupted headers and will fail to work, or worse.
<br><br>2) What the ErrorModel class was designed to model is the ability of a
<br>checksum to detect that a packet is corrupted: it just looks at the
<br>packet and decides whether or not your MAC-level checksum detected an
<br>error without having to calculate a checksum. (Maybe the doxygen for the
<br>ErrorModel class is misleading)
<br><br>So, I have to ask now: what exactly are you trying to do ? i.e., what is
<br>the bigger picture, and how do you want to use your ErrorModel ?
<br><br>> Now, I admit I don't have a great solution for that problem either
<br>> right now. My first idea was a method Packet::ReplaceData that would
<br>> take a uint8_t* that contained the altered packet data and overwrite
<br>> the original data with it. But it doesn't feel very clean either.
<br>> Also, it would still be a memcpy, though save the memory allocation
<br>> and creation of a new Packet. The main advantage of that solution
<br>> would be that whatever possible tags are in the original packet would
<br>> be kept. I don't think your solution keeps them? Not that I use them
<br><br>my second solution would keep them.
<br><br>> myself right now, but it would feel weird if your'd just lose your
<br>> tags that way.
<br><br>yes.
<br><br>Mathieu
<br><br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26407942HMIP simulation in ns2009-11-18T05:38:40Z2009-11-18T05:38:40ZMuhammad Wasim<br>Salams,
<br>
<br>I am working with hmip using coloumbia micromobility suite (cims) version for ns-2.31. Do any body know how do i use my own scenario to run hfa?
<br><br>Muhammad Wasim
<br>International Islamic University
<br>Islamabad
<br><br><br> Get your new Email address!
<br>Grab the Email name you've always wanted before someone else does!
<br><a href="http://mail.promotions.yahoo.com/newdomains/aa/" target="_top" rel="nofollow">http://mail.promotions.yahoo.com/newdomains/aa/</a><br><p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>tag:old.nabble.com,2006:post-26407868Re: Packet data replacement2009-11-18T05:35:24Z2009-11-18T05:35:24ZFlorian Schmidt-5<br>On Nov 18, 2009, at 2:07 PM, Mathieu Lacage wrote:
<br><br>> Theoretically, yes, but, the truth is that if you create a
<br>> zero-filled-payload packet and then call PeekData, you trigger a memory
<br>> re-allocation/memcpy deep within Buffer::CreateFullCopy so, if we force
<br>> you to call CopyData, we are merely forcing you to make the hidden
<br>> memory allocation/memcpy explicit.
<br><br>Ah, yes, I got that. This is not my point. This one is though:
<br><br>> Now, I assume that you want to do something like this:
<br>>
<br>> packet->CopyData (m_temporaryErrorBuffer, packet->GetSize ());
<br>> ApplyBitErrorsInBuffer (m_temporaryErrorBuffer, packet->GetSize ());
<br>> p = Create<Packet> (m_temporaryErrorBuffer, packet->GetSize ());
<br>>
<br>> which is one extra memcpy (the one in Create<Packet> ()) compared to the
<br>> raw PeekData version. This is not really optimal, I agree.
<br><br>I can live with it, and I'm not too worried about performance right now. I was just talking from the view point of someone doing a large simulation with an error model. In the buffer implementation, for example, so much work went into making it very efficient, that it just feels like a shame if we made the simulator do an additional copy of each and every packet as soon as somebody applies an error model (any error model, really, if we changed ErrorModel itself).
<br><br>Now, I admit I don't have a great solution for that problem either right now. My first idea was a method Packet::ReplaceData that would take a uint8_t* that contained the altered packet data and overwrite the original data with it. But it doesn't feel very clean either. Also, it would still be a memcpy, though save the memory allocation and creation of a new Packet. The main advantage of that solution would be that whatever possible tags are in the original packet would be kept. I don't think your solution keeps them? Not that I use them myself right now, but it would feel weird if your'd just lose your tags that way.
<br><br>Florian
<br><p>From forum: <a href="http://old.nabble.com/ns-developers-f15584.html" embed="fixTarget[15584]" target="_top" >ns-developers</a></p>tag:old.nabble.com,2006:post-26407556TDMA functioning for Ad hoc Networks2009-11-18T05:15:36Z2009-11-18T05:15:36ZJiji578<br>Hi,
<br><br>I want to modify the TDMA functioning for the Ad hoc networks using NS2.27
<br>by changing the frame length and the number of slots and reserving slots for
<br>some flows.
<br>I tried to change the TDMA frame length or the number of slots in
<br>mac-tdma.cc and mac-tdma.h
<br>but the modification is not taken into account.
<br> Could you help me please.
<br><br>Thank you very much in advance.
<br><p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>tag:old.nabble.com,2006:post-26407426Modifying TDMA functioning for Ad hoc Networks2009-11-18T05:08:19Z2009-11-18T05:08:19ZJiji578Hi,
<br><br>I want to modify the TDMA functioning for the Ad hoc networks using NS2.27 by changing the frame length and the number of slots and reserving slots for some flows.
<br>I tried to change the TDMA frame length or the number of slots in mac-tdma.cc and mac-tdma.h
<br>but the modification is not taken into account.
<br> Could you help me please.
<br><br>Thank you very much in advance.<p>From forum: <a href="http://old.nabble.com/ns-users-f15583.html" embed="fixTarget[15583]" target="_top" >ns-users</a></p>