Bug 1110540

Summary: No IPv4/IPv6 NIC configuration from the commandline
Product: [Fedora] Fedora Reporter: A.J. Werkman <aj.werkman>
Component: dracutAssignee: dracut-maint-list
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 22CC: dracut-maint-list, harald, jonathan, xenoson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 19:29:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description A.J. Werkman 2014-06-17 21:16:13 UTC
Description of problem:
It is not possible to configure both IPv4 and IPv6 from the kernel commandline

Version-Release number of selected component (if applicable):
Rawhide

How reproducible:
Everytime

Steps to Reproduce:
1. Using the next grub entry
menuentry 'Local Fedora rawhide' --class fedora --class gnu-linux --class gnu --class os {
	set root=(hd0,3)
	echo 'Start Local installatie ...'
	linuxefi /images/pxeboot/vmlinuz ip=212.115.199.60::212.115.199.57:255.255.255.248:testsys.digifarma.nl::off ip=[2001:1af8:fe00:847f::4]::[2001:1af8:fe00:847f::1]:64:testsys.digifarma.nl::off nameserver=212.115.199.57 inst.stage2=hd:UUID=9cb02c12-71bf-49ef-9a9d-092923e0babd
	echo 'Initrd laden ...'
	initrdefi /images/pxeboot/initrd.img
}
2. boot the kernel
3. Error configuring NIC

Actual results:
NIC is not configured

Expected results:
NIC should be configured with both IPv4 and IPv6 address

Additional info:
When using the example, the error is that no device is specified.

When puting the devicename in both 'ip=' statements, the error is that a device can only be configured once.

Comment 1 Harald Hoyer 2014-06-25 09:57:35 UTC
Do you need _both_ to boot from PXE? If so, why?

Comment 2 A.J. Werkman 2014-06-25 10:30:35 UTC
Don't think so. But that is not the reason to use this.

I want to install Fedora dual stack. The command-line is where I supply the NIC data for an unattended installation.

Supplying this info in kickstart does not seem to work either, so I have to tell it to anaconda somewhere.

From a user experience point of view, it also feels 'silly' to supply IPv4 on the command-line and IPv6 in the UI.

Further I can imagine (maybe far fetched) to boot of of a server in IPv4, but having the install tree on IPv6. After all it is dual stack.

Comment 3 xenoson 2014-09-20 22:15:18 UTC
It can be necessary to provide network config to dracut for example for encrypted systems like here:
https://bugzilla.redhat.com/show_bug.cgi?id=524727

Per default dracut overwrites the network config in the root if it was configured via boot parameters.
I learned from here 
http://www.spinics.net/lists/linux-initramfs/msg03687.html
that 
sudo systemctl mask fedora-import-state.service
(or rhel-import-state.service)
disables this and the /etc/sysconfig/ifcfg-* stays intact.

But NetworkManager inherits the connection profile from dracut (not shure from where, could be that it reads /run/initramfs/state/etc/sysconfig/network-scripts/ifcfg-*) and always activates this particular profile at boot time.

Is there any way to give NetworkManager another connection profile name to activate at boot time? Would be a helpful feature enhancement even if dracut would allow dual stack.

The only workaround I found was to put this into rc.local
nmcli dev disconnect netif0
nmcli con del netif0
nmcli con up static

netif0 is the name given via ifname=netif0:macaddress
static is the NAME= in the ifcfg-netif0

This is the only way that ipv6 config from ifcfg-netif0 and custom routes from route-netif0 get applied.

Comment 4 Jaroslav Reznik 2015-03-03 16:02:36 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 5 Fedora End Of Life 2016-07-19 19:29:48 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.