[CUWiN-Dev] question about HSLS

[Bill Comisky]

On Tue, Mar 10, 2009 at 4:49 AM, 임영빈 <ovinee at gmail.com> wrote:

> Hello
> I'm testing HSLS routing protocol on my mesh testbed.
> What I want to do is to bring etx values from hslsd. So using -R option
> hslsd dumps routing table periodically.
> Following is an example.
>
> 10.0.154.123/32 nexthop 10.0.154.123, ath0, gen 8, [(etx, 0), (hopcount,
> 0), (backplane-hopcount, 0), (network-radius, 0)]
> 10.0.186.28/32 nexthop 10.0.186.28, ath0, gen 8, [(etx, 65535), (hopcount,
> 1), (backplane-hopcount, 0), (network-radius, 1)]
> 10.0.186.60/32 nexthop 10.0.186.60, ath0, gen 8, [(etx, 65535), (hopcount,
> 1), (backplane-hopcount, 0), (network-radius, 1)]
>
> The problem is that the etx value for one hop neighbor is always 65535
> which is not reasonable.
> Even after a long time, it does not change.
>
> I couldn't find the version of hslsd, but my main.c code shows some
> information about the version.
> $Id: main.c 4756 2007-08-04 06:36:38Z dyoung
> I run hslsd with this command.
> hslsd -f inet -t ptmp -i ath0 -m -M etx,hopcount -R /home/root/hsls_out
>
> Is there any option needed to get the actual etx values, or am I missing
> something?
>

Try dumping the link-states; via the README:

-o viz-dumpfile tells hslsd where to dump link-states in the viz
>    format when it receives a SIGUSR2 signal (also, dump them
>    periodically)
>
> -O ls-dumpfile tells hslsd where to dump link-states in their
>    "native" ASCII format when it receives a SIGUSR2 signal (also,
>    dump them periodically)
>

 Bill

-- 
Bill Comisky
bcomisky at pobox.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.chambana.net/mailman/archive/cu-wireless-dev/attachments/20090310/ce9a3ede/attachment.htm