[Click] Using nsclick

[Michael Voorhaen]

Hi Jens,

Jens Mueller wrote:

>Hi Michael,
>
>  
>
>>after
>>
>>[$node_(0) entry] loadclick "access-point.nsclick"
>>[$node_(1) entry] loadclick "station.nsclick"
>>
>>add something like:
>>
>>for {set i 0} {$i < $nodecount} {incr i} {
>>   $ns_ at 0.0 "[$node_($i) entry] runclick"
>>}
>>
>>This forces the click node to start, else no click code is executed 
>>until the first data packet is sent to click.
>>
>>I'm pretty sure that this will fix your problem.
>>    
>>
>
>I added your snippet. BTW did you know any other resources for using
>nsclick despite the ones found on
>http://systems.cs.colorado.edu/Networking/nsclick/? 
>
Not really, I managed to learn most of what I know on my own in the last 
year.

>Your snippet saves
>me from attaching Agents and Applications to the ClickNodes, which is
>quite helpful. But it doesn't solve the problem. I changed the order of
>nodes:
>
>[$node_(0) entry] loadclick "access-point.nsclick"
>[$node_(1) entry] loadclick "station.nsclick"
>to
>[$node_(1) entry] loadclick "access-point.nsclick"
>[$node_(0) entry] loadclick "station.nsclick"
>
>And now the access point won't receive any packets from SimDevice. Do
>you have a clue about this symptom?
>  
>
I don't see any obvious problems. Perhaps it has something to do with 
the prism2decap that you are using in the station script and not in the 
AP script. I'm not that familiar with the wireless extensions.

Michael

>Bye,
>Jens
>_______________________________________________
>click mailing list
>click at amsterdam.lcs.mit.edu
>https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>  
>