Network manager 0.7

We currently use a pretty hacked version of network manager 0.6

Sjoerd modified network manager to work with the mesh in 0.7 (forward ported the changes).

It would be nice if we had network manager 0.7 in joyride.

• Nicer API
• Nobody is developing 0.6 anymore
• 0.7 has new functionality and may have support for more networks

This would likely require working with

• Sugar presence service
• Neighborhood view
• Frame for the mesh device representation

Progress

• Michael Stone told bjordan this would be nice
• Sent out email to devel --Bjordan 22:35, 16 July 2008 (UTC)
• Initial NM 0.7 with mesh support ready -- sjoerd, 17 July 2008

Testing NM 0.7

A version of NM 0.7 with support for the OLPC mesh device is available at http://dev.laptop.org/~sjoerd/NM0.7/, this contains rpms, some needed config files and a few demo python programs. Note that using this version will break network configuration in sugar!

To test do the following steps:

• Ensure you have a recent joyride (Tested with build 2173)
• Install ppp using yum
• Install the NetworkManager-0.7.0 and NetworkManager-glib-0.7.0 rpms
• copy olpc-mesh.fdi to /etc/hal/fdi/information
• copy nm-user-settings.conf to /etc/dbus-1/system.d/
• reboot! (or restart hal and NM)

Now one can use:

• list_aps.py to list access points in range
• connect.py to connect to normal access points
• connectmsh.py to connect to the mesh in various ways

TODO

• Mesh Portal (MPP) support in NM 0.7
• NM 0.7 support in sugar:

What we need now is for someone to port the sugar components to use the new NetworkManager D-Bus API. NM 0.7 introduces a new D-Bus API and no longer supports the old one, which is what we use in sugar. --User:DanielDrake, via devel@

Bug #6248 - Presence service broken with NetworkManager-0.7 (NM D-Bus API change)

Interested in helping

--Bjordan - The more helpful information on the Wiki, the better my capacity to contribute (haven't done much dealing with network manager)

--mtd - I've done some work on Frame/mesh icons (Trac #6995) , so I could help with "Frame for the mesh device representation"