Is there any manual way to prioritize a wired interface over a wireless interface? It seems to do so naturally at first, but if I unplug and replug the Ethernet cable a couple times when testing it will stay on wireless. Is this considered an optimization or a bug, and how can I make it so it should always choose the Ethernet, even in multi-hop situations? For example, Babel uses an "rxcost" metric for each interface to manually increase the cost of a route on each interface.
Thanks for your help.
On Thursday, September 13, 2012 08:25:36 adam wiz wrote:
Is there any manual way to prioritize a wired interface over a wireless interface? It seems to do so naturally at first, but if I unplug and replug the Ethernet cable a couple times when testing it will stay on wireless. Is this considered an optimization or a bug, and how can I make it so it should always choose the Ethernet, even in multi-hop situations? For example, Babel uses an "rxcost" metric for each interface to manually increase the cost of a route on each interface.
batman-adv has no ability to manually manipulate the cost of a link. Our goal is to make batman-adv as easy to use as possible, thus we refrain from adding too many configuration options. We'd rather implement an automatic detection even if it comes at the cost of not being amongst the first of supporting a certain feature.
Cheers, Marek
b.a.t.m.a.n@lists.open-mesh.org
-
adam wiz -
Marek Lindner