similar to: Locally-loaded syslinux.efi with remote HTTP config?

On Sat, Jun 18, 2016 at 4:09 AM, Geert Stappers via Syslinux <syslinux at zytor.com> wrote: > On Fri, Jun 17, 2016 at 07:27:17PM -0500, Alexander Perlis via Syslinux wrote: >> Question: >> If syslinux.efi is loaded locally off USB rather than via an EFI >> PXE option ROM boot, but on a client whose EFI firmware has TCP >> support, should that locally-booted

On Fri, Jun 17, 2016 at 07:27:17PM -0500, Alexander Perlis via Syslinux wrote: > Question: > If syslinux.efi is loaded locally off USB rather than via an EFI > PXE option ROM boot, but on a client whose EFI firmware has TCP > support, should that locally-booted syslinux.efi be able to process > HTTP URLs? Initial experiments indicate "no", but why not? > >

Hello dear list, Using VMware I built a test setup of a server with dhcp, tftp and a http-server and several pxe-clients with EFI mode turned on. This setup worked, albeit with the exponential-like decay of IO rate I described earlier. The work-around of using HTTP works beautifully though. So it was time for the next step. Migrate this setup to our automated testing environment that runs

> > Is syslinux.efi supposed to be able to handle HTTP URLs? > > If the underlying firmware can. Try just specifying an HTTP URL in the > config or on the command line instead of the path-prefix option. Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. Somehow I was under the impression improvements from pxelinux variants like lpxelinux were

>> Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. > > There's a lot of variation. Do you have a shell option > in your boot selections? None of Dell OptiPlex 990 (firmware A19), 9010 (firmware A22), nor 9020 (firmware A16) seem have a built-in EFI shell option, but in all three cases I had success running the external EFI shell from

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

>First, I was looking for the actual values.? >For a VM with (among other values): > config.version = "8" > virtualHW.version = "10" > ethernet0.virtualDev = "e1000" > guestOS = "rhel6-64" > firmware = "efi" > I see: > option-93 = 0x07 > option-60 ="PXEClient:Arch:00007:UNDI:003016" OK I take

> Date: Thu, 25 Dec 2014 07:07:52 +0000 > From: Luke Ledgerd <luke.ledgerd at niteco.se> > To: "syslinux at zytor.com" <syslinux at zytor.com> > Subject: [syslinux] Chain-loading from WDS to PXELinux on a different > tftp server > Message-ID: <17ba7ad419d54b6cab685c2cedc3de95 at NI-MAILEX.niteco.se> > Content-Type: text/plain;

Hi, I'm trying to boot 64bit version of syslinux.efi through network. But booting is freezes with following message: Getting cached packets My IP is X.X.X.X the last file that was requested through tftp is syslinux.efi. I'm using precompiled binary from official syslinux-6.02.tar.gz. Here is the dump in ASCII - http://brom.in/dumps/syslinux-20131220.txt Any help is appreciated.

On Sat, Jan 10, 2015 at 5:44 AM, Patrick Masotta <masottaus at yahoo.com> wrote: >> I use Syslinux 6.03 EFI64 on a VMware Workstation 10 VM on >> 10.0.2 on Linux. >> > w/o any problem? Yes. > Me too, I just send the ""corresponding"" syslinux.efi >> Are they actually transferring the syslinux.efi files? > > sure > >> What

On Wed, Oct 7, 2015 at 6:09 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> -----Original Message----- >> From: Gene Cumm [mailto:gene.cumm at gmail.com] >> Sent: Wednesday, October 07, 2015 4:43 PM >> To: For discussion of Syslinux and tftp-hpa; Geert Stappers >> Subject: Re: [syslinux] UEFI: Failed to load ldlinux.e64/ldlinux.e32 >> >> On Wed, Oct

> I use Syslinux 6.03 EFI64 on a VMware Workstation 10 VM on > 10.0.2 on Linux. > w/o any problem? >> correctly sends back w/o error the "corresponding" syslinux.efi >> "EFI BC" -> EFI64\syslinux.efi >> "EFI IA32"-> EFI32\syslinux.efi >I only send back 1 filename. > Me too, I just send the

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 minimum of changes to the

Thanks for your email. Yes it does provide some insight into why I could hack a Linux DHCP server into providing enough PXE boot information for PXE 3 clients but PXE 2.1 were happy (ROMs under many circumstances need to use proxy dhcp 4011 - as documented by IBM on the link I shared earlier). It appears only the most latest Dell business systems have EFI 64 support, and the best you can expect

> Some magic in dhcpd.conf: > > if option architecture-type = 00:09 { > filename "efi64/syslinux-87020-or.efi"; > option pxelinux.pathprefix "http://bla/efi64/"; > } elsif option > architecture-type = 00:07 { > filename "efi64/ipxe-git87981.efi"; > } else { > filename

On 31-07-15 14:25, Patrick Masotta wrote: > ""exponential-like decay of IO rate"" could you please post a link on > your comments on this? Sure, see the thread starting at: http://www.syslinux.org/archives/2015-June/023621.html And Gene's confirmation at: http://www.syslinux.org/archives/2015-June/023629.html > OK I got lost. > are you saying you finally

Hi all, I currently use iPXE to load memdisk and, subsequently, a FreeBSD disk image to perform an OS installation to disk. This works great in BIOS, but upcoming requirements make UEFI a prerequisite. Because memdisk is not UEFI-aware, new UEFI-aware media is necessary. The current plan is to integrate the installation scripts (currently in the hard drive image) into a bootable FreeBSD ISO

On 31-07-15 18:45, Patrick Masotta wrote: >>>> > Is this possible? Are you saying the FW is stealing the DHCP response > away before iPXE gets it? I haven't thought of this possibility. > > Or am I misunderstanding you? > <<< > > I'm saying that "probably" iPXE is trigerring a new PXE sequence with a different arch but > the one

On 2019-12-13 08:36, Gregory Lee Bartholomew via Syslinux wrote: > On Fri, 2019-12-13 at 08:47 +0100, jps--- via Syslinux wrote: >> Hi, >> >> We are currently testing PXE booting with syslinux.efi in UEFI mode. >> This is working fine. >> However the loading of syslinux.efi and the config files is still using >> TFTP protocol, the rest kernel and initrd is

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