Displaying 3 results from an estimated 3 matches for "unknown_vci".
2014 Mar 09
2
pxelinux.0 not fully booting in EFI 64 mode...not requesting ldlinux.e64 via TFTP...
...EFI PXE boot agent gets confused by this string, even
though
# it's FF-terminated. Per RFC. So it thinks it's pxelinux.0\377 !
(where
# \377 is the FF).
#
#option bootfile-name "efi.x64/pxelinux.cfg/pxelinux.0";
} else {
filename "UNKNOWN_VCI";
option bootfile-name "UNKNOWN_VCI";
}
in legacy PXE mode, wireshark confirms it successfully TFTPs
bios/pxelinux.cfg/pxelinux.0, followed by (in order, all from
bios/pxelinux.cfg/ dir):
ldlinux.c32
<tries other config files>
pxelinux.cfg/default...
2014 Oct 03
1
RE: DHCP option 93 for UEFI
...EClient:Arch:00000:UNDI:002001"
{
option bootfile-name "bios/pxelinux.0";
} elsif option vendor-class-identifier =
"PXEClient:Arch:0007:UNDI:003016" {
option bootfile-name "efi.x64/syslinux.efi";
} else {
option bootfile-name "UNKNOWN_VCI";
}
}
2. Match on arch.
?
# In initial DHCP DISCOVER packet, PXE client sets option 93 to its arch.
# 0000 == IA x86 PC (BIOS boot)
# 0006 == x86 EFI boot
# 0007 == x64 EFI boot
option arch code 93 = unsigned integer 16;
class "pxe-clients" {
match if substring (o...
2014 Mar 09
0
pxelinux.0 not fully booting in EFI 64 mode...not requesting ldlinux.e64 via TFTP...
...EFI PXE boot agent gets confused by this string, even
though
? ? ? ? # it's FF-terminated. Per RFC.? So it thinks it's pxelinux.0\377 !
(where
? ? ? ? # \377 is the FF).
? ? ? ? #
? ? ? ? #option bootfile-name "efi.x64/pxelinux.cfg/pxelinux.0";
? ? } else {
? ? ? filename "UNKNOWN_VCI";
? ? ? option bootfile-name "UNKNOWN_VCI";
? ? }
in legacy PXE mode, wireshark confirms it? successfully TFTPs
bios/pxelinux.cfg/pxelinux.0, followed by (in order, all from
bios/pxelinux.cfg/ dir):
? ? ldlinux.c32
? ? <tries other config files>
? ? pxelinux.cfg/default
? ?...