Question on NatThreshold config parameter

[Saverio Proto]

Hello,

I have a node suffering from default route flapping because there are
actually two gateways with similar costs few hops away in different
directions.

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
etx_float.

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 ?

thanks

Saverio

[Ferry Huberts]

Post by Saverio Proto
Hello,
I have a node suffering from default route flapping because there are
actually two gateways with similar costs few hops away in different
directions.
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
etx_float.
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 ?
thanks
Saverio

I did some major work on the smart gateway functionality, which is all
present in the release-0.6.5 branch that we're going to release in the
next few days.

Maybe you can use some of the following settings:

(from the 'full config' file)

Post by Saverio Proto
# When another gateway than the current one has a cost of less than the cost
# of the current gateway multiplied by SmartGatewayThreshold then the smart
# gateway is switched to the other gateway. The unit is percentage.
# (defaults to 0)
# SmartGatewayThreshold 0
# The weighing factor for the gateway uplink bandwidth (exit link, uplink).
# See README-Olsr-Extensions for a description of smart gateways.
# (default is 1)
# SmartGatewayWeightExitLinkUp 1
# The weighing factor for the gateway downlink bandwidth (exit link, downlink).
# See README-Olsr-Extensions for a description of smart gateways.
# (default is 1)
# SmartGatewayWeightExitLinkDown 1
# The weighing factor for the ETX costs.
# See README-Olsr-Extensions for a description of smart gateways.
# (default is 1)
# SmartGatewayWeightEtx 1
# The divider for the ETX costs.
# See README-Olsr-Extensions for a description of smart gateways.
# (default is 0)
# SmartGatewayDividerEtx 0

[Saverio Proto]

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.

Thanks

Saverio

Post by Saverio Proto
Hello,
I have a node suffering from default route flapping because there are
actually two gateways with similar costs few hops away in different
directions.
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
etx_float.
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 ?
thanks
Saverio

[Henning Rogge]

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.

Henning

Post by Saverio Proto
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.
Thanks
Saverio

Post by Saverio Proto
Hello,
I have a node suffering from default route flapping because there are
actually two gateways with similar costs few hops away in different
directions.
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
etx_float.
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 ?
thanks
Saverio

--
Olsr-dev mailing list
https://lists.olsr.org/mailman/listinfo/olsr-dev

[Teco Boot]

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?

Teco

Post by Henning Rogge
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.
Henning

Post by Saverio Proto
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.
Thanks
Saverio

Post by Saverio Proto
Hello,
I have a node suffering from default route flapping because there are
actually two gateways with similar costs few hops away in different
directions.
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
etx_float.
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 ?
thanks
Saverio

--
Olsr-dev mailing list
https://lists.olsr.org/mailman/listinfo/olsr-dev

--
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
https://lists.olsr.org/mailman/listinfo/olsr-users