From Fedora Project Wiki

< Anaconda

Revision as of 12:40, 10 January 2011 by Rvykydal (talk | contribs)

incomplete

Network enablement and network configuration

Two tasks:

  • Network enablement for installer - configure and activate one device to be used during installation, e.g. to get kickstart, packages, or for network-backed storage. It can be configured using boot parameters, or kickstart, or if needed user can be prompted to enable network in loader UI (when fetching kickstart or updates image over network), or in text mode UI and GUI (when setting up network storage (iscsi, fcoe) or network repository). Additional devices can be activated only in GUI, using NetworkManager Connection Editor (nm-c-e) by checking Connect Automatically
    • There is a bug requiring an option of activation of additional devices in kickstart.
    • Once the device is activated, it can't be reactivated with changed configuration (e.g. static configuration with fixed nameserver, see bug 504983). I want to offer this possibility in GUI which requires option to activate/disconnect a device on demand (see device activation). In some cases it can be worked around by editing configuration files.
  • Network configuration of target system. Can be done with kickstart or in GUI using nm-c-e. Undesirably, checking Connect Automatically will activate the device after the configuration is applied (see ONBOOT side-effect). We are not aware of any problems caused by this side effect which is invisible to the user (Anaconda doesn't wait for NetworkManager activating the device), but I can imagine there might be some lurking.

As you can see, configuration of installer environment and target system is not well separated. It is because in GUI we use nm-c-e for enablement, and we have to use same configuration files for installer and target system configuration.

On Live CD, network is configured in Live CD environment using NetworkManager Applet on panel.

Modes of configuration

boot options

These anaconda boot options can be used to enable network in loader (e.g. for getting kickstart, updates image, or for network installation): asknetwork, dhcpclass, dhcptimeout, dns, essid, ethtool, gateway, ip, ipv6, ksdevice, linksleep, mtu, netmask, nicdelay, noipv4, noipv6, wepkey

kickstart

Kickstart network command can be used both to enable and configure devices. The behaviour has changed in the course of adoption of NM.

  • RHEL 5 - the first network command from kickstart activates or reactivates (if the device has already been enabled e.g. to get kickstart using configuration given in boot parameters) relevant device with configuration set by the command. Other network commands only set configuration for target system, they are not enabled in installer.
  • RHEL 6.0, Fedora 14 - the same as in RHEL 5, but already activated device is not reactivated with configuration set in network command, it is only set for the target system.
  • RHEL 6.1, Fedora 15 - expected behaviour (bug 668395, bug 638131) - the same as in RHEL 5 with option to activate additional devices using new network --activate option. Note that the device from first network command is (re)activated regardless of the option (to keep the behaviour of RHEL 5).

For RHEL 6.0 and RHEL 6.1, devices having.

loader text UI

Serves for selection and configuration of a network device that will be enabled in loader (which happens if kickstart or updates image should be fetched from network or in case of network installation). It will not be run if the information is provided via boot options or kickstart unless required by boot option asknetwork. Configuration options of this UI are a subset of nm-c-e which is used in GUI.

Once the device is successfully activated, there is no possibility to change its configuration in loader UI (see bug 504983).

TODO screenshots

TODO explain ipv6 options

TODO ipv4 succ and ipv6 fail

text mode UI

TODO

anaconda GUI

TODO

editing configuration files

Anaconda communictes with NetworkManager mostly with ifcfg files (nm-c-e stores its configuration there too). It can be handy to edit them directly for debugging or as workaround solution. Files can be edited using shell in virtual terminal tty2 ([Ctrl][Alt][F2]). Their location is /etc/sysconfig/netwrok-scripts/ifcfg-<device name>. The configuration will be applied in installer after the device is disconnected and reactivated. The device is disconnected if its ifcfg file is removed. It will be activated if an ifcfg file will be copied back to its location with ONBOOT=yes set. So configuration of active device for installer environment can be changed this way: 

mv /etc/sysconfig/network-scripts/ifcfg-eth0 /tmp
vi /tmp/ifcfg-eth0
mv /tmp/ifcfg-eth0 /etc/sysconfig/network-scripts

At the end of the installation, ifcfg files are copied to target system tree to directory /mnt/sysimage/etc/sysconfig/network-scripts.

Bugs and issues

  • No more than one device can be activated in installer with kickstart (e.g.: one NIC for repositories, another for iSCSI). Bug 638181 - here is a patch.
  • Reading configuration from iBFT in anaconda instead of passing the task to NetworkManager and dracut. Bug 634016 - here is a patch.

  • Configuration of successfully activated device in installer environment can't be changed (related bugs: 504983, 635239). There is no way to disconnect the device and activate it so that changed configuration could be applied (except for workaround by editing configuration files). In desktop, this is done with NetworkManager Applet which offers also selection of access points for wireless connection. I proposed two solutions for GUI on anaconda-devel-list:


  • IPV4_FAILURE_FATAL=yes by default and disabling ipv4 in loader UI or with noipv4 doesn't seem to work, so ipv6 only network configuration is problematic. bug 633815.

TODO ipv6 fail + ipv4 success

  • TODO stateless dhcp6
  • TODO onboot -> activate
  • TODO ONBOOT=no by default

Wireless

TODO

Retrieved from "https://fedoraproject.org/w/index.php?title=Anaconda/Network&oldid=214531"