Dapper Network Manager

NetworkManager aims for network connectivity which "Just Works". The computer should use the wired network connection when its plugged in, but automatically switch to a wireless connection when the user unplugs it and walks away from the desk. Likewise, when the user plugs the computer back in, the computer should switch back to the wired connection. The user should, most times, not even notice that their connection has has been managed for them; they should simply see uninterrupted network connectivity.

NetworkManager has the chance" of being integrated into Dapper and will feature support for WPA and 802.1x as well. We will also provide l-r-m packages with updated wifi drivers.

There is GNOME network-manager-gnome (old nm-applet) and KDE (knetworkmanager) front-end that runs in sys tray and provides control over NetworkManager.

More information about NetworkManager is available at the gnome project page. You can also check the list of supported hardware.

NetworkManager is beta software.


NOTE: NetworkManager 0.6.1 has been included into official repositories - see report.

Thanks to everybody involved. You will be able to remove our test repository from your list.

Note: If you are running Kubuntu/KDE, then you should be installing KNetworkManager.

The repository contains the following packages:

  • network-manager, netwok-manager-gnome (by us)
  • libnl, a dependency of n-m 0.6 (by TomParker)

  • libnl-dev (patched by us and the DapperKNetworkmanager maintainers)

  • wpasupplicant 0.4 with the required feature for n-m backported from 0.5 (by ReinhardTartler)

And also:


NOTE: if you are using NM from official Ubuntu repository, please report your bugs into Malone. Official version of NM is also discussed in forums in this thread.

NetworkManager doesn't manage interfaces with manual configuration defined in /etc/network/interfaces. To get n-m to manage all the interfaces properly, backup /etc/network/interfaces and remove all wired/wireless interfaces that you want to be managed by n-m (if you want to leave full control to NM just leave the lines concerning the lo and maybe ppp and tun interfaces). You can leave your wired/wireless interfaces only if they are set to auto and dhcp (and no other options!) - the only allowed config for NM is the following two lines (replace eth1 with your interface):

  •   auto eth1
      iface eth1 inet dhcp

WPA users: you need to set "ENABLED=0" in /etc/default/wpasupplicant and ensure than wpasupplicant is not running. NM will take care for controlling wpasupplicant.

Discussion about these packages is also going on in this forum thread. There is also older thread.where you may find useful info.

If it does not work for you, you may get more info from messages reported by NM processes - see this forum post for instructions.


Before reporting issue, please try to follow tips in this thread (thanks to NeoChaosX).

n-m & driver issues

  • NM tries to connect WEP instead of WPA
    • removing key from keyring helps - see forum post 1, 2, 3, 4, 5

  • madwifi driver does not support bacground scan, causing disconnects due to NM network scanning - see forum post

    • can NM network scan be disabled/limited when connection is established (only done on disconnect or when user opens applet menu)?
    • can bacground scan feature be backported from madwifi-ng driver back to Ubuntu madwifi - see forum post

  • madwifi doesn't report status in percentages, but rather in RSSI

  • orinoco with WEP regression from 0.5.1 - see post

    • logs: NM 0.5 and NM 0.6 and NM mailing list

    • in some cases it is possible to use hostap drivers instead. to try that one has to create a blacklist file for the orinoco drivers: create /etc/modprobe.d/blacklist-orinoco with this content:
    • blacklist    hermes
      blacklist    orinoco
      blacklist    orinoco_pci
      blacklist    orinoco_cs
      blacklist    orinoco_plx

nm-applet issues

  • you must enter your keyring password each time NM starts - see GNOME bug#331529

  • nm-applet assertion on startup - see Malone #35662: FIXED: this is a dupe of Malone #6473, do "sudo gtk-update-icon-cache -f /usr/share/icons/hicolor/" and it should be fixed.

Cosmectic issues

  • The differents icons used in nm-applet don't have the same size. In some configuration, this can cause your whole gnome-panel icons moving forth and back when switching icon in NM. ( LP#36009)

  • With the new Dapper icons, the WEP icon looks like nothing. I guess it's the "lock" WEP icon but it doesn't mean anything. I think this icon must be set back as a lock or something similar. ( LP#36017)

  • If one of your card has a very long name (for example here : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ ), the menu becomes really large and quite ugly. ( LP#36011)


Please do not edit this page directly, place your comments here. Thanks.

  • Please consider this patch (http://mail.gnome.org/archives/networkmanager-list/2006-January/msg00141.html) to NM to get the best functionality from madwifi seeing as the madwifi project are hesitant to change anything. Robert Love is including it to Redhat/Fedora (I believe) and Dan refuses to commit it to upstream (fair enough).

  • As far as I can tell madwifi does not work with the provided drivers. Please consider this HOWTO if you have issues NetworkManagerMadwifi

  • The sources.list information is wrong, I get a 404.
    • I do too, but this is because I have an amd64 and they don't have these packages yet.
  • When NetworkManger runs I'm hit by this bug: #16137. After killing the 'ip route' process NM works fine though. BTW, where should we report problems about these packages?

    • you can always report problems to "mario dot danic at gmail dot com" regarding N-M
      • and it's gnome applet. For KNetworkManager, please contact maintainers.
  • It seems that the packagess were updated (names changed and all). Next time please try to also update the version number. Thanks.
    • this is intentional - first version that will be included in Dapper should be ubuntu1
  • Apparently NM conflicts with manual configuration of network interfaces, it resets changes in the networking configuration panel on Flight 5.
    • known ... see notes.
      • yes, but it should not happen, it is a show stopper for first time users
        • we'll try to make it play more nicely with current interfaces, but complete compatibility is a no-no
  • NM is trying to run /usr/sbin/wpa_supplicant (says in --no-daemon in console), which fails with ENOENT, should be /sbin/wpa_supplicant. Making symlink resolves this. Should be fixed. (wpasupplicant=0.4.8-0ubuntu1, network-manager=0.6.1-0ubuntu1).
    • This breaks on my machine, where it tries to run /sbin/wpa_supplicant which is not there because it is in /usr/sbin/. Can there please be some consistency?
      • You have wpasupplicant from test repo (which was in /usr/sbin), but you should get official version (wihich is /sbin). I suggest that you remove wpasupplicant and restart.
        • Thanks, it works now, the normal package update didn't catch that.

DapperNetworkManager (last edited 2008-08-06 16:31:14 by localhost)