My existing network environment provides the following:DHCP server that sends PXE clients to a particular TFTP serverTFTP server with SYSLINUX pxelinux.0 file for bootingThe SYSLINUX installation defaults on timeout to boot from local disk, which allows existing clients to reboot correctly but also provides for the option of booting into a rescue or provisioning environment.I am testing a new provisioning environment which resides on a different TFTP server than the one pointed to by the DHCP server. Existing clients depend upon the current environment, but I'd like to refer test clients to the new TFTP server for provisioning.Ideally I'd like to be able to use a particular menu option from the SYSLINUX prompt that would cause the client to boot from another (hardcoded, rather than DHCP-server-provided) TFTP server.I tried installing a custom gPXE image as a menu option on SYSLINUX. The custom image (re-)acquired a DHCP address and went to the hardcoded TFTP server, but it's missing a piece that I don't think gPXE is capable of fulfilling.The new provisioning system is based upon Cobbler, and it depends upon the usual PXE sequence where the client looks for a file named with its MAC address before settling for a less-specific, and eventually generic, file. From what I can tell, it appears that gPXE isn't capable of doing this mac-address-based boot sequence. Can anyone tell me of another way to do this? I've been banging my head for several days on this problem. Thanks in advance!
PXE boot chaining to hardcoded TFTP server?
dhcp;pxe;tftp