Hi,
There is nothing wrong with that address, it's the integer representation of a
hierarchical address. You can find more info in the ns2 Manual.
Maybe you was expecting the node identifier to appear instead of that address.
If you're interested in changing the tracing, this piece of C++ code may be
useful for you:
Node* node = Node::get_node_by_address(addr);
if (node != NULL)
return node->nodeid();
Regards,
fran
On Wednesday 05 April 2006 13:51, Mohammad Abdul Awal wrote:
> Hi OLSR experts,
>
> I am trying to use Hierarchical routing for OLSR in NS2.
> At first, I installed the OOLSR from developed in INRIA.
>
> Some part of my script is as follows:
>
> set val(nn) 10 ;# nb mobiles
>
> $ns node-config -addressType hierarchical
> AddrParams set domain_num_ 2
> lappend cluster_num 1 1
> AddrParams set cluster_num_ $cluster_num
> lappend eilastlevel 10 10
> AddrParams set nodes_num_ $eilastlevel
>
> for {set i 0} {$i < [expr $val(nn)/2]} {incr i} {
> set node($i) [$ns node 0.0.$i]
> }
>
> for {set i 5} {$i < $val(nn)} {incr i} {
> set node($i) [$ns node 1.0.[expr $i-5]]
> }
>
> When I run the simulation, it work fine. But the address of the node shows
> like 4194308.
>
> Sample trace below.
>
> s -t 0.000000000 -Hs 0 -Hd -2 -Ni 0 -Nx 0.00 -Ny 400.00 -Nz 0.00 -Ne
> -1.000000 -Nl AGT -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 0.0 -Id 4194308.0 -It
> cbr -Il 128 -If 0 -Ii 0 -Iv 32 -Pn cbr -Pi 0 -Pf 0 -Po 0
>
> Then I tried with UM-OLSR too. That also shows the same thing. Could you
> please give some hints why it happens like this.
>
> Regards,
> Abdul Awal.
