search for: bootif

Is it normal for pxelinux to append something like BOOTIF=01-aa-bb-cc-dd-ee-ff ? the leading 01- is there in my config file name, but this doesn't seem to be right behaviour. Can someone confirm if this is a bug? I tried this on syslinux 3.21. thanks. -- Ram Yalamanchili

...cation that your network configuration is broken. Using just ip=dhcp on the kernel command line is a preferrable option, or, better yet, run dhcpcd/dhclient, from an initrd if necessary. 2: indicates that an option of the following format should be generated and added to the kernel command line: BOOTIF=hardware-address-of-boot-interface ... in dash-separated hexadecimal with leading hardware type (same as for the configuration file; see pxelinux.doc.) This allows an initrd program to determine from which interface the system booted. So if I want both BOOTIF an ip environment variables I do...

<overly trimmed> On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote: > Ok, so some of this now works, but I'm still having problems. With the > bootif option, the system now correctly configures and uses the same > interface to get its kickstart file. However, when the system is done and > boots up, the interfaces are still messed up. So this is what I have in the > kickstart file: What version of CentOS 6 is this? > In the PXE conf...

...gt; >> Should I be using the device's MAC address when I set the >> 'network' option in the kickstart file? So instead of 'network >> --device=eth0' I make it 'network -device=aa;bb:cc:dd:eee:ff' ? >> > > kickstart has an option: ksdevice=bootif > > I think that'll let you accomplish what you are trying. Totally unrelated, but this is the reason I love discussions like this getting into the archives. I had no idea this option existed and it just solved an annoying problems I've been trying to think how to solve for ages! I...

...ate it based on how anaconda has seen them. In order for this to work on Cent 6 you have to set biosdevname=0 on the kernel boot for the installed system. PXE boot options: label c6inst-sda kernel /linux-boot/cent6-x64/vmlinuz append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg ipappend 2 In kickstart: BOOTOPTS="biosdevname=0" Also in kickstart I do not specify the config for ANY network interfaces. I let anaconda pull in only the config for the boot interface from PXE. I manually...

Ok, so some of this now works, but I'm still having problems. With the bootif option, the system now correctly configures and uses the same interface to get its kickstart file. However, when the system is done and boots up, the interfaces are still messed up. So this is what I have in the kickstart file: # On-Board Port 1 with public IP configuration network --noipv6 --onbo...

...g/01-00-0d-60-d5-d6-3b COM32 Multiboot loader v0.2. Copyright (C) 2005-2006 Tim Deegan. Kernel: boot/xen.gz nosmp noacpi Loading boot/xen.gz....... Module: boot/res-1-kernel ramdisk_size=131072 ramdisk_blocksize=1024 console=tty S0 apm=off id=1 qrm=10.0.1.1 ip=10.0.0.99:10.0.1.1:10.0.0.1:255.0.0.0 BOOTIF=00: 0d:60:d5:d6:3b Loading boot/res-1-kernel........................ Module: boot/res-1-initrd.img Loading boot/res-1-initrd.img................................................... ................................................................................ .........................................

...or this to work on Cent 6 you have to set biosdevname=0 on the >> kernel boot for the installed system. >> >> PXE boot options: >> >> label c6inst-sda >> kernel /linux-boot/cent6-x64/vmlinuz >> append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif >> ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg >> ipappend 2 >> >> In kickstart: >> >> BOOTOPTS="biosdevname=0" >> >> Also in kickstart I do not specify the config for ANY network >> interfaces. >> I...

...n them. > > In order for this to work on Cent 6 you have to set biosdevname=0 on the > kernel boot for the installed system. > > PXE boot options: > > label c6inst-sda > kernel /linux-boot/cent6-x64/vmlinuz > append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif > ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg > ipappend 2 > > In kickstart: > > BOOTOPTS="biosdevname=0" > > Also in kickstart I do not specify the config for ANY network interfaces. > I let anaconda pull in only the config for the bo...

...t;gw-ip>:<netmask> Is there a way to tell ipappend to assign these to individual arguments. Or does anyone know a good way to parse each of these to individual variables in dos. What I want to get is clientip= bootserver= gw= netmask= And for the MAC the format is something like BOOTIF=00-00-00-00-00... Anyone know how to strip out the dashes. Thanks -Aaron

...again in the second phase. Here is where the trouble starts. The --device= cannot handle MAC addresses, in other words if we ommit the --device= parameter we get a list of interfaces, which we do not want because the list does not indicate which one is the right interface. Using ksdevice=bootif and providing BOOTIF=MAC-ADDRESS on the commandline does not help either because the second phase always wants to reconfigure the network. In fact we don't want the second phase to reconfigure the network, we want it to keep the working network configuration from the first phase which w...

...t; ]; then + . ${vendor_script} + vendor_pre_hook + fi + if [ -z "$ip_netmask" ]; then ip_netmask=$netmask fi @@ -379,7 +397,8 @@ start() { ip_gateway=$gateway fi # save boot parameters as defaults for ovirt-config-* - params="bootif init vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_data_size local_boot standalone overcommit ip_address ip_netmask ip_gateway ipv6 dns ntp vlan ssh_pwauth syslog_server syslog_port collectd_server collectd_port bootparams hostname firstboot" + # and allow v...

...lookup to work and I'm hoping you can help! My pxelinux.cfg/default file is as follows: ======================= default linux prompt 0 timeout 1 label linux kernel /images/Centos-5.4-x86_64/vmlinuz ipappend 2 append initrd=/images/Centos-5.4-x86_64/initrd.img ksdevice=bootif text serial=tty0 kssendmac ks=http://edison/api/kickstart/ ======================= However the image that pxeboots doesn't appear to support DNS lookups, regardless of the fact that my DHCP config pushes a DNS Server out to the PXE Client (proven using a liveCD running dhclient against the sa...

...log=*) i=${i#syslog=} eval $(printf $i|awk -F: '{print "syslog_server="$1; print "syslog_port="$2;}') @@ -365,7 +370,7 @@ start() { ip_gateway=$gateway fi # save boot parameters as defaults for ovirt-config-* - params="bootif init vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_data_size local_boot standalone overcommit ip_address ip_netmask ip_gateway ipv6 dns ntp syslog_server syslog_port collectd_server collectd_port bootparams hostname firstboot" + params="bootif init vol_...

...t; the >>>> kernel boot for the installed system. >>>> >>>> PXE boot options: >>>> >>>> label c6inst-sda >>>> kernel /linux-boot/cent6-x64/vmlinuz >>>> append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif >>>> ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg >>>> ipappend 2 >>>> >>>> In kickstart: >>>> >>>> BOOTOPTS="biosdevname=0" >>>> >>>> Also in kickstart I do not speci...

I have a Dell server that has two built-in ethernet devices. When I kickstart the machine, they are correctly identified as eth0 and eth1 (correctly meaning they correspond to the physical device ports 1 and 2). I need a third one and want that to come up as eth2. After adding the hardware, kickstart now fails because for some reason it goes through a rename process where it makes the newly added

FYI -------- Original Message -------- Subject: IPAPPEND on http://syslinux.zytor.com/faq.php#config Date: Mon, 31 Jan 2005 15:20:00 +0100 From: Pascal Terjan <pterjan at mandrakesoft.com> Organization: Mandrakesoft To: david at weekly.org Hi, I needed to get the MAC from which we booted using pxelinux (in order to know which interface we used to boot). I found reading the source that

Version 6.6 ... On Wed, Feb 25, 2015 at 1:17 PM, Jim Perrin <jperrin at centos.org> wrote: > <overly trimmed> > > On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote: > > Ok, so some of this now works, but I'm still having problems. With the > > bootif option, the system now correctly configures and uses the same > > interface to get its kickstart file. However, when the system is done and > > boots up, the interfaces are still messed up. So this is what I have in > the > > kickstart file: > > What version of CentOS 6 i...

...to IPAPPEND, cuz I commented that out as a test. working: Kernel command line: console=ttyS0,19200n81 initrd=initrd.img-2.6.8-1-386 root=/dev/ram0 nfsaddrs=10.10.10.100:10.10.10.2:10.10.10.2:255.255.255.0:soekris:eth0 nfsroot=10.10.10.2:/nfshost/truck panic=10 BOOT_IMAGE=vmlinuz-2.6.8-1-386 BOOTIF=01-00-00-24-c2-46-c8 failing - no initrd download Kernel command line: console=ttyS0,19200n81 root=/dev/nfs nfsaddrs=10.10.10.100:10.10.10.2:10.10.10.2:255.255.255.0:soekris:eth0 nfsroot=10.10.10.2:/nfshost/truck panic=15 BOOT_IMAGE=vmlinuz-2.6.8-1-386 BOOTIF=01-00-00-24-c2-46-c8 Im not much...

Greetings all, Is there currently any mechanism in pxelinux the would send a mac address of the pxe booted interface through to the linux kernel much like ipappend can send the ip address? Kickstarting a system with multiple interfaces can be troublesome. ksdevice is helpful but only in some circumstances such as forcing eth0, but that doesn't always work since probe order changes depending