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

[Markus Kittenberger]

On Wed, Dec 14, 2011 at 11:52 AM, Teco Boot <(spam-protected)> wrote:

> A default of 1.0 is bad: flapping NAPT and broken connections.
> A default of 0.0 is bad: stick to SGW with bad path: lousy
> (thus broken) connectivity.
> So we have to pick something in between.
>
ACK

i guess i am fine with anything in the 0.25 to 0.5 range (-;

>
> I used NATthreshold 0.9. This was already loopy.

yep nat-theshold is nearly worthless,..

btw what about "deprecating" it?

@Ferry

i asume trying to have a default value that really suits highly mobile and
static city-meshes is impossible,..

(but ACK 0 id definitely not the answer, as its an extreme, that i guess
only very seldomly will be used (if its not the default anymmore))
but it s a configuration parameter, i.e. changeable (-;

and smartgateway allows it to be changed on a per user/node basis without
negative side effects for others,..

so the default just needs to be somewhat sane, .. (even for mobile users)
therefore i prefer to keep leaning towards the original (nearly change
ever) behaviour, and set e.g. 0.33 as default,..

btw. in theory on node could in future also have multiple (differently
configured/used) tunnels, ..

e.g. to seperate between stable gateways for long lasting connections that
should no change gateway, and other traffic classes where it does not hurt
much to change gateways, and additinoal maybe even use no tunnel (and
always the nearest gateway) for some traffic for example  dns or ntp
requests

(and this needs no conntrack support to realize, just some simple traffic
classification, and anhancements to olsrd to maintain/configure multiple
SGW tunnels)

Markus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20111214/8909c537/attachment.html>