BATMAN is interesting because it operates at Layer 2 rather than Layer 3, unlike most IP-based mesh networking schemes. There is some explanation here, including the rationale for its implementation as a kernel module the batctl CLI:
http://www.open-mesh.org/projects/batman-adv/wiki/Doc-overview I suspect that negotiating the gateway will be the major point of contention between connman and batman— the proper behaviour is probably "use a local (connman) gateway if available; fall back on a gateway in the mesh", similar to how mobile data works. I suppose you'd express that as a batman-specific Technology which manages the relationship between bat0 and the other interfaces? Mike On 9 January 2015 at 10:16, Tim Tisdall <tisd...@gmail.com> wrote: > On Fri, Jan 9, 2015 at 1:49 AM, Patrik Flykt <patrik.fl...@linux.intel.com > > > wrote: > > > On Thu, 2015-01-08 at 11:05 -0500, Tim Tisdall wrote: > > > Does connman have any capabilities to manage a mesh network such as > > > B.A.T.M.A.N.? > > > > Not at the moment. Feel free to educate us on the mailing list with what > > functionality would be needed for ConnMan, though :-) > > > > Well, I'm still figuring it all out myself... As far as I understand it, > the mesh network shows up as a virtual network interface with a fixed IP > address. Does ConnMan just ignore network interfaces it doesn't > recognize? I'm thinking specifically of settings > like "SingleConnectedTechnology=true"; will ConnMan try to manage the mesh > networking interface? > > -Tim > _______________________________________________ > connman mailing list > connman@connman.net > https://lists.connman.net/mailman/listinfo/connman > _______________________________________________ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
