[Battlemesh] o11s and L3 routing protocol coexistence

[Pau]

Hello Thomas.
>From my point of view o11s and the other protocols cannot be tested at same
time.
However we can perform the experiments one after the other. We just need to
adapt
the firmware to be able to switch the link-layer, and think about
not-concurrent experiments.

Cheers
--
./p4u


On Fri, Jan 25, 2013 at 7:41 PM, Thomas Pedersen <thomas at cozybit.com> wrote:

> Hi list,
>
> We'd like to represent o11s at WBMv6, but are a little concerned how
> the battlemesh will be done in practice. According to the wiki [1]
> there is a desire for all routing protocols to coexist on the same
> (physical) L2 link. As you probably know though, o11s implements its
> own routing protocol at L2 and cannot coexist with an IBSS interface
> on the same radio.
>
> One way to resolve this is let o11s be the "carrier" link for the
> different VLANs, but this would probably break the other routing
> protocols as they don't expect their L2 broadcast traffic to propagate
> throughout the entire mesh? Not to mention the mcast storm that would
> incur.
>
> We could set the o11s mesh TTL = 1 to ensure only single-hop
> propagation takes place, but of course this would have to be switched
> back when testing o11s and the tests could no longer be run in
> parallel.
>
> Another solution is to find a test platform that has 2 radios and
> dedicate one of them to o11s.
>
> Any ideas?
>
> --
> Thomas
>
> [1] http://battlemesh.org/BattleMeshV6/Firmware
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20130125/cd1a2758/attachment-0001.html>