Infeasible
Status Update
Comments
yo...@gmail.com <yo...@gmail.com> #2
Apologies, this needs to be a Feature Request but that didn't appear as an easy to find option when I created the ticket.
yo...@gmail.com <yo...@gmail.com> #3
Also include in consideration is the ability to support projects in the US like:
Redhook, Brooklyn
BambooWifi, Philidelphia
SMesh, Baltimore
MetaMesh, Pittsburgh
DigitalStewards, Detroit
NYCWireless, New York
MeshnetProject, Seattle
and more... But hopefully you get the idea of just where and how being able to extend a mesh network might be a useful feature.
Redhook, Brooklyn
BambooWifi, Philidelphia
SMesh, Baltimore
MetaMesh, Pittsburgh
DigitalStewards, Detroit
NYCWireless, New York
MeshnetProject, Seattle
and more... But hopefully you get the idea of just where and how being able to extend a mesh network might be a useful feature.
si...@google.com <si...@google.com> #4
Hi,
We have passed this request to the development team and will update this issue with more information as it becomes available.
Thanks
We have passed this request to the development team and will update this issue with more information as it becomes available.
Thanks
us...@gmail.com <us...@gmail.com> #5
Serval Project is another that will benefit from this initiative.
vi...@google.com <vi...@google.com> #6
Once again, thank you for submitting the feature request. After following up with our product and engineering teams, the feature request will not be able to be considered at this time.
Description
Therefore, since I'm unable to comment or vote on any active tickets regarding the featrure request for an Ad Hoc network support I'm adding a ticket to your system.
The original is quoted below but I think there's more that needs to be considered given current developments in the networking community.
There are a number of active projects to create an ad hoc networking solution, aka mesh network, using cell phones to extend the current networks, provide networks in communities where none exists either because of technology or disaster which have been trying to develop work arounds for this and they all are essentially rooting or replacing the core functionality of the networking components.
Examples of this include such projects as:
Serval Mesh (
Open Garden (
Right Mesh (
Apple Iphone (iOS 7 and above supports this)
Haiti rescue operations in 2010 (
Additional rescue operations that benefited from ad-hoc networking operations include Hurricanes Harvey, Irma, Maria.
Finally there is growing support for this type of functionality on a global scale if you can consider the UN resolution (
In short - the need for ad-hoc mesh networking for smart phones is here and arguably even overdue.
While these solutions utilize a combination of Bluetooth - WiFi - Cellular data to build out the networks, the fundamental problem is that establishing AdHoc WiFi networks that can be efficient, secure (VPN and/or WPA2), and consistently implemented is lacking. Security is a must and cannot be blocked but could be enabled as part of the implementation.
In order for these fragmented communication platforms to work effectively some core functionalities need to be developed with the eventual requirement that it become cross platform capable, providing other platforms are willing to use a non-proprietary interface.
The ability to support wifi ad hoc networking will allow use cases
currently not supported by any non-wifi phone and even on the iPhone ad hoc
networks are not officially supported. This could be a significant
differentiator.
The use cases I have in mind include using wifi to message friends on a
plane or bus where you couldn't get a seat next to each other.