From bart.braem at ua.ac.be  Thu Feb 10 03:22:41 2005
From: bart.braem at ua.ac.be (Bart Braem)
Date: Thu Feb 10 06:09:39 2005
Subject: [nsclick-users] No element activity until data streams?
Message-ID: <200502101122.42380.bart.braem@ua.ac.be>

Hello,

I've noticed something strange: an element does not become active until data 
is sent in the network?
I'm doing an implementation of AODV in nsclick. Each AODV node periodically 
sends out HELLO messages. But to my surprise that generation does not happen 
until the first ns data streams pass through the network. 
Is there any explanation why? I'd like to have my network to have handled some 
HELLO traffic before handling data streams...

Greetings,
Bart
From Michael.Neufeld at colorado.edu  Thu Feb 10 08:51:42 2005
From: Michael.Neufeld at colorado.edu (Michael Neufeld)
Date: Thu Feb 10 08:52:19 2005
Subject: [nsclick-users] No element activity until data streams?
In-Reply-To: <200502101122.42380.bart.braem@ua.ac.be>
References: <200502101122.42380.bart.braem@ua.ac.be>
Message-ID: <420B830E.2030106@colorado.edu>

I've seen this happen sometimes -- perhaps the problem is related to this:

http://cs-lists.cs.colorado.edu/pipermail/nsclick-users/2003-March/000021.html

The "runclick" command should be in the current nsclick patchset, I 
honestly can't recall if I ever got around to automatically adding a 
call to it. Anyhow, you might try adding the chunk of tcl code like that 
suggested in the message:

for {set i 0} {$i < $nodecount} {incr i} {
      $ns_ at 0 "[$node_($i) entry] runclick"
}

and see if it helps. If not, let me know.

-Mike

Bart Braem wrote:
> Hello,
> 
> I've noticed something strange: an element does not become active until data 
> is sent in the network?
> I'm doing an implementation of AODV in nsclick. Each AODV node periodically 
> sends out HELLO messages. But to my surprise that generation does not happen 
> until the first ns data streams pass through the network. 
> Is there any explanation why? I'd like to have my network to have handled some 
> HELLO traffic before handling data streams...
> 
> Greetings,
> Bart
> _______________________________________________
> nsclick-users mailing list
> nsclick-users@cs-lists.cs.colorado.edu
> http://cs-lists.cs.colorado.edu/mailman/listinfo/nsclick-users
> 
From bart.braem at ua.ac.be  Fri Feb 11 02:45:53 2005
From: bart.braem at ua.ac.be (Bart Braem)
Date: Fri Feb 11 02:46:23 2005
Subject: [nsclick-users] No element activity until data streams?
In-Reply-To: <A4E682B8A936374A9190A3A0FEE412F225D2D7@xmail10.ad.ua.ac.be>
References: <A4E682B8A936374A9190A3A0FEE412F225D2D7@xmail10.ad.ua.ac.be>
Message-ID: <200502111045.53163.bart.braem@ua.ac.be>

> The "runclick" command should be in the current nsclick patchset, I
> honestly can't recall if I ever got around to automatically adding a
> call to it. Anyhow, you might try adding the chunk of tcl code like that
> suggested in the message:
>
> for {set i 0} {$i < $nodecount} {incr i} {
>       $ns_ at 0 "[$node_($i) entry] runclick"
> }
>
That works, great! Perhaps a usefull addition to the nsclick manual?

Thanks for your help
Bart