similar to: Confusion on lpxelinux vs. gpxelinux vs. ipxe vs gpxe.

On 06/16/2014 05:14 PM, Gene Cumm wrote: > This sounds like you're using gpxelinux.0 4.07 which as I stated will > introduce issues. Instead of using gpxelinux.0 4.07, try pxelinux.0 > 4.07 then do your chainload to lpxelinux.0 6.02. If this doesn't > solve it, try 6.03-pre14. When I DHCP boot to lpxelinux.0 6.02, and then pxechn.c32 back to lpxelinux.0 6.02 with the http

On Tue, Jul 16, 2013 at 6:26 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Jul 15, 2013 at 11:57 PM, Alexandre Blanchette > <blanalex at gmail.com> wrote: > > In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to > use > > pxechn.c32 to call iPXE (undionly) with option 67 set to call an iPXE > > script. > > > > The

In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to use pxechn.c32 to call iPXE (undionly) with option 67 set to call an iPXE script. The relevant portion of my PXELinux config looks like this: LABEL MDT MENU LABEL ^B - MDT 2012 SP1 com32 pxechn.c32 APPEND undionly.kpxe -o 67.s=ipxe/mdt.ipxe However iPXE doesn't seem to get the option correctly, it goes into

On Mon, Dec 29, 2014 at 04:15:56AM -0800, Patrick Masotta wrote: > On Mon, Dec 29, 2014 at 08:47:54AM +0100, Luke Ledgerd wrote: > > I think I'd like to ask for a feature request to allow pxechn.c32 > > to work with EFI too and to have the ability for PXELinux to have a > > ROOT path variable (kind of like gpxelinux.0) that can either have > > HTTP or TFTP urls.

On Sat, Oct 24, 2015 at 6:15 PM, Michael Brown via Syslinux <syslinux at zytor.com> wrote: > Also, not a fork: http://git.ipxe.org/ipxe.git/commitdiff/8406115 A fork is a fork, regardless the reasons behind it (yes, I have some understanding in this case). iPXE is based off of forking further development as of a certain gPXE commit with some backporting of gPXE development to iPXE. --

Hi! We use Windows tftp-servers (so I dont think switching now would be an alternative). But I can try to suggest it. More specific, vendor id of the mac address, is what I want to be able to "choose" (if match) which bootmenu to display. Like all broadcom NICs we have would boot the undionly.kpxe "menu!! (I am having some trouble with broadcom (PCI fiber) and iPXE :) And the

I'm looking for either a way of setting the root path - a Linux style "pivot_root" functionality, that would be perfect. Also a way of overriding prefixing the root path with a URL or some other acceptable syntax to designate to use a different TFTP server. That would really make PXELinux really versatile. Some people concerned about security may want a way of blocking that just

On 06/16/2014 07:12 PM, H. Peter Anvin wrote: > On 06/16/2014 02:57 PM, Alexander Perlis wrote: >> Here's what I mean by 'chainloading to install an automatic http prefix': > > The other option is to use a very small default configuration file > containing only: > > default reload > label reload > config http://...path to real config file .../

On Jul 22, 2013 5:27 PM, "Gene Cumm" <gene.cumm at gmail.com> wrote: > > On Mon, Jul 22, 2013 at 11:36 AM, Matt Fleming <matt at console-pimps.org> wrote: > > On Sat, 20 Jul, at 09:48:38AM, Victor Sudakov wrote: > >> Negative. > >> > >> I have changed the stanza into > >> > >> label WDS > >> menu LABEL ^4.

On May 31, 2012 5:23 AM, "Arends, R.R." <r.r.arends at hr.nl> wrote: > > Hello Genec, > > Got a question regarding pxechn.c32 in combination with wds (2k8r2). > > We got (i)pxelinux as our main pxe system, and want to chain to wds with a vesamenu option. > > I tried the latest pxechn.c32 from git. But somehow wds still tries to contact the next-server (main

On Thu, Aug 8, 2013 at 7:21 PM, Hans Lellelid <hans at velum.net> wrote: > On Thu, Aug 8, 2013 at 7:15 PM, H. Peter Anvin <hpa at zytor.com> wrote: > >> On 08/08/2013 04:14 PM, Hans Lellelid wrote: >> > >> > Sorry, I will give some better output tomorrow. I think when this >> > happened I was still using menu.c32 so I didn't see any output,

Hello everyone, I am trying to chainload grub2 using both pxechain.com and pxechn.c32 and in both cases once grub2 loads it fails to find the grub config file on the server. My setup is as follows: 1. DHCP (192.168.1.2) server points to a multi pxe server menu on itself. The entry in the dhcp config file is: *class "installerator-pxeclients" { match if substring (option

Folks, Finally, Syslinux 5.10 has been released. This release includes a merge of the 4.10 development branch, which means that there's a new network stack availble, based on the lwIP embedded TCP/IP stack. The jump from the previous 5.01 release to 5.10 may be a little confusing, but a new network stack is such a large change that it deserved a significant bump in the version minor number.

On 06/16/2014 10:41 AM, Gene Cumm wrote: > [...] Initially I wrote pxechn.c32 to allow further > modifications of the DHCP data [...] Awesome! In fact, this might allow us to install an automatic 'http' prefix on all subsequent requests, to avoid slow tftp --- or is that a bad idea, and/or is there a way to default all transfers to http without using pxechn and without prefixing

On Thu, Oct 10, 2013 at 10:00 AM, Michael Brown <mbrown at fensystems.co.uk> wrote: > On 09/10/13 10:45, Robin Smidsr?d wrote: >> >> On 09.10.2013 02:56, H. Peter Anvin wrote: >>> >>> The gPXE in the Syslinux tree is ridiculously old. We could either >>> replace it with iPXE or just drop it, giving people a recipe for how to >>> integrate

On 08/08/2013 04:14 PM, Hans Lellelid wrote: > > Sorry, I will give some better output tomorrow. I think when this > happened I was still using menu.c32 so I didn't see any output, it just > reloaded the menu. But I will respond back tomorrow after trying this > with more scientific rigour. I might be able to do the packet trace, > though that may be a little tricky to

On 24/10/15 21:57, Doug Scoular via Syslinux wrote: > 1. gpxe - a mothballed Network Boot Program but with a possibly problematic > and slow HTTP implementation. > 2. ipxe - an active fork of gpxe but still with the possibly problematic > and slow HTTP implementation (?) iPXE's HTTP implementation is definitely not slow. On a Gigabit LAN, you should get the full 1000Mbps speed

I'm sure I'm doing something wrong here, but I would appreciate a pointer. I have tried to rtfm, but find the docs a little sparse wrt pxechain.comand gpxelinux.0. I am trying to setup a pxe chain server (aka chainloading?) where one of the entries on one pxe server forwards to another (cobbler, in this case). I know this works fine with traditional pxelinux.0 images, but it's

On Wed, Aug 7, 2013 at 7:26 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > <snip> > > After my experiences with writing/testing pxechn.c32, I'm not > surprised that this happens. What version(s) have you used? > > One of the goals of lpxelinux.0 is to replace gpxelinux.0 for HTTP/FTP > fetch capability. This is available in versions 5.10+ and 6.00+ (BIOS

Hi! As documented: http://www.syslinux.org/wiki/index.php/PXELINUX When pxelinux "boots" it is looking for this: /mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd /mybootdir/pxelinux.cfg/C000025B /mybootdir/pxelinux.cfg/C000025 /mybootdir/pxelinux.cfg/C00002 /mybootdir/pxelinux.cfg/C0000 /mybootdir/pxelinux.cfg/C000