Hello Devu, I think that the change is ok. The reason is that you should be able to still use the previous scripts, and that's why we keep the original code; note that in that sense you are using another command, because the number of parameters is different (from the if-queue originally used by AODV and the one which you need to use).
It would be possible also to add this code within the aodvonly condition, but then the extension could be only applied to this routing protocol. Anyhow, do you have any compile or execution error with this? Cheers, Ramón At 23:50 25/05/2007, Devu ManikantanShila wrote: >---------- Forwarded message ---------- >From: Devu ManikantanShila <[EMAIL PROTECTED]> >Date: May 25, 2007 4:46 PM >Subject: Multiple Interfaces in AODV [based on Ramon] >To: [email protected] > > > >Hello, > >I am simulating multiple interfaces according to Ramon's tutorial in AODV. >I have highlighted the problem in the document!! > ># Special processing for AODV > >MY DOUBT HERE. Should I change the $agent if-queue [$self set ifq_(0)] so as >to simulate multiple interfaces in AODV > >set aodvonly [string first "AODV" [$agent info class]] > >if {$aodvonly != -1 } { > >$agent if-queue [$self set ifq_(0)] ;# ifq between LL and MAC > >} > >THEY HAVE CHANGED ONLY HERE!!! > >if { $port == [Node set rtagent_port_] } { > >*# Special Processing when multiple interfaces are suported* > >*if {$numIfsSimulator != ""} {* > >*for {set i 0} {$i < [$self set nifs_]} {incr i} {* > >*$agent if-queue $i [$self set ifq_($i)]* > >*}* > >*} * > ># Ad hoc routing agent setup needs special handling > >$self add-target-rtagent $agent $port > >return > >} > > > >PLEASE HELP ME!!! > >Thanks > >Devu
