search for: 002001

...2 8384 8586 8739 0204 ec61 1100 C........9...a.. 0x0130 997e 931d 3d06 d511 a800 accd f1ea 391d .~..=.........9. 0x0140 5d02 0000 5e03 0102 013c 2050 5845 436c ]...^....<.PXECl 0x0150 6965 6e74 3a41 7263 683a 3030 3030 303a ient:Arch:00000: 0x0160 554e 4449 3a30 3032 3030 31ff 0000 0000 UNDI:002001..... 0x0170 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0180 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0190 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x01a0 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x01b0 0000 0000 0000 0000 0000 0...

...t"; set vendor-string = substring ( option vendor-class-identifier, 0, 9); set vendor-class option vendor-class-identifier; option tftp-server-name "192.168.0.100"; next-server 192.168.0.100; if option vendor-class-identifier = "PXEClient: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...

----- Original Message ----- From: Gene Cumm <gene.cumm at gmail.com> > It's been a while since I used Yahoo but I didn't think I had > that issue.? GMail does default to top-posting Doing it manually... didn't find that option. > Perhaps also try -o 43.x=01:04:0a:d7:90:3c:ff (which will set the > mtftp option) in addition to -W. Tried it but still the same error.

...5 ??????????? MSZ Option 57, length 2: 1260 ??????????? GUID Option 97, length 17: 0.0.12.143.150.232.29.178.17.128.0.154.39.8.20.171.64 ??????????? ARCH Option 93, length 2: 0 ??????????? NDI Option 94, length 3: 1.2.1 ??????????? Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001" 13:24:05.680362 IP (tos 0x10, ttl? 16, id 0, offset 0, flags [none], proto: UDP (17), length: 328) 10.215.144.7.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x55d9d42f, secs 4, Flags [ Broadcast ] (0x8000) ????????? Your-IP 10.215.145.94 ????????? Client...

...ooks like this: # 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; ... #if option vendor-class-identifier = "PXEClient:Arch:00000:UNDI:002001" { if option arch = 00:00 { filename "bios/pxelinux.cfg/pxelinux.0"; # option 67. A string. full path to NBP. option bootfile-name "bios/pxelinux.cfg/pxelinux.0"; #} elsif option vendor-class-identifier = "PXEClient:Arch:0007:UNDI:0030...

...it's unofficially version 3. That's the firmware version. (I'm sure it's based on Intel's reference PXE implementations. All PXE ROMs seem to be.) My clients report 2.01 for their firmware version, when doing BIOS. i.e. Vendor Class Identifier == PXEClient:Arch:00000:UNDI:002001 And 3.16 when doing UEFI 64 bit. I.e., Vendor Class Identifier == PXEClient:Arch:0007:UNDI:003016 Spike

...ooks like this: # 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; ... ? ? #if option vendor-class-identifier = "PXEClient:Arch:00000:UNDI:002001" { ? ? if option arch = 00:00 { ? ? ? filename "bios/pxelinux.cfg/pxelinux.0"; ? ? ? # option 67. A string. full path to NBP. ? ? ? option bootfile-name "bios/pxelinux.cfg/pxelinux.0"; ? ? #} elsif? option vendor-class-identifier = "PXEClient:Arch:0007:UNDI:0030...

On Thu, Nov 27, 2014 at 8:59 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote: > Gene, > > As it happened I started working on this again just as you mailed me. I saw it in IRC. > It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no

...filename = "sis900.zpxe"; # } #} # Uncomment the following to get the debug/verbose messages in system log. The messages like the following will be shown: # Client 0:c:29:3b:34:fb requests 1:2:3:5:6:b:c:d:f:10:11:12:2b:36:3c:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id # Client 0:c:29:3b:34:fb requests 1:3:6:c:f:1c:28:29:2a - DRBLClient - no dhcp-client-id # Begin of log command log-facility local7 ; log(info, concat("Client ", binary-to-ascii(16, 8, ":", substring(hardware, 1, 6)), " requests ",...

Gene, As it happened I started working on this again just as you mailed me. It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no joy. The bootfile size shows up as zero because that relates to "option boot-size" in dhcp and doesn't seem to

On 2014/3/7 ?? 05:23, Gene Cumm wrote: > On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> Sorry for the confusion, I am actually using 6.02. It turns out that I was >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to >> using "syslinux64.efi" but it hangs during boot, just before loading the >>

...filename = "sis900.zpxe"; # } #} # Uncomment the following to get the debug/verbose messages in system log. The messages like the following will be shown: # Client 0:c:29:3b:34:fb requests 1:2:3:5:6:b:c:d:f:10:11:12:2b:36:3c:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id # Client 0:c:29:3b:34:fb requests 1:3:6:c:f:1c:28:29:2a - DRBLClient - no dhcp-client-id # Begin of log command log(info, concat("Client ", binary-to-ascii(16, 8, ":", substring(hardware, 1, 6)), " requests ", binary-to-ascii...