[Olsr-dev] getting the etx value to a destination

Henning Rogge (spam-protected)
Wed Jul 15 17:22:10 CEST 2009

Am Mittwoch 15 Juli 2009 17:13:10 schrieb ZioPRoTo (Saverio Proto):
> >> So to get the ETX I divide this value by 2^16 ??
> >
> > Yes, this values make sense... but you SHOULD NOT assume that "65536" is
> > "good", because it depends on your routing metric.
> OK ! So if the metric is ETX is it okay to divide by 2^16 ?
Just forget about ETX... you don't need it.

There is a function to convert the link cost back into the text representation 
(depending on the plugin) in lq_plugin.c:

const char *
get_linkcost_text(olsr_linkcost cost, bool route, struct lqtextbuffer *buffer)

use this if you want to output the "human readable" linkcost.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20090715/68f242df/attachment.sig>

More information about the Olsr-dev mailing list