[Commotion-dev] first test version of NetworkManager integration for GNU/Linux

[Hans-Christoph Steiner]

It only handles wifi devices.  The dispatcher script/dbus approach used here
would not really handle the complexity of also meshing over ethernet well.
That should wait until there is actual work on the core of NetworkManager to
support mesh plugins.

.hc



On 02/26/2013 12:12 PM, Dan Staples wrote:
> I suppose it's all dependent upon the wireless driver supporting ad-hoc.
> We've had enormous difficulty getting our Asus netbooks to do ad-hoc.
> 
> Will this network manager also ethernet interfaces to join a mesh? How
> about if the computer has multiple wireless interfaces, such as a USB
> wireless device?
> 
> And I think at the moment we only have the commotionwireless.net profile
> to work from.
> 
> On 02/18/2013 10:55 PM, Hans-Christoph Steiner wrote:
>> I'm pretty sure I figured out the Ubuntu/quantal issue: that machine has a
>> binary blob wifi driver that does not handle adhoc well at all...  hopefully
>> this is not a common scenario.
>>
>> .hc
>>
>> On 02/18/2013 09:48 PM, Hans-Christoph Steiner wrote:
>>> Ok, I've done a bunch more testing, and have it reliably working on two Linux
>>> Mint/Maya aka Ubuntu/Precise machines.  I have been testing on a
>>> Ubuntu/quantal machine, and its NetworkManager seems to ignore the channel and
>>> hardcoded BSSID, so it tries repeated on channel 1 and fails.   arg...
>>>
>>> Right now, it includes a pre-configured NetworkManager connection for
>>> 'commotionwireless.net'.  Are there any other mesh profiles that should be
>>> included by default?
>>>
>>> .hc
>>>
>>> On 02/15/2013 01:18 PM, Dan Staples wrote:
>>>> That's excellent. I'd like to try it out in our Commotion-OpenBTS live
>>>> images, since they are based on Ubuntu.
>>>>
>>>> On 02/14/2013 02:21 PM, Hans-Christoph Steiner wrote:
>>>>> Hey all,
>>>>>
>>>>> I got the core of my 'dispatcher script' NetworkManager integration working,
>>>>> its called 'nm-dispatcher-olsrd' for now.  It uses the very simple
>>>>> 'dispatcher' script API to launch a python script in respond to network
>>>>> changes (interface up/down), then that python script talks to NetworkManager
>>>>> over dbus to get the whole picture. It then parses any profiles that are in
>>>>> /etc/nm-dispatcher-olsrd and if a new wifi connection matches one of the
>>>>> profiles, it sets up olsrd properly.
>>>>>
>>>>> The profiles are the same format as the MethTether profile, and the
>>>>> nm-dispatcher-olsrd Ubuntu packages I created include a profile for
>>>>> commotionwireless.net/02:ca:ff:ee:ba:be/channel 5.  So if you are within range
>>>>> of another commotionwireless.net node, you should just be able to install
>>>>> nm-dispatcher-olsrd, click commotionwireless.net in the NetworkManager wifi
>>>>> browser panel applet, then have working OLSR mesh!
>>>>>
>>>>>
>>>>> To try this on Ubuntu/Mint and probably Debian, do:
>>>>>
>>>>> sudo add-apt-repository ppa:guardianproject/commotion
>>>>> sudo apt-get install nm-dispatcher-olsrd
>>>>>
>>>>>
>>>>> Here are the repos:
>>>>>
>>>>> Ubuntu packages:
>>>>> https://launchpad.net/~guardianproject/+archive/commotion
>>>>>
>>>>> sources:
>>>>> https://github.com/eighthave/nm-dispatcher-olsrd
>>>>> https://github.com/eighthave/python-networkmanager
>>>>> http://pypi.python.org/pypi/pyjavaproperties
>>>>>
>>>>> Coming soon:
>>>>> * a panel applet to represent the status of the mesh
>>>>> * hopefully more automation of profiles
>>>>>
>>>>> .hc
>>>>>
>>>>> _______________________________________________
>>>>> Commotion-dev mailing list
>>>>> Commotion-dev at lists.chambana.net
>>>>> https://lists.chambana.net/mailman/listinfo/commotion-dev
>>>>>
>> _______________________________________________
>> Commotion-dev mailing list
>> Commotion-dev at lists.chambana.net
>> https://lists.chambana.net/mailman/listinfo/commotion-dev
>>
>