Google and open source mesh…please?
There are some questions being asked about the Google wifi project in Mountain View, CA. It appears that the real world performance is not acceptable from some user complaints and the network appears to buckle under pressure! Imagine that, a wireless network buckling under pressure!
The wireless portion of the network is powered by Tropos, a “mesh” wireless vendor. Tropos has responded.
We know that wifi was not designed with these deployments in mind, however its “what we got” and its in everyone’s laptops. Alot of these problems could be caused by the standard issues with wifi deployment such as interference from other Part 15 devices and attenuation caused by physical obstacles such as houses and their pesky walls or roofs.
At the Community Wireless Summit I watched an informative presentation by Jeffery King of Northrup Grumman describing the Corpus Christi Tropos deployment.
My one question at the end of the presentation was something like this “Did your due dillegence cover assesing the risk of going with a propreitary solution and the vendor lock in that happens?”. Most people don’t think of something like Tropos as being proprietary because it talks 802.11 to the end user. But all of the backend/backhaul mesh is proprietary, its what makes them in Jeffery’s words “infinitely scalable”. The problem being that extending the mesh requires buying tropos equipment because they do not use an open standardized routing protocol. Jeff’s answer was an honest “I don’t know if that was investigated”.
So now my question is why is the google project Tropos powered? There are open source mesh solutions that could really benefit from an injection of cash to move development forward. In addition these technologies need large scale deployments to help move them forward and make them better. This seems like it would be right up googles alley. Additionally deploying an open source mesh network would also mean that it would be possible for the users to extend the network themselves in MANET fashion.
You could say that my opinion is such because I am an owner of a company that sells wireless gear based on Open Source software. However I think we have already learned of the Internet that prorietary protocols in infrastructure devices does not go very far. I think this particular issue gets overlooked as a result of people assumming the network is standards based because its 802.11a/b/g. Most commercial mesh implementations are proprietary ,Google is in a position where they could help out the Open Source mesh networking world and change that. It’s not too late.

