[Commotion-dev] OLSR mesh tether app on Commotion

Hans-Christoph Steiner hans at guardianproject.info
Tue May 8 18:05:23 UTC 2012


On 05/08/2012 12:10 PM, Will Hawkins wrote:
> Thanks for the reply, Hans!
> 
> On 05/08/2012 12:00 PM, Hans-Christoph Steiner wrote:
>>
>> Hey Will,
>>
>> Glad to have your contributions on this! I'll go ahead and commit that.
>>  That app as it stands is the first alpha, so yea, it'll need lots more
>> fixes like this to make it work well.  I'm currently immersed in writing
>> a 'jsoninfo' plugin for olsrd which will allow the Android app to easily
>> get all of the information that the current txtinfo and httpinfo plugins
>> provide, as well as provide a way to set the HNA routes dynamically.
> 
> This seems like it will help with your goal (from your previous message)
> of making something that helps the user evaluate their "coverage".

>> We then plan on making olsrd.conf files for 7ish profiles, which will be
>> user-selectable, that's something you could work on now, if you are
>> interested.
> 
> This seems like a great idea. I was imagining profiles as something that
> would be a terrific idea (like you already have for the ad-hoc mode
> configurations for certain devices) for selecting configurations. Do you
> think that you will give the user that option on the home screen of the
> app or via the Settings? That's probably more of a GUI design decision,
> but I thought I'd ask.

This seems like an open question to me.  If the profiles end up being
something that a normal user will regularly switch between, then they
should be represented on the main screen.  If the profiles are something
that normal users set once and forget about it, then it would be better
as a setting.  I don't really have a strong idea about this yet, but I
think it would be good to have this on the main GUI to start out with to
see what people do with it.

>> Then we'll be implementing the final round of the GUI, I'll try to post
>> sketches this week.
>>
>> Perhaps you could also help us get some Commotion nodes setup on our
>> end?  We have a Buffalo and a few Foneras.  This would help us a lot
>> with testing.
> 
> I'd be happy to help you with this. Josh is rolling out some new builds
> shortly (w/in days) so I will work with him to find out exactly which
> buttons to press to make compatible images for those devices. We'll be
> in touch about this soon!

Excellent, keep me posted.

.hc


>>
>> On 05/08/2012 10:02 AM, Will Hawkins wrote:
>>> Hello everyone!
>>>
>>> First, let me introduce myself. I'm the newly minted "Commotion Mobile
>>> Developer" at OTI. I'm sure that I will be working closely with everyone
>>> from the Guardian Project (and others on this list) so I wanted to say
>>> hello before I got any further.
>>>
>>> I have had success building, configuring and running the OLSR mesh
>>> tether app (pulled from the Guardian project's github repo). After some
>>> tweaking to olsrd.conf I was also able to get it to properly mesh with
>>> the other nodes on our Commotion test network here at the office. Here
>>> are the relevant changes:
>>>
>>> --- a/assets/olsrd.conf
>>> +++ b/assets/olsrd.conf
>>> @@ -12,7 +12,7 @@ InterfaceDefaults
>>>      # If not defined the broadcastaddress
>>>      # every card is configured with is used
>>>
>>> -    # Ip4Broadcast             255.255.255.255
>>> +    Ip4Broadcast               255.255.255.255
>>>
>>>      # IPv6 address scope to use.
>>>      # Must be 'site-local' or 'global'
>>> @@ -91,8 +91,8 @@ InterfaceDefaults
>>>
>>>  # Fisheye mechanism for TC messages 0=off, 1=on
>>>
>>> -LinkQualityFishEye 1
>>> -
>>> +LinkQualityFishEye 0
>>> +LinkQualityAlgorithm "etx_ffeth"
>>>
>>>  # IP version to use (4 or 6)
>>>
>>> @@ -144,7 +144,7 @@ AllowNoInt  yes
>>>  # dynamically based on battery/power status
>>>  # if such information is available
>>>
>>> -Willingness            7
>>> +Willingness            3
>>>
>>>  # Allow processes like the GUI front-end
>>>  # to connect to the daemon.
>>>
>>>
>>> This diff is just FYI. Josh and I are going to figure out the best way
>>> to publish these changes.
>>>
>>> I'm very excited to get to work with everyone on this project.
>>>
>>> Will
>>> _______________________________________________
>>> Commotion-dev mailing list
>>> Commotion-dev at lists.chambana.net
>>> http://lists.chambana.net/mailman/listinfo/commotion-dev
>>>
>>
>> _______________________________________________
>> Commotion-dev mailing list
>> Commotion-dev at lists.chambana.net
>> http://lists.chambana.net/mailman/listinfo/commotion-dev
>>
> 
> _______________________________________________
> 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