Pro legacy mam pxelinux a pro uefi pak syslinux, ale v konfiguraci DHCP je treba dulezite toto pro BIOS+UEFI, viz zdroj informaci v odkazu v komentari:
# Provide PXE clients with appropriate information
class "pxeclient" {
match if substring(option vendor-class-identifier, 0, 9) = "PXEClient";
# vendor-option-space PXE;
# At least one of the vendor-specific PXE options must be set in
# order for the client boot ROMs to realize that we are a PXE-compliant
# server. We set the MCAST IP address to 0.0.0.0 to tell the boot ROM
# that we can't provide multicast TFTP.
# option PXE.mtftp-ip 0.0.0.0;
# This is the name of the file the boot ROMs should download.
# filename "/pxe/pxelinux.0";
next-server 192.168.68.5;
}
### # Provide Etherboot clients with appropriate information
### class "etherboot" {
### match if substring(option vendor-class-identifier, 0, 9) = "Etherboot";
### filename "vmlinuz_arch";
### }
# 2/2 of https://wiki.syslinux.org/wiki/index.php?title=PXELINUX#UEFI
class "pxeclients" {
match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
# About "architecture-type":
# 06 (EFI IA32) is sometimes (mis)used for legacy (CSM) boot of x64 machines by some vendors.
# 07 (EFI BC) is sometimes (mis)used for EFI x64 boot by some vendors.
if option architecture-type = 00:00 {
filename "pxe-bios/pxelinux.0";
} elsif option architecture-type = 00:09 {
filename "pxe-uefi-x64/syslinux.efi";
} elsif option architecture-type = 00:07 {
filename "pxe-uefi-x64/syslinux.efi";
} elsif option architecture-type = 00:06 {
# should be 32bit version
filename "pxe-uefi-ia32/syslinux.efi";
}
}
Zobrazit příspěvky
