Hi Juan,
Comment out the following line in 'aodv.h' and recompile.
#define AODV_LINK_LAYER_DETECTION
Regards,
fran
On Wednesday 17 May 2006 18:26, juan manuel gomez garcia wrote:
Why I can't see the hello messages?.
I put the next code :
fprintf(stdout,helloo\n);
Hello,
i am new to ns-2 and would like to install
ns-2.1b9a over macosx-10.4.6. Any one is having a
complete patch to install ns-2.1b9a over macox? Please
do send me the patch. Thanks a lot.
Ps: I have gone through the mailing list and tried 2/3
patches, couldn't work for me.
Regs
Has anyone simulated a mobile node using only send/receive functions with
ns-2?
Is it absolutely necessary to have separate Routing/MAC/Transport layers to
use ns-2?
Thanks,
Jeff S.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of [EMAIL PROTECTED]
Dear Qihe,
I did exactly as you describe below when I got the error message. To be
sure, I did it one more time just now with the same result:
...
/home/alexh/ns-2/ns-allinone-2.29/tk8.4.11/unix/../generic/tk3d.c:334: warning:
control reaches end of non-void function
make: *** [tk3d.o] Error
Hi all,
I'm currently trying to extend the AODV routing protocol to have a
'behaviour object' associated with a node's routing agent. (normal,
malicious or selfish for example) I thought the best and most extensible
way of going about this was to write a new class (Behaviour) which can
then be
Hmmm...
The return value of create is *TclObject and the function returns a new
Behavior object. But Behaviour does not inherit from TclObject -
therefore, it can not be converted!
I don't have my compiler handy right now but I'd say that Behaviour
should inherit from TclObject and you
Hi
I'm working on a wireless topology and NS-2.29 (configure in linux) for my
research work. When I try to simulate a bidirectionnal communication between a
wireless endpoint and a wireline endpoint with 11 Mbps and smalls packets (size
200 bytes), I'm getting this error:
Scheduler: Event
Question 1:
Scheduler:: Event UID not valid!
Answer:
Each event in NS2 has a unique UID. The scheduler toggles the UID twice,
once during dispatching and once during scheduling. Thus, the event has a
positive UID