I'd recommend reading the ns-lib.tcl script through a few times. I added a lot of 'puts' lines in there to try and figure out what was going on. The next thing I did was add some text to each 'event' that the scheduler processed. I printed out the text and UID to get an idea of who was making what event, and why. That really helped.
I'm debugging the application using Sun Java based Eclipse on Ubuntu Linux running under a free version of VMWare. That is working well, but it is slow. As for routing, I'd recommend finding the article "Implementing MANET Routing Protocols in ns2 <http://ants.dif.um.es/masimum/nsrt-howto/html/nsrt-howto.html>". I think the site it used to be at is gone. You might need to search around the web some to find it. What I don't get the hierarchical addressing, and how it figures out what connection to send what packet. My protocol keeps picking wireless, and not wired. Faisal Siddiqui wrote: > > I totally agree with you. I have spent so much time trying to > understand as to how does the simulation flows through the source > code, but can't really make any headways anymore. I am trying to > implement a new control flow mechanism where no packet are dropped, > but in order to do so I have read the queue size of the next hop so > that the current node can decide whether to accept any more packets > from other nodes or flag its exception indicatiing to all other nodes > feeding into it to stop sending more packets to it. I am really stuck > right now because I can't locate where in the source code does the > current node find its next hop address and how does it find that out. > I have bunch of more questions like how does the node and agents are > located to each other because nodes don't store any information > regarding agents or classifiers within them and vice-versa. > > I am still waiting if someone could lend some insight into it. Please > let me know if you have any comments or if you find any help.
