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 "downstream" 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:p...@balorda.com] > > 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), > but > > 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, > but > > 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)?
