create your links as follows:
$ns duplex-link $CN_($i) $W(1) 10Mb $delay_links DropTail right-down
< or left, or right, etc
standard request follows:
now that you have your problem solved, please describe the problem and the
solution in the NS2 wiki, __in your own words__, to help the next NS2 users
that has a similar problem.
Thanks :-)
Pedro Vale Estrela
Hello Pedro,
Thank you for the help...that was everything i needed.
Just one more thing if you can help medo you know if it is possible to
load a previously saved layout of my topology in NAM?
Best Regards,
On 7/3/06, Pedro Vale Estrela <[EMAIL PROTECTED]> wrote:
http://tagus.inesc-id.pt/~pestrela/ns2/ns2_haddr_tips.html
Type of Addresses that a node can have in NS2 (hAddr, ID, iAddr, Handle)?
In NS2, a node can be uniquely identified by several forms
the "handle" is the otcl name; it refers to an object of the form "_oXXX",
and because of this, it is the only form can be used to directly call
internal instprocs and variables.
the "haddr" is the Hierarchical address, on the form " X.Y.Z"
the "iaddr" is the INTEGER hierarchical address, where the haddr string is
simply ENCODED in a 32 bit integer.
the "id" is the sequential Node ID of the simulator.
...
In my ns2_shared_procs.tcl "utils" tcl file, I introduce procs for all
possible conversions of each form, using the procs "handle2iaddr",
"handle2haddr", "handle2id", etc.
http://tagus.inesc-id.pt/~pestrela/ns2/files/ns2_shared_procs.tcl
Feel free to ask further questions if necessary
Pedro Vale Estrela
> I am currently implementing a routing algorithm in NS2. I have utilized
> the
> command [$node neighbors] for discovering the neighbors of a specific
> node.
>
> This command returns a list with the following three elements (_o13, _o16,
> _019). Is is possible in TCL to retrieve dynamically the ID of each node
> using this elements in the list.
>
> For example:
>
> _o19 = n(1)
> _o13 = n (0)
> _o16 = n(2)