I don't think it's CPU that's the issue, it's WLAN overhead. Too many nodes is too much overhead traffic.
The web is telling me there is an upper limit of a 'basic' cluster of about 300, and if you add some multicast filtering you can hit maybe 1500. OGM's are eventually going to saturate the network though.
That makes me think you should be looking at small clouds and some other 'routing' protocol to connect those clusters together. Maybe do an OSPF ring linking up the batman-adv clouds.
On Wed, Apr 26, 2017 at 10:06 AM, fuumind fuumind@openmailbox.org wrote:
Hi Jens!
By 'sufficient power', do you mean processing power to handle overhead traffic? I'm imagining a network which primarily connects WLANs.
Clouds of batman-adv networks sounds like a good idea. Any idea about how to implement the interfaces between these clouds? How big should they be allowed to grow before forming a new cloud?
fuumind
ons 2017-04-26 klockan 17:10 +0200 skrev jens:
i think this could scale , but you will need sufficient power / ethernet capacities at the nodes.
and the biggest problem may be that these endpoints make much noise on the layer2 level. (disovery protocolls and stuff like this)
you could easily imagine what would happen if you have a layer2 switch with 100000 ports.
i think that most of the time you will not do this, and implement some sort of routing between some clouds of batman-adv networks.
On 26.04.2017 16:20, fuumind wrote:
Hi list!
Been lurking for almost a year on the battlemesh list and recently joined here as well.
I'm curious about how well batman-adv scales. Would a network of 10 000 nodes work well? What about 100 000 nodes or 1 000 000?
Thanks! fuumind