DapperNetworkManager

Differences between revisions 27 and 28
Revision 27 as of 2006-03-20 08:43:05
Size: 3089
Editor: external-7
Comment:
Revision 28 as of 2006-03-20 12:56:54
Size: 3254
Editor: external-7
Comment: WPA note
Deletions are marked like this. Additions are marked like this.
Line 50: Line 50:
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.
Line 55: Line 57:

Status

Dapper Network Manager

Network Manager 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.

Network manager that "has the chance" of being integrated into Dapper will feature support for WPA and 802.1x as well. We will also provide l-r-m packages.

More information about Network Manager is available [http://www.gnome.org/projects/NetworkManager/ here] .

Network-Manager is beta software.

Installation

  • Import the PGP key by running wget -q -O- http://kubuntu.no-ip.org/AnthonyMercatante.gpg | sudo apt-key add -

  • Add the following to /etc/apt/sources.list:

    deb     http://kubuntu.no-ip.org/kubuntu dapper main
    deb-src http://kubuntu.no-ip.org/kubuntu dapper main
  • Run sudo apt-get update

  • Run sudo apt-get install network-manager nm-applet

The repository contains the following packages:

  • network-manager, nm-applet (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:

Notes

Network-manager doesn't manage interfaces defined in /etc/network/interfaces. To get n-m to manage all the interfaces properly, backup /etc/network/interfaces and remove everything except the lines concerning the lo interface.

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 [http://ubuntuforums.org/showthread.php?t=145230 forum thread].

Madwifi doesn't report status in percentages, but rather in [wiki:WikiPedia/Rssi RSSI].

If you are running Kubuntu/KDE, then you should be using [:DapperKNetworkmanager:KNetworkManager]?

New kernel builds are on the way, and once that happens, a new linux-restricted-modules will replace our patched package. Once the new kernel builds are out, we will work hard to rebuild the package, so that it works for the new kernel build as well. When that happens, you can just upgrade the system.

Issues

Comments

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

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