[Commotion-dev] Unifying Serval and Commotion Mesh (Paul Gardner-Stephen)

Paul Gardner-Stephen paul at servalproject.org
Wed Dec 19 02:08:21 UTC 2012


Hello,

While a custom kernel isn't ideal, I am happy if they maintain them,
and make them available, as my main objection is the difficulty in
porting useful kernels to every type of phone, followed by rooting.

Paul.

On Wed, Dec 19, 2012 at 7:30 AM, Hans of Guardian
<hans at guardianproject.info> wrote:
>
> We've made contact with them, but haven't heard from them in a while.  If I remember correctly, they rely on a custom kernel, which is a no go for Serval and Commotion.  But other parts might make sense to merge.
>
> .hc
>
> On Dec 18, 2012, at 4:56 AM, Eric de Vries wrote:
>
>>
>> Hi,
>> I was wondering if anyone had given some thought into taking consideration the SPAN project as well for a possible merge/converge ? They also have a simple and working UI for (dis)activating a mesh network on Android.
>>
>> On Sun 16 Dec 2012 09:07:38 PM EST, Paul Gardner-Stephen wrote:
>>> Hi All,
>>
>>> From a Serval Project perspective, we see much value in converging on
>>> a single "standard" SSID (and ideally BSSID) for WiFi mesh networks
>>> for Serval and Commotion.  The logical choice is almost certainly to
>>> use whatever values that Commotion uses.
>>
>>> In fact, what we would like to see in time is that Commotion and
>>> Serval's Android ad-hoc WiFi mesh management software converge into a
>>> single thing, and possible a single APK that contains all Commotion
>>> and Serval functions, or possibly it will be two separate APKs --
>>> there are arguments for and against.
>>
>>> But back to the present...
>>
>>> The BSSID/ad-hoc bug issues on Android phones remains a source of
>>> intense pain (which is part of why we are working on a "mesh helper"
>>> device that would basically be a cross between an OpenWRT router and
>>> mobile phone, that would basically be pocket-sized battery-powered
>>> WiFi adhoc+AP plus long-range UHF radio).
>>
>>> So I am not sure that a final solution is possible now, but we are
>>> thinking about our default SSID for the Serval Mesh 0.90 release we
>>> are hoping to have out by Christmas, and we hope to continue the
>>> conversation about converging this all as much as possible.
>>
>>> Our feeling in the lab here is that until we have interoperation
>>> sorted out, that we will probably default to a serval-specific SSID,
>>> probably mesh.servalproject.org, so that it will point people to a
>>> (yet to be populated) web page where they can learn more.  But for
>>> 0.91 and later, we hope to make moves towards convergence.  Perhaps
>>> having a short list of configured network names and patterns is the
>>> next step, but this is all really thinking out loud for now.
>>
>>> Paul.
>>
>> _______________________________________________
>> Commotion-dev mailing list
>> Commotion-dev at lists.chambana.net
>> http://lists.chambana.net/mailman/listinfo/commotion-dev
>>
>



More information about the Commotion-dev mailing list