On Fri, 2013-01-18 at 19:15 -0500, Hans-Christoph Steiner wrote: > Hey dcbw, > > Right now I'm looking for where I can jump in and start coding something. I'm > thinking that I would modify NM to add the OLSR handling stuff like another > dhclient, avahi-autoip, etc. to get something working, then hopefully that > will make it more apparent what the plugin interface should look like. Then > we'd also have something to play with. I open to hearing other approaches to, > but I'm getting eager to try some coding.
To simplify the requirements we'd talked about: 1) need to identify which BSSIDs from scan results are an OLSR mesh node 2) when connecting to an OLSR node, olsrd needs to be started 3) once connected, IP configuration method may be specific to that mesh network and cannot be autodetected yet 4) need to separately identify OLSR mesh networks in UI applets Correct? Are there any more? Not trying to talk implementation here, but the 10,000ft requirements picture in general. Dan > Here's the transcript of our original conversation, where I think we pretty > much outlined the problem: > https://lists.chambana.net/pipermail/commotion-dev/2012-October/000853.html > > .hc > > _______________________________________________ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list _______________________________________________ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
