Red Hat Bugzilla – Bug 475844
Anaconda ignores network=bootif
Last modified: 2008-12-10 14:29:45 EST
Description of problem:
Anaconda seems to ignore the network=bootif option described in https://fedoraproject.org/wiki/Anaconda/Options as: "BOOTIF command line option will be used to locate the boot interface. BOOTIF is automagically supplied by pxelinux when you include the option 'IPAPPEND 2' in your pxelinux.cfg file".
Version-Release number of selected component (if applicable):
18.104.22.168 (Fedora 10 release)
Steps to Reproduce:
1. Set "ipappend 2" option in pxelinux configuration and add "network=bootif" to the kernel command line.
2. Boot over the network on a machine that has both an eth0 and a wlan0 interface.
Anaconda asks whether to install using eth0 or wlan0.
Anaconda should automagically use the device that pxelinux adds to the kernel command line.
Anaconda reports that the kernel command line is as follows:
initrd=f10-i386/initrd.img network=bootif ks=nfs:10.0.0.10:/install/f10-i386.ks BOOTIF=01-00-13-77-d0-6d-75 BOOT_IMAGE=f10-i386/vmlinuz
The BOOTIF option was added automatically by pxelinux. I'm not sure if it's relevant that BOOTIF uses hyphens instead of colons to separate the bytes in the MAC address.
Please let me know if there is any additional information that would be helpful.
The boot parameter is: