[Olsr-users] [Olsr-dev] Configuring TC redundancy parameter?

chris - (spam-protected)
Thu May 9 03:36:49 CEST 2013

Saverio, that's helpful advice. I also was able to look up how these two
algorithms work. One thing: is there a parameter for hop cost?


On Wed, May 8, 2013 at 12:29 AM, Saverio Proto <(spam-protected)> wrote:

> > (1) We were thinking it would be reasonable in our network to use only
> > signal level in path length calculations. Our main problem is that
> fewer-hop
> > paths are preferred, even if they use a weak, geographically-separated
> link.
> > This results in enormous losses for us. Is this tunable or does it
> require a
> > rewrite? I've notice that ETX has become the default link-sensing metric.
> Hello,
> we have similar problems in Ninux
> we use:
> LinkQualityAlgorithm    "etx_float"    (instead of etx_ff)
> LinkQualityAging 0.02     (that is used only with etx_float)
> and then on the weak geographically-separated link we configure
> LinkQualityMult 0.3
> Saverio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20130508/446afa49/attachment.html>

More information about the Olsr-users mailing list