Re: [ns] make clean, make depend, make do not take effect
Hi, try "make clean", "make", "sudo make install" from /ns-whatever/ns-2.31 directory Filip >Hi, >Here are my two cents, perhaps one of the following could be the problem: > >1. Perhaps you are not executing the make/make clean commands in the right >directory, you have to do it >in /ns-whatever/ns-2.31 directory or >2. You are not calling the right protocol in your tcl script file e.g. you >made some changes in TORA.cc but > you are calling AODV in your tcl script file. > >Hope that helps. > > >- Original Message >From: bilge kartal <[EMAIL PROTECTED]> >To: minisivakumar vellore <[EMAIL PROTECTED]> >Cc: ns-users@ISI.EDU >Sent: Friday, October 26, 2007 10:46:37 AM >Subject: Re: [ns] make clean, make depend, make do not take effect > > >Hi, > >I had same problem before. I m using same version but under XP via Cygwin. I >m not sure this help. >you should be under the ns-2.31 directory. And then > >./configure >./make clean >./make > >Good luck > >Bilge > >On 10/25/07, minisivakumar vellore <[EMAIL PROTECTED]> wrote: >> >> >> Hi all >> I am using ns-2.31 under linux environment. >> I made some changes to .cc files in the ns2 directory (introduced or >> remove= >> d some printf statements). >> But my changes do not take effect at all. >> I've tried the following >> (i) make clean, make depend, make >> (ii) make distclean, ./configure, make >> (iii) make clean, ./install, ./configure, make >> (iv) make distclean, ./install (then setting the library paths again), >> ./co= >> nfigure, make >> >> I run my tcl script by giving the command as ./ns xxx.tcl >> I am not sure why my changes don't take effect. If someone has any >> pointers= >> please let me know. >> >> PS: I do not get any errors for any of the commands. >> >> _ >> Are you ready for Windows Live Messenger Beta 8.5 ? Get the latest for >> free today! >> http://entertainment.sympatico.msn.ca/WindowsLiveMessenger >> > >__ >Do You Yahoo!? >Tired of spam? Yahoo! Mail has the best spam protection around >http://mail.yahoo.com >
Re: [ns] Could not schedule timer
>This query has been posted in past also but my search for the >solutions was unsuccessful: > >When I run my NS script with heavy traffic, the execution sometimes >stop in between giving the error as "Couldn't schedule timer". I am >also using my own timer for acknowledgement timeout. > >Does this refer to the internal timer or my own defined timer? It seems that this is the internal timer (common/timer-handler.cc), unless you fprint the same text with your own timer. Make sure by e.g. editing the line fprintf(stderr,"Couldn't schedule timer"); in common/timer-handler.cc to fprintf(stderr,"Couldn't schedule timer from timer-handler.cc"); Then recompile ns-2, reinstall it, and run your tcl script. If the text that ns-2 prints out matches your changes in common/timer-handler.cc, then you know which timer this text refers to. >How can I avoid this error? It seems that your ns-2 sets the timer to idle state somewhere. Try to check where it does it. >Tarun Regards, Filip
[ns] How to classify packets in a node using fid?
Hi All, I would like to route packets using their flow ids. I tried to use the Hash/Fid classifier (implemented a new Routing Module, following the ns-manual), but didn't manage to make it classify packets. I believe, I am missing some ns-2 commands. As an example, I am using the following network: 5 3 - 4 \ / \ 2 0 / \ / 6 1--- and want, that packets from node 5 to node 0 go via 3 and 4, and packets from node 6 to node 0 go via node 1. Do you know, how to implement it? And also, how to influence/check the routing table? I would be grateful for hints. Kind regards, Filip
[ns] How to implement circuit-switching in ns-2?
Hi, I've been trying to implement a circuit-switched network model using ns-2 for some time. I have the following ideas: - use manual routing and separate queues for each flow - add path information to a packet payload - lay more links between a node pair - create separate links and nodes for every circuit path - implement source routing - implement GMPLS/WDM, and base on labels/wavelengths (OWNS extension) Unfortunately, none of these has been successful to me so far. Does anybody have any experience, ideas, hints connected with circuit-switching in ns -2? I would appreciate every information. Thanks a lot in advance! Filip
[ns] How to implement circuit-switching in ns-2?
Hi, I've been trying to implement a circuit-switched network model using ns-2 for some time. I have the following ideas: - use manual routing and separate queues for each flow - add path information to a packet payload - lay more links between a node pair - implement source routing - implement GMPLS/WDM, and base on labels/wavelengths I managed to introduce manual routing for a packet switched-network (add-route command), but I got stuck by defining separate queues for each flow in the first approach. The second approach seems less elegant to me, and I don't know how to add any information to the payload. When I tried the third idea, ns-2 saw just a single link between a node pair, even though there were more links created (using command $ns duplex-link $n($i) $n($j) 1Mb 10ms DropTail but I wouldn't know, how I could refer to each link, as a link doesn't have its name...) Source routing seems to be an interesting approach, but I would still need to define separate queues for each flow... As for GMPLS, WDM, I am aware, that a WDM extension is available for ns (http://dawn.cs.umbc.edu/owns/), but it is not updated any more, and I am not sure if it works with current and with future releases of ns-2. I searched the whole mailing list for GMPLS and WDM, but I didn't find any clear solution for a WDM or GMPLS network. I searched the ns mailing list also for circuit switching, and saw that some people managed to implement circuit-switching, but there is no information on how to do it. Could you please give me some hints on how to implement one of the ideas I presented above, or maybe on a completely another idea? Simply, how to implement circuit-switching in ns-2? Thanks a lot in advance! Filip
