[B.A.T.M.A.N.] Multi-card MESH

[B.A.T.M.A.N.] Multi-card MESH

[Derek C]

Hi,

Is it possible to use BATMAN with two backbone network cards?

I am hoping to make nodes with three radio cards - two at 5Ghz and one
2Ghz card for customer access.

I have been playing around with openwrt on gateworks boards (4 miniPCI
slots) and three radio cards.  In my testing I've only been using typical
AP / STA setups on the "backbone" radio cards and I'm using OSPF to handle
dynamic routing.  I'm handing my MESH "intelligence" (making one node's
STA card associate to a close-by strong signal node's AP card) with Perl
scripts.

I've got problems with my test system not avoiding circular loops and
ignoring the bandwidth supply node(s).  I think I've gone on the wrong
path trying to re-invent the MESH wheel so I'm now looking into BATMAN as
a possibility.

thanks for any information!

Derek




-- 
Derek C

Re: [B.A.T.M.A.N.] Multi-card MESH

[elektra]

Hi -


 > Is it possible to use BATMAN with two backbone network cards?


multiple network interfaces are supported, but the current routing 
metric is based on packet loss and hop count, not actual throughput - 
this is likely to be suboptimal in some scenarios. Please go ahead and 
test if it does fit your purpose.

cu elektra

Re: [B.A.T.M.A.N.] Multi-card MESH

[Derek C]

Hi Elektra,

I wonder if I use an omni and a higher gain directional antenna would it
work itself out?  Longer distance links would find the directional
antennas would give a better association an hopefully less packet loss
while still having the same hop count.

Then again if the higher gain directional antennas all saw each other
(like with a higher node density) then it would end up being a single card
MESH system with unused cards and antennas.

I'm trying to find out if OLSR is the same with multi card systems

thanks

Derek

On Thu, July 31, 2008 2:43 am, elektra wrote:
> Hi -
>
>
>
>> Is it possible to use BATMAN with two backbone network cards?
>>
>
>
> multiple network interfaces are supported, but the current routing metric
> is based on packet loss and hop count, not actual throughput - this is
> likely to be suboptimal in some scenarios. Please go ahead and test if it
> does fit your purpose.
>
> cu elektra _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>
>


-- 
Derek C