search for: 81eeaa3

...e request) sent to the wrong MAC address (MAC address of gateway) VMHWv10, Host-Only, 6.03: success VMHWv9, NAT: Same as VMHWv10 VMHWv9, Host-Only, 6.03: Syslinux appears deaf; no ARP response, no TFTP acknowledgement after receiving the first packet of a file request. VMHWv9, Host-Only, Commit 81eeaa3: Same as 6.03. -- -Gene

...s of gateway) > > VMHWv10, Host-Only, 6.03: success > > VMHWv9, NAT: Same as VMHWv10 > > VMHWv9, Host-Only, 6.03: Syslinux appears deaf; no ARP > response, no TFTP acknowledgement after receiving the first packet of a > file request. > > VMHWv9, Host-Only, Commit 81eeaa3: Same as 6.03. > > -- > -Gene > <<< > > Are you testing with the patch applied or without? > As clients I'm using Workstation 10 VMs (32/64bit) and a real Toshiba notebook. > When the client is a VM the DHCP server is VMware's, When the client is a real &g...

..., Host-Only, 6.03: success >> >> VMHWv9, NAT: Same as VMHWv10 >> >> VMHWv9, Host-Only, 6.03: Syslinux appears deaf; no ARP >> response, no TFTP acknowledgement after receiving the first packet of a >> file request. >> >> VMHWv9, Host-Only, Commit 81eeaa3: Same as 6.03. >> >> -- >> -Gene >> <<< >> >> Are you testing with the patch applied or without? >> As clients I'm using Workstation 10 VMs (32/64bit) and a real Toshiba notebook. >> When the client is a VM the DHCP server is VMware'...

...sent to the wrong MAC address (MAC address of gateway) VMHWv10, Host-Only, 6.03: success VMHWv9, NAT: Same as VMHWv10 VMHWv9, Host-Only, 6.03: Syslinux appears deaf; no ARP response, no TFTP acknowledgement after receiving the first packet of a file request. VMHWv9, Host-Only, Commit 81eeaa3: Same as 6.03. -- -Gene <<< Are you testing with the patch applied or without? As clients I'm using Workstation 10 VMs (32/64bit) and a real Toshiba notebook. When the client is a VM the DHCP server is VMware's, When the client is a real notebook the DHCP server is an externa...

...ess and populate missing correct ip addresses. Details and > code below. > > My approach: > Thoughts? 1) It's not a diff. 2) What exact version or commit ID is this patch attempt based on? 3) If you have a system that successfully can build Syslinux EFI, have you tried commit ID 81eeaa3? -- -Gene

The UEFI PXE boot DHCP/proxyDHCP issue is very timely. I am working on that very topic now. Our scenario is a manufacturing environment set up to format and load/install custom hard drive images in our systems. Our environment: This is a manufacturing floor setup where we build computers for our customers. We have two servers and a client in the mix, all connected via Ethernet (IPv4 only).