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

Markus Kittenberger (spam-protected)
Wed Dec 14 23:26:52 CET 2011

On Wed, Dec 14, 2011 at 8:28 PM, Teco Boot <(spam-protected)> wrote:

> i asume trying to have a default value that really suits highly mobile and
> static city-meshes is impossible,..
> What about trying to be smart: when candidate is far better than current,
> change fast (but not to fast). So we count the elections of a better
> candidate, and switch based on better path and duration it is the best.

no bad idea (if i got it right), but might need more parameters to define
this smartness,..

e.g. a slow and a (lower) fast-SGW-Threshold
and a slow-SGW-Threshold-duration value,..

and if a new gateway is fast-SGW-thresh better olsrd should switch
but if new gateway is only by slow-SGW-thresh better, olsrd shoudl switch
only after it is/was always better for a full slow-SGW-Threshold-duration,..

but such smart/configuration/code "heavy" stuff, should imho really be a

> 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)
> So new long lifetime connections take 2nd best path, or worse?
yes, but at least they can live long,.. (-;

> I didn't try conntrack for this, but what is wrong with it? (other than
> make it happen...)
olsrd currently does not need a patched kernel, for any of its features
(which is great!)

but having conntrack and SGW (and routing) work seemless together would!
(or at least i have no idea to make it happen without kernel modifications)

> With IPv6
, traffic classification could be based on source address prefix mapping to
> corresponding exit link. IETF Homenet workgroup is looking for such. Having
> it, SmartGateway would get deprecated, as all routers forward to right
> border and no NAT is in use. And no connection state at all in routers. No
> encap, no MTU problems. And my favorite: multi-path.

btw some if not all of this could already be done with ipv4 too (-;
 (if one happen to have enough adresses)

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

More information about the Olsr-dev mailing list