[PATCH 0/2] Enable the batman-adv Gateway selection

[Tom Green]

Wechseln dann alle Clients das GW mit, oder nur die neuen?

Wenn es alle sind, stell mir das so vor, als ob dann ganze Herrscharen
das GW wechseln, auslasten, um dann als Schwarm ein oder zwei Minuten
über das nächste GW herzufallen (und dabei die externe IP zu wechseln,
was mitten im Youtube Video vielleicht nicht so gut kommt).


On 14.09.2015 21:58, Tim Niemeyer wrote:
> This Patchset enables the gateway selection and adds a cron to reset the
> selection every one minute. I didn't find a better way to tell batman to
> look for newer and better gateways.
>
> I tried different gateway selection classes, only class 1 allows us to
> take care of the selection via the announced bandwidth. Unfortunately the
> class 1 stick with the selection until the gateway disappears. Even if a
> much better gateway is announced the node will stay with that gateway. To encounter this behaviour, the cron disables the client mode for one second.
> This will tell batman to make a new evaluation.
>
> Attention: By applying this patches only Hoods with enabled gateway selection
> can serve DHCP to Client.
>
>
> Tim Niemeyer (2):
>   batman-adv: enabled client gateway mode
>   cron: disable every 1min the gw selection for 1s
>
>  bsp/default/root_file_system/etc/config/batman-adv | 4 ++--
>  bsp/default/root_file_system/etc/crontabs/root     | 1 +
>  2 files changed, 3 insertions(+), 2 deletions(-)
>