[Olsr-users] OLSR setup with VPN interface for management

[Rogge Henning]

There is no upper bound for the ETX value... there is only an lower bound
for LQ and NLQ. If one of them drops below 0.1, the link is considered
broken.

Henning Rogge

--
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für 
Kommunikation, Informationsverarbeitung und Ergonomie FKIE 
Kommunikationssysteme (KOM) Neuenahrer Straße 20, 53343 Wachtberg, 
Germany Telefon +49 228 9435-961,   Fax +49 228 9435 685 
mailto:(spam-protected) http://www.fkie.fraunhofer.de
GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0 

> -----Ursprüngliche Nachricht-----
> Von: (spam-protected) 
> [mailto:(spam-protected)] Im Auftrag von 
> ZioPRoTo (Saverio Proto)
> Gesendet: Montag, 24. Januar 2011 13:37
> An: Markus Kittenberger
> Cc: contatti; Olsr-users
> Betreff: Re: [Olsr-users] OLSR setup with VPN interface for management
> 
> > just do not use 0.1, use at least 0.11 *G
> >
> > as every link with lq or nlq <0.1 is not used by olsrd for 
> routing anymore.
> > that means a single lost packet (e.g. ETX 0.99 * 0.1) stops 
> olsrd from 
> > using your vpn link for some minutes,..
> 
> Actually 0.99 * 0.1 would lead to ETX 10.10
> 
> We have links working with ETX > 100 removing 
> LinkQualityAlgorithm "etx_fpm" !
> The ETX gets so big because the multiplier is always on both 
> edges of the links.
> 
> what is the upper bound of ETX usable to insert a route in 
> the routing table ?
> 
> Saverio
> 
> --
> Olsr-users mailing list
> (spam-protected)
> http://lists.olsr.org/mailman/listinfo/olsr-users
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7095 bytes
Desc: not available
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20110124/0e0d31ce/attachment.bin>