I am seriously looking at using B.A.T.M.A.N. to drive a mesh network in a small town in Australia. One of the hassles with typical mesh networks is the way the performance drops off when you have many hops, due to the radio having to keep switching between send and receive. The standard way to get around this appears to be to use multiple radios.
How is this done with batman? Is it a case of having multiple directional aerials - such that one radio can be receiving from one direction and another can be sending to the next node up the chain? It makes sense to put the local traffic (e.g. running a local AP) on a separate radio from the "back haul".
Does anyone have any experience with sort of layout? The main driver here is performance rather than coverage.
Damian
Ignore this, I think I have found my answer in the archives!
Damian
On Wed, 2008-06-11 at 00:13 +1000, Damian Ivereigh wrote:
I am seriously looking at using B.A.T.M.A.N. to drive a mesh network in a small town in Australia. One of the hassles with typical mesh networks is the way the performance drops off when you have many hops, due to the radio having to keep switching between send and receive. The standard way to get around this appears to be to use multiple radios.
How is this done with batman? Is it a case of having multiple directional aerials - such that one radio can be receiving from one direction and another can be sending to the next node up the chain? It makes sense to put the local traffic (e.g. running a local AP) on a separate radio from the "back haul".
Does anyone have any experience with sort of layout? The main driver here is performance rather than coverage.
Damian
Damian Ivereigh damo@launtel.net.au [080610]:
Ignore this, I think I have found my answer in the archives!
URL?
Hi -
B.A.T.M.A.N. supports multiple interfaces - so you may add more than one WiFi card to your systems and run batman on every interface that you like. Performance wise you should use different non-overlapping channels with different ESSIDs for your cards. You may use omnidirectional antennas, sectors or directionals. The latter two options will give you a planned infrastructure, where you have to do the channel planning (cellular infrastructure). There is no point in aiming directionals against each other while their interfaces work on different channels... You may still benefit from batman in such a planned network, because it will save you editing routing tables by hand.
If you use omnis (say two interface per device on channel 1 and 13) and the network is idle the routing may utilize just one channel. But as soon as there is traffic starting to saturate the links, the protocol should start using different channels. There is however no dedicated mechanism to coordinate the re-use of channels. Therefore Batman will need traffic in order to channel adaption. However this is AFAIK untested, and we'd love to hear about your results.
cu elektra
I am seriously looking at using B.A.T.M.A.N. to drive a mesh network in a small town in Australia. One of the hassles with typical mesh networks is the way the performance drops off when you have many hops, due to the radio having to keep switching between send and receive. The standard way to get around this appears to be to use multiple radios.
How is this done with batman? Is it a case of having multiple directional aerials - such that one radio can be receiving from one direction and another can be sending to the next node up the chain? It makes sense to put the local traffic (e.g. running a local AP) on a separate radio from the "back haul".
Does anyone have any experience with sort of layout? The main driver here is performance rather than coverage.
Damian
b.a.t.m.a.n@lists.open-mesh.org
-
Benjamin Henrion -
Damian Ivereigh -
elektra