-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Zitat von Marek Lindner lindner_marek@yahoo.de:
Hi,
this question was a bit forgotten. :-)
how does batmand detect whether the internet connection is really connected to the internet or not. Or does batmand just relays on the -g parameter. Until now we let run a cron job that checks for the real working gateway. Because we can not relay on the presence of the default route. User may use a different router to connect to the internet and just add the default route this private router. The problem is that the node offering a internet connection (-g) should also be able to access other internet connection if its local connection is brocken.
First of all, "-g" is just flooded through the network. We also want some kind of "dyngw"-plugin but with a better approach: By using tunnels to the gateway batman is in a far better situation than OLSR. The "is internet really available" check can be done on the client side and is therefore much more reliable. With batman 0.3 all the packet flow towards and from the internet is going through batman. Batman just has to check whether traffic is coming back through the tunnel after sending packets to the internet. If this is not the case the batman node offering the internet is blacklisted and another gateway is chosen. This has not been implemented yet but all the neccessary basics for that feature are completed by now. Expect this feature to come in the following weeks.
Regards, Marek _______________________________________________ B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
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. For this I beleave that it is better to have a separated process 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. I have implemented in our firmware a test (like leipzig) that only pings some addresses.
cheers Stephan
Hi,
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 separated process 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 of.
Regards, Marek
b.a.t.m.a.n@lists.open-mesh.org