[B.A.T.M.A.N.] batman-adv not selecting a gateway when using "client 1" through uci config
Hi everyone,
I've been experimenting with gateway selection in QuintanaLibre. I have a very bad gateway that I want to work as a last resort gateway when the other is down, so I tried changing to gw_mode client 1 and used some unreal values for the Up/Down speeds to "force" the selection.
Anyway, this is all well, the good gateway gets selected from almost all the mesh, but the problem is that when I updated the client routers configuration using uci to make it permanent, I stumbled with this strange result that you can see here:
there's no gateway being selected until I manually run: # batctl gw_mode client 1 (which was te current mode anyway) on each client.
In fact, connected computers are not being served DHCP offers because of this.
Is this some known behavior or just something I overlooked?
Thanks as ever for your help with batman-adv, which here at the far south we are loving every day more as little mesh clouds keep spawning around us :)
Cheers, NicoEchániz
On Friday, July 20, 2012 04:24:11 Nicolás Echániz wrote:
there's no gateway being selected until I manually run: # batctl gw_mode client 1 (which was te current mode anyway) on each client.
In fact, connected computers are not being served DHCP offers because of this.
Is this some known behavior or just something I overlooked?
In fact you managed to uncover a regression that was overlooked for quite some time. Guess gw selection class 1 is rarely used. :-)
Can you apply the attached patch and verify that it fixes the problem ? Here in my test setup it does.
Regards, Marek
On 07/22/2012 08:20 AM, Marek Lindner wrote:
On Friday, July 20, 2012 04:24:11 Nicolás Echániz wrote:
there's no gateway being selected until I manually run: # batctl gw_mode client 1 (which was te current mode anyway) on each client.
In fact, connected computers are not being served DHCP offers because of this.
Is this some known behavior or just something I overlooked?
In fact you managed to uncover a regression that was overlooked for quite some time. Guess gw selection class 1 is rarely used. :-)
Can you apply the attached patch and verify that it fixes the problem ? Here in my test setup it does.
Marek patch applied (thanks Guido) and verified. gw_mode client 1 is now properly selecting a gateway when set in the config.
thanks for your prompt reply :)
cheers, NicoEchániz
On Monday, July 23, 2012 11:02:49 Nicolás Echániz wrote:
Is this some known behavior or just something I overlooked?
In fact you managed to uncover a regression that was overlooked for quite some time. Guess gw selection class 1 is rarely used. :-)
Can you apply the attached patch and verify that it fixes the problem ? Here in my test setup it does.
Marek patch applied (thanks Guido) and verified. gw_mode client 1 is now properly selecting a gateway when set in the config.
Thanks for testing the patch. I updated the OpenWrt package and will provide a patch that goes into the next release.
Cheers, Marek
b.a.t.m.a.n@lists.open-mesh.org
-
Marek Lindner -
Nicolás Echániz