KubuntuFeistyNetworking

Revision 4 as of 2006-11-10 01:54:06

Clear message

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

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).

Rationale

Good networking support is critical, particularly for mobile people.

Use cases

Scope

Design

Implementation

Code

Data preservation and migration

Unresolved issues

BoF agenda and discussion

  • Should we install knetworkmanager by default (just not auto started on logon?)?

  • Network configuration GUI:
    • stay with knetworkconf (add WPA support) or

    • implement new Guidance networking module
    • Conclusion: do nothing, we have WPA only for dynamic through knetworkmanager
  • Should we drop wlassistant?

    • replaced by knetworkmanager?

    • should we consider KWlan (see alse KubuntuKWlanInclusion)

    • Conclusion: knetworkmanager is the way to go
  • Make network applications aware of network availability
    • Kopete/Konversation: automatically reconnect, no error if network is unavailable
    • KMail: go to offline mode if not connected, no (or less invasive) errors if network down
    • Conclusion: review the patches in other distos that provide similar functionality
  • Tray icon notification: nothing (in edgy) vs. knetworkmanager (only wireless) vs. knemo (in universe)

    • Integrating tray icon notification (if any) and network configuration GUI
    • Conclusion: we do not need it as knetworkmanager will provide enough info
  • Avahi/Zero-config - see ZeroConfNetworking

    • We do not need enable/disable zero-conf anymore
    • Conclusion: As we will have .local TLD by default, we can drop System settings module completely as it will just work out of the box


CategorySpec