@Edward and David: Don't know if this is helpful or if you've already seen it...
Here's how the new network interface naming scheme works (or is supposed to work): http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ From that page: "By default, systemd v197 will now name interfaces following policy 1) if that information from the firmware is applicable and available, falling back to 2) if that information from the firmware is applicable and available, falling back to 3) if applicable, falling back to 5) in all other cases. Policy 4) is not used by default, but is available if the user chooses so." And from my own testing on sid using a usb wireless interface, I got Policy 4 (MAC address in device name) by default, contrary to what it says. (Maybe 'cause I'm not running systemd?) This describes the names in detail: http://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev-builtin-net_id.c#n20 fsr On 09/28/2015 07:43 AM, Edward Bartolo wrote: > You can use udev to map wlan0 to the new device name so that netman would > work. > > I was thinking about a configuration file for the backend so that it > would be able to substitute wlan0 and eth0 with other device names as > set up by the user. I was thinking about this format: > wlanX=wireless-device-name > ethX=wired-connection-name > > However, I need the know what other developers think about this approach. > > Edward > > On 28/09/2015, Edward Bartolo <edb...@gmail.com> wrote: >> To connect automatically on boot you only need to pass --auto-conn >> parameter to netman, the frontend GUI. I use it that way and it >> connects as soon as I log into XFCE4. Configure your desktop or window >> manager to run netman with --auto-conn as a parameter. >> >> So, the command should be like this: >> /usr/bin/netman --auto-conn >> >> The latest netman commit on git.devuan.org uses a systray icon just >> like all other network managers. Left click shows the GUI, right click >> shows a popup menu. Icon is updated to signify 'connected' and >> 'disconnected' status. >> >> Edward >> >> On 28/09/2015, David Hare <davidah...@gmail.com> wrote: >>> Thanks Edward for your great effort, commitment and persistence and >>> Aitor for packaging. >>> >>> I have yet to work out how to automatically connect on boot. A manpage >>> is needed. >>> >>> An installation and some live images here use (self-compiled) eudev. The >>> wireless inteface is not necessarily wlanx but a string which I haven't >>> yet identified where it comes from. Maybe it's to do with newer >>> (systemd-)udev which eudev tracks. However it does show and work in >>> wicd. I would like to see netman identify and use other than wlan0. >>> >>> I have used wicd for convenience and ability to autoconnect but am not >>> keen on dbus reliance. Before I used wpa-gui but it has qt4 deps. >>> >>> Netman wouldn't work here till after reboot, with wicd initscript >>> disabled. >>> >>> David >>> >>> _______________________________________________ >>> Dng mailing list >>> Dng@lists.dyne.org >>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng >>> >> > _______________________________________________ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
