From Fedora Project Wiki

Refine Network Configuration Given NetworkManager as Default


With NetworkManager as a Fedora X feature, we need to update the UI and backend code within anaconda to make sense for this.


  • Name: DavidCantrell

Current status

  • Targeted release: Fedora 10 (with at least IPv4 support)
  • Last updated: 2008-07-21
  • Percentage of completion: 25%

For Fedora 11, I plan to correct bugs and finalize the IPv6 support necessary for installation.

Detailed Description

Anaconda currently relies on the libdhcp (which, in turn, uses the libdhcp4client and libdhcp6client libraries) library for network device configuration. We discover the available devices in the system using udev and hal and then present a configuration interface for the user to collect configuration information. Once we have that information, we call libdhcp to bring up the device. The main problems with this are duplication of a lot of effort (other tools already do this) and the fact that we execute the DHCP and DHCPv6 clients via a library call, so the protocols are not followed correctly. Beyond that, we lack the capabilities for any new networking technologies that gain support in Fedora. Because we have our own configuration path, we cannot make use of those new tools.

Moving to NetworkManager in the installer will bring all of the current network interface management to the installer that the final system currently has.

Benefit to Fedora

  • Gain a more centralized network interface management tool for another part of the Fedora world (installation in this case).
  • Same tools used on the final system that are used during installation.
  • Possibility for other network interface installation scenarios (WPA wireless, mobile broadband, and so on).


Test Plan

User Experience


Contingency Plan


Release Notes