[Olsr-users] OLSR configuration for mobility.
Tue Aug 25 21:36:15 CEST 2015
On Tue, Aug 25, 2015 at 9:31 PM, Dan O'Keeffe <(spam-protected)> wrote:
>> OLSRv2 includes the link speed into its metrics, OLSRv1 does not.
> By link speed do you mean something like ETT? Do you have a
> reference/link describing how OLSRv2 incorporates link speed, and the
> benefits over just using ETX?
>> The most common change would be to reduce the Hello/TC intervals...
>> validity time could also be reduced, but the interval is more
> OK, thanks. Out of interest, does OLSRd (or a plugin) by any chance
> report any statistics about how stable the network is, i.e. what
> proportion of the time it converged?
There is no real convergence time in link-state, its more a matter of
how likely you receive a TC from everyone else because of "topology
redundancy vs. packet loss".
But yes, both Olsrd and Olsrd2 have plugins to report about their
For olsrd its "txtinfo" or "jsoninfo".
Olsrd2 uses "nhdpinfo" for reporting on the neighborhood discovery,
"olsrv2info" for information about the routing and "layer2info" for
looking at the layer-2 knowledge of the routing agent. All three can
be accessed by the same port (olsrd2 has a generic telnet interface).
>> Oh, with CORE/EMANE the link-speed detection of Olsrd2 will not work
>> because there is no Wifi-card to query.
> OK. When you say it won't work, will it fall back to something like ETX,
> or will OLSRv2 just not work at all in emulation?
The packet loss estimator will work fine... the link speed would need
to be configured by hand... or you would have to write a plugin to
take the data from EMANE and put it into the layer2-database within
More information about the Olsr-users