DapperNetworkManager
3084
Comment:
|
3046
Various changes
|
Deletions are marked like this. | Additions are marked like this. |
Line 39: | Line 39: |
* libnl-dev (patched by us and [https://wiki.ubuntu.com/DapperNetworkManager Dapper Kn-m maintainers]) | * libnl-dev (patched by us and the DapperKNetworkManager maintainers) |
Line 50: | Line 50: |
Discussion about these packages is also going on in this forum [http://ubuntuforums.org/showthread.php?t=145230 thread]. | Discussion about these packages is also going on in this [http://ubuntuforums.org/showthread.php?t=145230 forum thread]. |
Line 52: | Line 52: |
Madwifi doesn't report status in percentages, but rather in [http://en.wikipedia.org/wiki/Rssi RSSI]. | Madwifi doesn't report status in percentages, but rather in [wiki:WikiPedia/Rssi RSSI]. |
Line 54: | Line 54: |
Perhaps you need [https://wiki.ubuntu.com/DapperKNetworkmanager KNetworkManager]? | Perhaps you need [:DapperKNetworkmanager:KNetworkManager]? |
Line 57: | Line 57: |
New kernel builds are on the way, and once that happens our L-R-M package will be overwritten. Once the new kernel builds are out, we will work hard to rebuild the package, so that it works for new kernel build as well. When that happen, you can just upgrade the system. | 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. |
Status
Created: by JohanKiviniemi, MarioDanic
Priority: LowPriority
Maintainers: JohanKiviniemi, MarioDanic
Contributors: AdamConrad
- Interested:
Status: Building packages, DapperGoal
- Branch:
- Malone Bug:
- Packages:
- Depends:
- Current needs: As much testers as possible
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:
knetworkmanager (by AnthonyMercatante, a patch from LukaRenko)
- linux-restricted-modules (patched so that madwifi users can use WPA networks with n-m)
(built by AdamConrad)
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.
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].
Perhaps you need [: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)