[Olsr-dev] OLSRd 0.5.4 and 0.5.5 with ETT available

[Hannes Gredler]

Jens Nachtigall wrote:
> Hence, best way to do it is PacketPair atm, at least for a generic routing 
> daemon like olsrd that should be working independent of what's below the IP 
> layer.

if your target OS does not support what *should* be around,
then we could fallback to packet/pairing.

or let me ask the question in a different way:
if one OS in the wireless mesh does not support wireless APIs
and cannot compute 'good' metrics, why should we squash the
rest of the network to that lower limit.

actually i am more in favor of a reflection of this in the metric.

if the target OS can do good airtime estimation (by means of reading
out wireless stats) its offered links should be more attractive
than a link offered by a system that needs to do heuristics.

/hannes