[Commotion-dev] Unifying Serval and Commotion Mesh

[Paul Gardner-Stephen]

On Tue, Dec 18, 2012 at 8:17 AM, Jeremy Lakeman
<Jeremy.Lakeman at gmail.com> wrote:
> On Tue, Dec 18, 2012 at 3:34 AM, Josh King <jking at chambana.net> wrote:
>> Hi Paul,
>>
>> This is something that we've been thinking about recently here at OTI as
>> well. I think it makes a lot of sense to standardize around SSIDs and
>> BSSIDs. Additionally, I'm working on rewriting the way that the OpenWRT
>> firmware handles connecting to the mesh as a standalone C daemon and
>> library, something that I hope may eventually serve as a cross-platform
>> way to manage configuration profiles and wireless connection issues in a
>> generalized fashion.
>>
>> In the short term, I've been thinking too about how to make sure that
>> the Commotion Android application and Serval can work together
>> effectively on the same device. Would it make sense for Serval to make
>> use of Meshtether to establish the wifi network if it's available, and
>> for Meshtether to connect to the Serval application's instance of
>> servald for encryption, if available?
>>
>
> If the Commotion Android application broadcasts an intent when the
> network is up, it would be fairly easy for Serval to start our daemon
> and communicate on that interface.

... and if you want example code of how to implement such a broadcast,
feel free to copy what we have in Serval Mesh :)