In
https://docs.centos.org/en-US/centos/install-guide/pxe-server/#chap-installation-server-setup
they show the following example for setting dhcpd.conf to point to the
tftp server for pxe booting:
option space pxelinux;
option pxelinux.magic code 208 = string;
option pxelinux.configfile code 209 = text;
option pxelinux.pathprefix code 210 = text;
option pxelinux.reboottime code 211 = unsigned integer 32;
option architecture-type code 93 = unsigned integer 16;
subnet 10.0.0.0 netmask 255.255.255.0 {
option routers 10.0.0.254;
range 10.0.0.2 10.0.0.253;
class "pxeclients" {
match if substring (option vendor-class-identifier, 0, 9) =
"PXEClient";
next-server 10.0.0.1;
if option architecture-type = 00:07 {
filename "shim.efi";
} else {
filename "pxelinux/pxelinux.0";
}
}
}
If the server is a different one, how would the option
architecture-type{} change to reflect the file location?
On Sun, Feb 23, 2020 at 09:10:18PM -0500, Mauricio Tavares wrote:> if option architecture-type = 00:07 { > filename "shim.efi"; > } else { > filename "pxelinux/pxelinux.0"; >} > } >} > >If the server is a different one, how would the option >architecture-type{} change to reflect the file location?It wouldn't change at all. The specified file name is written as-is into the DHCP reply. The client will look for the file on the TFTP server specified by next-server. More recent UEFI implementations (arch ID 0x0010, I think) also accept HTTP URLs as file names. Those would contain the host name. Not relevant to your snippet though.