[Olsr-dev] [PATCH v3 1/1] smart gateway: add threshold configuration parameter

[Ferry Huberts]

On 12/14/2011 11:03 AM, Markus Kittenberger wrote:
> btw nice SGW gets finally tested/debugged/fixed,..
> 
> and ACK, i would not really consider SGW as "very" stable in olsrd,..
> but ...
> 
> On Tue, Dec 13, 2011 at 10:31 AM, Ferry Huberts <(spam-protected)
> <mailto:(spam-protected)>> wrote:
> how about changing the default to 67 percent for the threshold?
> 
>     we would really like to change that.
> 
> 
> ... afair the main idea/reasoning for SmartGateways in first place, was
> to provide a solution for users suffering from changing gateways (which
> are doing NAT), leading to changing "public" ips.
> (i.e the same issue Nat-Threshold was aimed at, but ...)
> 
> or are there new (widely/predominantly used) SGW usecases, i am not
> aware of?
> 

we have _highly_ mobile adhoc networks (e.g. vehicles driving around).
therefore we'd like to always choose the best gateway (with some obvious
hysteresis/delay)


> imho the "only" behaviour matching the original goal, is to change the
> gateway only if the old one ist lost (or maybe got extremely bad/costly),.. 
> i.e. 0 (or a very low value) would be the "correct" default for the
> SGW-Threshold
> 
> but imho 0.67 is not!
> as it might even cause switching between gateways every some minutes in
> some spots in some networks,..
> 

in a static setup (like in a city) this should not cause switching under
normal circumstances, while enabling the highly mobile case to function
per default as well. win-win


-- 
Ferry Huberts