BATMAN does not really support that for multihop mesh networks. If you want
this behavior only for single hop connections you can cheat with batmand-exp
using the options:
--asymmetric-weight and the interface specific option /c
A smaller /c value (than the default) will apply a penalty to the detected
link transmit quality of an interface and the --asymmetric-weight switch can
then be used to tell the algorithm to be more reluctant to use links with a
bad transmit quality.
I successfully tested this in a simple wired two-node setup each with two
interfaces as illustrated below. Afterwards batman did set up the routing
table that a ping between node A and node B always chooses the upper link
from A to B and the lower link from B to A.
node A node B
eth0 -------------> eth0
eth1 <------------- eth1
therefore I started on node A:
batmand --asymmetric-weight 2 eth0 /c 100 eth1 /c 50
and on node B:
batmand --asymmetric-weight 2 eth0 /c 50 eth1 /c 100
But be aware, that this will change the default behavior of batman and may
have negative side effects on the overall path detection in you mesh.
On Montag 11 Februar 2008, Predrag Balorda wrote:
Has anyone thought about this "problem" recently?
To simplify - 3 routers, 2 adapters each, how do we establish duplex links
between each of those by using batman alone?
Or, 3 routers, 2 adapters each, how do we establish simplex links between
each of those such that one adapter links "upstream" and one
using batman alone?
> Another thing - think of this as quasi-asynchronous links, i.e. B can
> talk to A on both interfaces (call them int1 and int2), but only chooses
> int1, and A does the opposite, chooses the other (int2) to talk back to
> B. If B has to talk to both A and C at the same time and can see A and C
> on both int1 and int2 then it will choose int1 to talk to A and int2 to
> talk to C.
> Maybe it makes sense now....
> P.S. or maybe I'm just missing something
> > -----Original Message-----
> > From: Predrag Balorda [mailto:firstname.lastname@example.org]
> > Sent: Friday, January 18, 2008 2:42 PM
> > To: 'The list for a Better Approach To Mobile Ad-hoc Networking'
> > Subject: Multiple wireless interfaces
> > Ok. Here is something batman doesn't provision for - dual-interface
> > setup where you want to create a duplex link (tx on one and rx on
> > another). Duplex link to one other node is simple (and has to be done
> > manually),
> > how would we go about creating a duplex link to 2 or more nodes? Or one
> > simplex link to downstream node and one simplex link to upstream node?
> > Example:
> > A = B C duplex link (for example I need to talk from B to A fast and
> > I use both interfaces to talk to A)
> > A - B - C simplex links (I use one interface to talk to A and one to
> > talk to B)
> > A = B/B = C duplex links for all links (I talk to both A and C duplex,
> > not at the same time of course)
> > How do we do this with batman easily and dynamically (without having to
> > manually mess around with routing tables etc)?
B.A.T.M.A.N mailing list