[Commotion-dev] Use case for mobile + fixed wireless OLSR?

Hans-Christoph Steiner hans at guardianproject.info
Tue May 8 19:53:37 UTC 2012


I think that mobile+mesh is probably the ideal use case for reliable
mobile meshing.  The fixed devices maintain a barebones mesh and perhaps
internet HNA routes, then as the mobiles come and go, they should be
able to associate with the fixed mesh nodes.  The fixed nodes could also
have a very high willingness so that they bear the bulk of the broadcast
traffic, allowing the mobile devices to save their batteries.  I'm
guessing there are other things that we'll want to tweak.

I'm thinking these would likely be two profiles: purely mobile mesh, and
mobile mesh with fixed anchors.

.hc

On 05/08/2012 02:15 PM, Ben West wrote:
> Hi All,
> 
> In lieu of Will Hawkins' recent recruitment for OTI mobile mesh
> development (congrats, Will!), I am curious if anyone has given
> thought to use cases where potential mobile devices with OLSR mesh
> tether app would interoperate with fixed 802.11 hotspots running
> OpenWRT/Commotion + OLSR.
> 
> That is, I personally work with meshes of fixed hotspots, and I do
> understand many of the list members are envisioning meshes of perhaps
> only mobile devices, e.g. for ad-hoc assemblies of people in public
> plazas and the like.
> 
> Is there a particular, compelling use case to have both classes of
> devices, mobile and fixed, participate in the same mesh?  E.g., is it
> likely that a mostly mobile mesh might use one or two fixed hotspots
> for convenient uplink to the Internet?  That is, besides letting the
> mesh operate in conventional fashion, are there specific things one
> could do to take advantage of the fixed hotspots (which one could
> expect to have higher tx power, better rx sensitivity, and/or fast
> wired uplink)?
> 
> Part of my motivation for asking is that I await a Republic Wireless
> handset hopefully at some point this summer, and that phone's
> proclivity to use 802.11 service over 3/4G seem to make it a natural
> companion to Commotion.
> 



More information about the Commotion-dev mailing list