KubuntuFeistyNetworking

Differences between revisions 1 and 11 (spanning 10 versions)
Revision 1 as of 2006-10-22 21:16:08
Size: 1558
Editor: clj46-234
Comment:
Revision 11 as of 2007-02-08 12:08:59
Size: 3203
Editor: clj46-234
Comment: current status
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
 * '''Launchpad entry''': https://features.launchpad.net/distros/ubuntu/+spec/kubuntu-feisty-networking
 * '''Packages affected''': TBD
 * '''Launchpad entry''': UbuntuSpec:kubuntu-feisty-networking
 * '''Packages affected''': kde-systemsettings, kdepim, kdenetwork, knetworkmanager
Line 10: Line 10:
We are lacking static configuration for WPA networks (knetworkconf), better handling of network availability by key applications (kopete, kmail...) and have to reduce some duplication (knetworkmanager, wlassistant). Kubuntu is lacking static configuration for WPA networks (knetworkconf), better handling of network availability by key applications (kopete, kmail...) and have to reduce some duplication (knetworkmanager, wlassistant).
Line 16: Line 16:
 * John is a mobile user. He connects to different wireless networks when traveling. He can use the network-manager tray icon to get a list of wireless network and can easily connect to them using any of the supported security modes (WEP, WPA, RADIUS...). He can use network services in the environment, like network printers, without further configuration.
 * Nancy goes to many meetings during the day, switching meeting rooms and plugging/unplugging the network several times. Her mail and chat clients detect network state, and automatically and gracefully disconnect/reconnect when the network state changes.
Line 18: Line 20:
Reconsider Kubuntu network configuration applications after inclusion of network-manager and avahi in default Feisty install. Make key applications network aware.
Line 20: Line 23:
 * Switch to knetworkmanager as default application for wire/wireless network management (see NetworkRoaming)
 * Remove configuration options for Zeroconf networking to ensure just-works experience (see ZeroConfNetworking)
 * Improve mail/chat/IRC clients to gracefully handle network disconnects/reconnects.
    * SuSE includes [http://developer.kde.org/~binner/distributor-patches/SUSE patches in OpenSuse 10.1] which include these changes; they need to be reviewed with Upstream and/or for inclusion in Kubuntu
Line 22: Line 29:

=== Code ===

=== Data preservation and migration ===
 * Install `networkstatus` by default '''[in progress]'''
 * Install `knetworkmanager` by default and drop `wlassistant` from default install and CD. '''[done: kubuntu-meta 1.24]'''
 * Patch `knetworkmanager` to be compiled with networkstatus support '''[done: knetworkmanager 0.1-0ubuntu8]'''
 * Incorporate Kmail/Kopete patches to gracefully handle network disconnects/reconnects
    * KMail: go to offline mode if not connected, no (or less invasive) errors if network is down '''[done: kdepim 4:3.5.6-0ubuntu3]'''
    * Kopete: automatically reconnect, no error if network is unavailable '''[in progress]'''
 * Remove "Zeroconf Service Discovery" from System settings as it is not needed anymore (avahi should just work). '''[TBD]'''
Line 28: Line 38:

== BoF agenda and discussion ==
 * Network configuration GUI: stay with knetwork conf (add WPA support) or implement Guidance networking module
 * Should we install knetworkmanager by default (just not autostarted on logon?)?
 * Should we drop wlassistant (replaced by knetworkmanager)?
 * Make network applications aware of network availability:
   * Kopete: automatically reconnect, no error if network is unavailable
   * KMail: go to offline mode if not connected, no (or less invasive) errors if network down
 * Tray icon notification: nothing (in edgy) vs. knetworkmanager (only wireless) vs. knemo (in universe)
 * Static IP configuration with WPA: knetworkconf does only WEP - user will need to edit config files if WPA is needed with static IP config. Guidance network configuration module would be nice replacement for knetworkconf, but it would require quite some work to implement

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

Kubuntu is lacking static configuration for WPA networks (knetworkconf), better handling of network availability by key applications (kopete, kmail...) and have to reduce some duplication (knetworkmanager, wlassistant).

Rationale

Good networking support is critical, particularly for mobile people.

Use cases

  • John is a mobile user. He connects to different wireless networks when traveling. He can use the network-manager tray icon to get a list of wireless network and can easily connect to them using any of the supported security modes (WEP, WPA, RADIUS...). He can use network services in the environment, like network printers, without further configuration.
  • Nancy goes to many meetings during the day, switching meeting rooms and plugging/unplugging the network several times. Her mail and chat clients detect network state, and automatically and gracefully disconnect/reconnect when the network state changes.

Scope

Reconsider Kubuntu network configuration applications after inclusion of network-manager and avahi in default Feisty install. Make key applications network aware.

Design

  • Switch to knetworkmanager as default application for wire/wireless network management (see NetworkRoaming)

  • Remove configuration options for Zeroconf networking to ensure just-works experience (see ZeroConfNetworking)

  • Improve mail/chat/IRC clients to gracefully handle network disconnects/reconnects.

Implementation

  • Install networkstatus by default [in progress]

  • Install knetworkmanager by default and drop wlassistant from default install and CD. [done: kubuntu-meta 1.24]

  • Patch knetworkmanager to be compiled with networkstatus support [done: knetworkmanager 0.1-0ubuntu8]

  • Incorporate Kmail/Kopete patches to gracefully handle network disconnects/reconnects
    • KMail: go to offline mode if not connected, no (or less invasive) errors if network is down [done: kdepim 4:3.5.6-0ubuntu3]

    • Kopete: automatically reconnect, no error if network is unavailable [in progress]

  • Remove "Zeroconf Service Discovery" from System settings as it is not needed anymore (avahi should just work). [TBD]

Unresolved issues

  • Static IP configuration with WPA: knetworkconf does only WEP - user will need to edit config files if WPA is needed with static IP config. Guidance network configuration module would be nice replacement for knetworkconf, but it would require quite some work to implement


CategorySpec

KubuntuFeistyNetworking (last edited 2008-08-06 16:13:58 by localhost)