Re: [B.A.T.M.A.N.] Node keeps switching back and forth

[Marek Lindner <lindner_marek@yahoo.de>]

> As soon as signal from node2 to node1 goes down from let's say 250 to
> 240, if another connection to the gateway's quality is 241, it'll
> switch as soon as it hits 240... Then when quality comes back up to
> 242, it switches back to node1.
>
> I don't think it's very good to switch as soon as the quality is
> higher somewhere else, it should at least "give it a chance" by either
> having a threshold, or switch only if it's been in a more degraded
> state for more than x minutes, etc.
>
> Is there something I can do to influence that? Did I miss a command
> line argument?

You can use e.g. "-r 20" to switch the gateway as soon as the TQ difference is 
bigger than 20.

From "batmand -H":

-r routing class (only needed if gateway class = 0)
          default:         0  -> set no default route
          allowed values:  1  -> use fast internet connection (gw_flags * TQ)
                           2  -> use stable internet connection (TQ)
                           3  -> use fast-switch internet connection (TQ but 
switch as soon as a better gateway appears)

                           XX -> use late-switch internet connection (TQ but 
switch as soon as a gateway appears which is XX TQ better)

Greetings,
Marek