[Commotion-dev] network profiles in Mesh Tether

[David Oliver]

Hans,

Thanks so much for this clarification.

I do think we're missing something, still, however.  We know that olsrd -
the actual daemon software - has many operational parameters.  It's a
problem, however, that we don't really have a good idea what modifying
those parameters means, and we don't have a good idea if or how modifying
such parameters will improve or ruin mesh network connectivity and
performance when mobile networks (and intermittent network users on mobile
devices) are involved.

What this implies to me is that even under the (future) circumstances where
we have an easier ability to discover and connect to mesh networks (which
your definition of the "profile" addresses), we do not yet know if, upon
connection, there are other settings/configurations necessary to optimize
performance for specific mesh situations.    Thus, unlike WiFi, there may
need to be two "layers" here: (a) connection and (b) optimizing performance.

When I wrote up the scenarios earlier on (and proposed seven profiles,
mostly just dreaming them up since we have no knowledge to support them), I
intended them to be separate from "network settings" (network connection
parameters).  Overall, though, my current feeling is that we simply lack
the proper knowledge to understand this second portion and we should just
leave it for the experimenters to discover for us.

Dave

David M. Oliver | david at olivercoady.com | http://olivercoady.com |
http://dmo.tel | @davidmoliver | +1 970 368 2366


On Thu, Jun 28, 2012 at 2:05 PM, Hans-Christoph Steiner <
hans at guardianproject.info> wrote:

>
> I think the confusion over the "profiles" in the Mesh Tether app stems
> from the vague term "profile" and lack of context.  These profiles are
> network profiles, i.e. all of the settings needed to connect to an OLSR
> mesh network.  Here's a quick example:
>
> commotionwireless.net:
>        SSID: commotionwireless.net
>        BSSID: 02:ca:ff:ee:ba:be
>        channel: 5
>        DNS: 8.8.8.8 + plugin 127.0.0.1
>        LinkQualityAlgorithm "etx_ffeth"
>        IP root: 10.
>        netmask: 255.0.0.0
>
>
> funkfeuer:
>        SSID: freiesnetz.www.funkfeuer.at die
>        BSSID: 4E:FE:52:36:2E:65
>        channel: 1
>        DNS: 193.238.157.16
>        LinkQualityAlgorithm "etx_ff"
>        IP root: statically assigned, real IPs
>
>
> And so on and so forth.  The idea is that each profile represents how to
> connect to a mesh.  It is a quick and dirty version of the wifi browser
> that must be manually configured.  Hopefully, this won't be the final
> idea, but before we can do a proper scanner and browser, there is much
> work to be done (IP address assignment techniques, SSIDs as mesh
> descriptor, etc.).
>
> .hc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20120628/4ec9fc52/attachment.html>