search for: proxydhcp

>>> The real DHCP server supplies client ip address only. Everything else comes from proxyDHCP. The proxyDHCP server supplies boot file name, boot file (syslinux.efi), boot loader (ldlinux.e64), config file, tinycore and OS image files. <<< This is not completely correct: your DHCP server provides an IP and your proxyDHCP server only processes a complementary DHCP transaction...

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 serve...

Patrick, I think I've been able to figure out some missing details about your VMware Workstation tests. For a proxyDHCP, I'm using dnsmasq. Could you try to confirm your test was the same basic setup? On VMware Workstation 10 with a VMHWv10 VM set to EFI firmware for x64, I've been able to get mixed results, depending on if a gateway is provided. With a VMHWv9 VM, I see what appear to be the issues you se...

On Wed, Jun 3, 2015 at 3:25 PM, Jeff via Syslinux <syslinux at zytor.com> wrote: > The UEFI PXE boot DHCP/proxyDHCP issue is very timely. I am working on > that very topic now. > Our environment: > The real DHCP server supplies client ip address only. Everything else > comes from proxyDHCP. > Problem 2: > > The next problem is packet parsing and incomplete ip address sets on the > sysl...

from: Jeff Sloan <jeff_sloan at selinc.com> Update UEFI PXE proxyDHCP handling updated. This patch is based on commit ID 8a00e49 Updated pxe.c and udp.c to incorporate feedback.In addition to the previous modifications: pxe.c: Changed to use ProxyOffer Packet and added client ip from PxeReply into temp packet for parsing. Left all existing cached packets untouc...

On Sun, Jun 7, 2015 at 5:09 PM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > Patrick, I think I've been able to figure out some missing details > about your VMware Workstation tests. For a proxyDHCP, > I'm using dnsmasq. Could you try to confirm your test was the > same basic setup? > > On VMware Workstation 10 with a VMHWv10 VM set to EFI > firmware for x64, I've been able to get mixed results, depending on if agateway is provided. > > With a VMHWv9 VM, I see...

>>> Patrick, I think I've been able to figure out some missing details about your VMware Workstation tests.? For a proxyDHCP, I'm using dnsmasq.? Could you try to confirm your test was the same basic setup? On VMware Workstation 10 with a VMHWv10 VM set to EFI firmware for x64, I've been able to get mixed results, depending on if agateway is provided.? With a VMHWv9 VM, I see what appear to be the issues...

...PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sun, Jun 7, 2015 at 5:09 PM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>>> >> Patrick, I think I've been able to figure out some missing details >> about your VMware Workstation tests. For a proxyDHCP, >> I'm using dnsmasq. Could you try to confirm your test was the >> same basic setup? >> >> On VMware Workstation 10 with a VMHWv10 VM set to EFI >> firmware for x64, I've been able to get mixed results, depending on if agateway is provided. >> >...

...lt;gene.cumm at gmail.com> > To: jeff_sloan at selinc.com, > Cc: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com>, > masotta <masottaus at yahoo.com> > Date: 06/26/2015 09:13 AM > Subject: Re: [PATCH 0/1] Network UEFI PXE DHCP/proxyDHCP fix > ________________________________ > > > > On Fri, Jun 26, 2015 at 8:58 AM, <jeff_sloan at selinc.com> wrote: >> from: Jeff Sloan <jeff_sloan at selinc.com> >> >> Update UEFI PXE proxyDHCP handling updated. >> >> This patch is based on c...

...&mode->ProxyOffer.Dhcpv4; else pkt_v4 = &mode->DhcpAck.Dhcpv4; this code is used in C:\UDK2014.SP1.P1.Complete\MyWorkSpace\NetworkPkg\UefiPxeBcDxe\PxeBcBoot.c / PxeBcDhcp4BootInfo() when looking for boot info. I agree it is not 100% clear but it could be necessary on non proxyDHCP situations. i.e when the PXE info is contained within the DHCP OFFER/ACK I do not know if in that particular case some FWs probably do not populate the ProxyOffer pkt. In those cases the last "else" would be necessary. Best, Patrick

...asic layout of your PXE system would be > helpful, including: > > - Make/model of system > - UEFI firmware revision > - What NIC type and port number? > - UEFI extension agents (struggling to recall the proper term; > comparable to a BIOS PXE OROM for add-in cards) > - Was a proxyDHCP/PXE server involved in addition to DHCP? > - TFTP or HTTP transfer - TFTP/HTTP on a unique server or on the DHCP server or proxyDHCP/PXE server? - Where do the DHCP server, proxyDHCP/PXE server, and TFTP/HTTP server live relative to the client and each other (ie different subnets)? > - Wha...

...> else > pkt_v4 = &mode->DhcpAck.Dhcpv4; > > this code is used in > C:\UDK2014.SP1.P1.Complete\MyWorkSpace\NetworkPkg\UefiPxeBcDxe\PxeBcBoot.c / PxeBcDhcp4BootInfo() > when looking for boot info. > I agree it is not 100% clear but it could be necessary on non proxyDHCP situations. > i.e when the PXE info is contained within the DHCP OFFER/ACK I do not know if in that > particular case some FWs probably do not populate the ProxyOffer pkt. > In those cases the last "else" would be necessary. Such a change makes 0 sense. 1) We already parsed tha...

On Fri, Jun 26, 2015 at 8:58 AM, <jeff_sloan at selinc.com> wrote: > from: Jeff Sloan <jeff_sloan at selinc.com> > > Update UEFI PXE proxyDHCP handling updated. > > This patch is based on commit ID 8a00e49 This commit is outdated. Could you try commit ID 23b2707b as-is first? Thanks. > Updated pxe.c and udp.c to incorporate feedback.In addition to the previous > modifications: > > pxe.c: Changed to use ProxyOffer Pac...

...=Vendor class identifier: "PXEClient:Arch:00006:UNDI:003016" I've performed a deeper analysis and this is what's going on. The client get's its IP from VMware DHCP server, the ACK includes NextServer=192.168.62.254 (the DHCP Server IP) The client gets PXE parameters from a proxyDHCP NextServer=192.168.62.1 (the PXE Server IP) While the NBP syslinux.efi is correctly retrieved considering the PXE parameters given by the proxyDHCP (192.168.62.1) the TFTP request of the file ldlinux.e32 is performed with the data included in the DHCP answer (192.168.62.254) instead. That's wh...

On Mon, Jun 8, 2015 at 4:07 PM, <jeff_sloan at selinc.com> wrote: > Gene, > Where do you keep the development tree? It's probably staring me in the face > but I can't find any updates beyond initial 6.03. Officially listed at http://www.syslinux.org/wiki/index.php/Development The primary repo at kernel.org is behind. The development repo at zytor.com is up to date but

On Thu, Jun 11, 2015 at 4:02 PM, <jeff_sloan at selinc.com> wrote: > from: Jeff Sloan <jeff_sloan at selinc.com> > > Update UEFI PXE proxyDHCP handling. > > This patch is based on commit ID 8a00e49 > > Modify two files to specify valid ip addresses. These files are efi/pxe.c > and efi/udp.c. 1) In commit 2e266c35, I proposed using UseDefaultAddress. As I recall, there were clients that didn't utilize the default routi...

...Machine 2: Originally had: MBA: 3.2, PXE: 1.99J MAC: 00:50:da:64:41:54 Would not respond to the DHCP Server I upgraded the firmware to: MBA: 4.3, PXE: 2.20 MAC: 00:50:da:64:41:54 Now I get the following messages: Client ID: 192.168.104.56 Netmask: 255.255.255.0 DHCP 192.169.104.141 PXE-E55 ProxyDHCP No reply to request on Port 4011 It appears that I am missing something but I am not sure what since one machine works fine but the other one does not. Any Ideas?? Steve Oliphant Novadigm, Inc. 201-512-7821

...ic layout of your PXE system would be > helpful, including: > > - Make/model of system > - UEFI firmware revision > - What NIC type and port number? > - UEFI extension agents (struggling to recall the proper term; > comparable to a BIOS PXE OROM for add-in cards) > - Was a proxyDHCP/PXE server involved in addition to DHCP? > - TFTP or HTTP transfer > - TFTP/HTTP on a unique server or on the DHCP server or proxyDHCP/PXE server? - Where do the DHCP server, proxyDHCP/PXE server, and TFTP/HTTP server live relative to the client and each other (ie different subnets)? >...

from: Jeff Sloan <jeff_sloan at selinc.com> Update UEFI PXE proxyDHCP handling. This patch is based on commit ID 8a00e49 Modify two files to specify valid ip addresses. These files are efi/pxe.c and efi/udp.c. In efi/pxe.c: In net_parse_dhcp function. If ProxyOffer has been received, start with DhcpAck packet since it is the most complete. This requires a minim...

...TP, even if it doesn't support MTFTP and all that. > > Cheers, > > Luke Luke, I have considerable experience with this. We use WDS at work for PXE (MS-centric shop). I use pxelinux at home. I've got WDS working in our test lab w/ UEFI. As you state, it strongly wishes to do proxyDHCP (port 4011). More on this in a bit. It's quite common to segregate the DHCP server from the TFTP server. Commonly, it's because DHCP services is maintained why one team and PXE boot by another. What you're desiring is somewhat obscure -- you're wanting your WDS server to provide...