Re: [lime-dev] [Mesh] From libre-mesh

Hi! Probably. :-) I don't have a clear mental picture of it. And why not just BGP? So why using a routing protocol which was optimized for wireless links to run over something which is not a wireless network anymore (but an abstracted L2 Batman network, which might be somewhere deep in a wireless network, but none of this is seen to BMX)? The only thing you need is "network is available"/"network is not available" announcements which knows how to read Batman community IDs, no? You don't really need packet loss measurements for wireless links? Can Batman on one node participate in multiple communities at the same time? Have you seen this? http://www.open-mesh.org/projects/open-mesh/wiki/Connecting-Batman-adv-clou… So I do understand that you need some kind of L3 routing protocol on borders between L2 routing domains. But I am not exactly sure how this would work as a generic auto-configuring firmware. For example, if we have two L2 mesh networks: ------------ ------------ | [gateway1a]--link A--[gateway2a] | | mesh 1 | | mesh 2 | | [gateway1b]--link B--[gateway2b] | ------------ ------------ I am not sure how could gateway1b and gateway2b be one device, one node? And with an auto-configuring firmware? Both mesh 1 and mesh 2 are big L2 blobs. What I can understand is that gateway1a and gateway1b is part of mesh 1. And gateway2a and gateway2b part of mesh 2. They have between them each a special network link, respectively. So gateway1a/b have their own IPs inside mesh 1 and they also have IP inside the peering links. Same for gateway2a/b. So I know how to configure this manually. But I am not sure how BMX6 running on gateway nodes can just discover this automatically? And even more, how it can know over which link to route traffic? Link A or link B? It does not have any special knowledge of how well gatewa1a or gateway1b is connected to the rest of mesh 1. But even if we ignore that (which is really a hard problem to solve), the reason why BMX6 would be useful is because link A and link B can be of different link qualities and you want to route over better one? And how does BMX6 then propagate this information that link 1 is better than link 2 to clients in the mesh network? And still, how you configure those links automatically? I agree that discussion in person can help. But sooner or later we have to write something down. If you already have clear image what you want to build, then just write this down. Discussions are important if we need to create a solution. But in this case you are saying that you already have a solution. Can you just write this down? Mitar -- http://mitar.tnode.com/ https://twitter.com/mitar_m