- 1 Network enablement and network configuration
- 2 Modes of configuration
- 3 Selection of device to be enabled in installer
- 4 Wireless
- 5 Bugs and issues
Network enablement and network configuration
Network enablement in installer
Configure and activate a network device to be used during installation, e.g. to get kickstart, packages, or for network-backed storage. The configuration can be supplied with boot parameters, or kickstart, or if needed user will be prompted to configure a device in UI. Network enablement can happen in loader or in stage 2:
- In loader:
- for kickstart
- if network is needed in loader, e.g. to fetch kickstart or updates over network, or in case of vnc install (TODO: in case of using sshd)
- in rhel5 also in case of network installations (i.e. using remote stage 2 or repositories)
- for kickstart
- In stage 2, using text mode UI or GUI:
- when setting up network attached storage (iscsi, fcoe)
- when using network repository
Additional devices can be activated in GUI, using NetworkManager Connection Editor (nm-c-e) by checking Connect Automatically. Since RHEL 6 and Fedora 15/16?, additional devices can be activated (in loader) using kickstart network option
--activate (this can be needed e.g. when downloading packages from one NIC/subnet and having iSCSI target on separate NIC/subnet).
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). 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 in nm-c-e will activate the device after the configuration is saved (see ONBOOT side-effect). I am 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 using nm-c-e for enablement we have to use the 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
These anaconda boot options can be used to enable network in loader (e.g. for getting kickstart, updates image, or for vnc):
asknetwork, dhcpclass, dhcptimeout, dns, essid, ethtool, gateway, ip, ipv6, ksdevice, linksleep, mtu, netmask, nicdelay, noipv4, noipv6, wepkey
network command can be used both to enable and configure devices. The behaviour has been changing in the course of adoption of NM.
- RHEL 5 - in case of network installation the first
networkcommand from kickstart activates or reactivates (if the device has already been enabled e.g. to get kickstart using default DHCP or configuration given in boot parameters) relevant device with configuration set by the command. For non-network installs (e.g. for media or hd install) the device of the first network command is only configured for target system. Other
networkcommands only set configuration for target system, the devices are not activated 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 configured for the target system. Another difference from RHEL 5 is that the first network command device is activated also for non-network installs .
- RHEL 6.1, Fedora 15/16? - expected behaviour is the same as in RHEL 5 (bug 668395) with option to activate additional devices using new
network --activateoption (bug 638131). Note that the device from first
networkcommand is (re)activated regardless of the option (to keep the behaviour of RHEL 5).
For RHEL 6.0, Fedora 14, and later, devices that are supposed not to be activated in installer and have
onboot option set will be activated just before downloading packages due to ONBOOT side-effect. We have no reports of problems caused by this, but in some cases activation of the device could cause change of routing table making packages inaccessible.
Loader text UI
Serves for selection and/or configuration of a network device that should be enabled in loader. It is skipped 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).
Configuration of selected device:
The IPv6 options correspond to following options of nm-c-e:
- Automatic, DHCP only
Static (Manual) configuration:
- Gateway: entry is used both for IPv4 and IPv6, only one gateway is allowed. Bad, but same as with boot options and kickstart.
- Name Server: entry can contain more name servers separated by comma.
- IPv4 Address: and IPv6 Address: is present only if manual configuration of respective protocol is selected in previous dialog.
TODO limits, problems, need for NM Applet
Text mode UI
Rather limited compared to nm-c-e.
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 is 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
Selection of device to be enabled in installer
This is behaviour in rhel6-branch which should go into rawhide soon (but probably not into F15):
- Automatic use of device on which iBFT with active link was detected.
network --deviceoption. For the first
networkcommand defaults to
ksdeviceboot option, device used to fetch kickstart, or prompt in loder UI (how about detected iBFT device with link?). For next
--deviceoption is mandatory (will be enabled only with
- Dialog in loader UI if none of above applies.
Passing SSID and WEP key with boot parameters or kickstart is supported in Fedora 14. Other methods of authentication can be set in GUI using nm-c-e, although there are some issues with AP selection which should be solved with integration of NetworkManager Applet.
Bugs and issues
- DVD install defaults to ONBOOT=no leaving networking down after reboot - bug 498207. This is rather hot issue. Only devices enabled during install will have set ONBOOT=yes by default. For other devices, the setting has to be configured.
- No more than one device can be activated in installer with kickstart (e.g.: one NIC for repositories, another for iSCSI). Bug 638181. Done in rhel 6.1 - in testing.
- Reading configuration from iBFT in anaconda instead of passing the task to NetworkManager and dracut. Bug 634016. Done in rhel 6.1 - in testing.
- Configuration of successfully activated device in installer environment can't be changed (related bugs: bug 592856, 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. The use case is static configuration with wrong DNS server IP. In this case the device is considered as being successfully activated and user is not given second chance to configure network (for example when adding network repo or iSCSI drive in stage 2). It would be nice to have chance to change network configuration of installer environment at any moment, something like NM systray icon. The question is how to integrate it in anaconda UI, there are UX design concerns and technical concerns (NM Applet's is using freedesktop.org systray interface specification). Other possibility is to add reconfigure option just to places where network can be enabled which is ad hoc solution with issues. I proposed patches for these two approaches (they concern only GUI) on anaconda-devel-list:
IPV4_FAILURE_FATAL=yesby default so ipv4 failing and ipv6 configuration succeeding is considered as failing overall (bug 633815).
- Network installation on IPv6-only networks
/etc/resolv.confis not updated with ipv6 nameserver by NM - bug 672282
gatewayoption is common for ipv4 and ipv6 everywhere but in nm-c-e (bug 562538)
- Support for stateless dhcp6 in loader UI - should happen in nm-c-e first as we provide only subset of it bug 656335
- Check that anaconda works well with new (F15) Consistent Network Device Naming
- [Back] in loader UI, Manual TCP/IP Configuration screen, doesn't work in F15. It does on rhel6-branch so I guess it got screwed up in master by some other patch since I had fixed it (commit ec146852176e2b41ace7725ed8eda337842d3160).
- For media installs sshd can be started uselessly without networking - bug 643738
- Documentation update:
- Fedora - TODO: wiki, Installation Guide
- RHEL: big update posted in https://bugzilla.redhat.com/show_bug.cgi?id=679104
- https://bugzilla.redhat.com/show_bug.cgi?id=647462 (rhel 6.1, F15) -
- https://bugzilla.redhat.com/show_bug.cgi?id=668395 (rhel 6.1, F15) -
- https://bugzilla.redhat.com/show_bug.cgi?id=647462 (rhel 6.1, F15) -