On Tue, May 26, 2015 at 9:15 PM, Bob Copeland via Devel <[email protected]> wrote: > On Tue, May 26, 2015 at 08:40:14AM +0000, Lukas Göstl via Devel wrote: >> Now I want to increase the number of nodes in an area with this driver >> and I´m considering this: >> >> · If there are more than 8 nodes in an area, the nodes >> authenticate each other only to the limit of 8 neighbours. >> >> · Further the nodes authenticate in a way, that every node in >> the area is connected to at least one member of the mesh network. >> >> · If every node connects to different neighbours, every node >> could be reached directly, or over other nodes. >> >> · So if the limit of 8 stations is reached, all other nodes in >> the area which are not connected directly, are like >> nodes which are not in the area and should be reachable over other >> members of the mesh network. > > Yes, I haven't thought about this a lot, but the Mesh Formation Info > element appears to be useful here: it tells you whether a candidate peer > is connected to a gate and number of peerings it already has (and > connection to AS, but unless someone wants 802.1X that isn't so useful). > > I'm not sure what best policy is here, but I could envision something > simple like trying to split available slots between stations that are > connected to a gate and/or lots of other peers (thus enhancing our own > connectivity), and stations that have few numbers of peers (increasing > connectivity of leafs). I'm sure there's relevant research on that > though -- if anyone wants to point me at something to read, that would > be appreciated! > > I'd say userspace would be the best place to implement such a policy for > now. >
Perhaps, can take a look at the clustering approach. https://mentor.ieee.org/802.11/dcn/05/11-05-0611-03-000s-self-organizing-and-auto-configuring-mesh-networks.ppt ----- Chun-Yeow _______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
