this sounds good, but you should keep in mind that
such a "good"
internet connection that was choosen being the best, has only a short
disconnection. I this case each batmand of each client should retest
the connection after a timeout of few minutes. I think this could be
disturbing an established connection because the batmand has to change
the tunnel to the new gateway.
I think you misunderstood. The batman (internet) client will not "check" if
the internet connection is available or not. It waits until the user wants to
connect to the internet and than observes if the requests to the internet are
answered or not. Of course, batman will wait until a timeout is reached and
wont kill the connection instantly.
For this I beleave that it is better to have a
checking its own internet connection (if provided and setup by node
config). this process then tells batmand about the connection. batmand
will deside on some criteries if this connection is stable an worth to
be populated through the net.
In addition this is a good thing to do. But it should be implemented by the
firmware maintainer and not by us.
I have implemented in our firmware a test (like
leipzig) that only
pings some addresses.
You are not the first who has the idea to do so. Unfortunately this approach
does not work everywhere. You should get in contact with Sven-Ola (the
maintainer of the dyngw plugin) and ask him what his latest solution consists