[Olsr-dev] [Olsr-users] Question on NatThreshold config parameter
Thu Jan 3 08:29:07 CET 2013
NatThreshold is not a complete solution. Each node has its own actual threshold. Therefore, loops may occur. SmartGateway is also a hack, but much cleaner.
Updated SmartGateway makes smarter decisions, selecting gateway based on ETX to exit node and exit link metric. It also uses best gateway for each new connection, the gateway is selected during setup of the connection.
@Saverio: was it NatThreshold with 0.5 or etx_float? Isn't 0.5 a bit to extreme?
Op 2 jan. 2013, om 20:33 heeft Henning Rogge het volgende geschreven:
> We really need some "record raw link data" systems, so we can analyze
> what the hell is going on with certain links.
> That would allow us to work on better link metrics with some kind of
> "sanity tests". :)
> Hope DLEP will do this job in 2013.
> On Wed, Jan 2, 2013 at 1:29 PM, Saverio Proto <(spam-protected)> wrote:
>> We fixed this issue, so here our feedback.
>> We used NatThreshold with etx_float. The use the value of 0.5
>> It fixed completely our problema and it works great with etx_float.
>> 2012/12/29 Saverio Proto <(spam-protected)>:
>>> I have a node suffering from default route flapping because there are
>>> actually two gateways with similar costs few hops away in different
>>> I would like to know if NatThreshold is implemented only with etx_ff
>>> or if the feature can be used with other link quality algorthms like
>>> One last question: If I have nodes in my network configured with
>>> different values of NatThreshold I guess this might cause routing
>>> loops for traffic routed via the default route, is that correct ?
>> Olsr-dev mailing list
> Steven Hawkings about cosmic inflation: "An increase of billions of
> billions of percent in a tiny fraction of a second. Of course, that
> was before the present government."
> Olsr-users mailing list
More information about the Olsr-dev