similar to: pxechn.c32: Status

Now that pxechain.com can work (with my patch to core/pxelinux.asm), a PXE Chainload COM32 is not as big of a deal but I agree with HPA that it would be a good idea, especially considering the possible flexibility that this may allow. For the moment, I've named the chain module pxechn.c32 in order to not collide with the name pxechain.com when not specifying the .com/.c32 extension.

On Thu, Sep 19, 2013 at 5:13 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Wed, Sep 18, 2013 at 4:09 PM, Chris Valentino > <chris.valentino at 1010data.com> wrote: >> I upgraded from syslinux 4.x to syslinux 6.01 and am now having issues with >> pxe chaining. I've tried moving up as far as 6.02-pre16, but I'm still experiencing the same problem. The

As some have noticed, WDS (Windows Deployment Services) on Windows Server 2008R2 can't normally be chained with pxechain.com. Some have also noticed wdsnbp.com doing something resembling another round of DHCP (discover/ack/request/offer). Working on pxechn.c32 I've found the "issue" and incorporated a workaround into pxechn.c32. wdsnbp.com issues a DHCP discover to the IP

I upgraded from syslinux 4.x to syslinux 6.01 and am now having issues with pxe chaining. I've tried moving up as far as 6.02-pre16, but I'm still experiencing the same problem. The original config called the next server as follows: LABEL Cobbler KERNEL pxechain.com APPEND 10.x.x.x::pxelinux.0 Which worked for the previous version, but I started getting an error after

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

On Jul 16, 2013 2:01 PM, "Alexandre Blanchette" <blanalex at gmail.com> wrote: > > 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 >

On Wed, Sep 18, 2013 at 4:09 PM, Chris Valentino <chris.valentino at 1010data.com> wrote: > I upgraded from syslinux 4.x to syslinux 6.01 and am now having issues with > pxe chaining. I've tried moving up as far as 6.02-pre16, but I'm still experiencing the same problem. The original config called the next server as follows: What's the version of the first and second

Hi, I have more than one pxe server in my network and I need to chain from one to the other. I used to do that with pxechain.com from old versions of syslinux. With the new version (6.02) I'm trying to achieve this with pxechn.c32. I copied the files ldlinux.c32, libcom32.c32, libutil.c32, pxechn.c32, pxelinux.0 and vesamenu.c32 to the tftp's root in both servers and add this in the menu:

On 02/20/2014 07:34 AM, Rodrigo Abrantes Antunes wrote: > Hi, I have more than one pxe server in my network and I need to chain from > one to the other. I used to do that with pxechain.com from old versions of > syslinux. With the new version (6.02) I'm trying to achieve this with > pxechn.c32. I copied the files ldlinux.c32, libcom32.c32, libutil.c32, > pxechn.c32, pxelinux.0

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

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, 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 relevant portion of my PXELinux config looks like this: > > LABEL MDT > MENU LABEL ^B - MDT 2012 SP1 >

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

IRC user ernini first noticed this. We both tried using gpxe/gpxelinux.0 from Syslinux-4.04-pre22. ernini used pxechain to a commercial NBP which RETs (the same as PXELINUX) and failed. Both of us had success with core/pxelinux.0 from Syslinux-4.04-pre22. For my test, I have a VM in VMware Server 2.0.2 (VMHW v7). I loaded gpxelinux.0 using the VM's built-in PXE ROM. Then I used

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 Fri, Jul 12, 2013 at 8:14 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Fri, Jul 12, 2013 at 5:14 AM, Victor Sudakov <vas at mpeks.tomsk.su> wrote: >> Colleagues, >> >> I am attempting to chainload a file from TFTP. I have the following >> lines in the configuration file: >> >> LABEL WDS1 >> Menu LABEL WDS1 >> kernel

On Fri, Jul 12, 2013 at 9:09 AM, Victor Sudakov <vas at mpeks.tomsk.su> wrote: > Gene Cumm wrote: >> > >> > I am attempting to chainload a file from TFTP. I have the following >> > lines in the configuration file: >> > >> > LABEL WDS1 >> > Menu LABEL WDS1 >> > kernel pxechn.c32 >> > append

Gene Cumm wrote: > > > > I am attempting to chainload a file from TFTP. I have the following > > lines in the configuration file: > > > > LABEL WDS1 > > Menu LABEL WDS1 > > kernel pxechn.c32 > > append 10.14.141.150::boot\x86\wdsnbp.com -W -o 66.x=0a:0e:8d:96 -S > > > > The TFTP server at 10.14.141.150 is operational and wdsnbp.com is

Gene Cumm wrote: > >> > > >> > I am attempting to chainload a file from TFTP. I have the following > >> > lines in the configuration file: > >> > > >> > LABEL WDS1 > >> > Menu LABEL WDS1 > >> > kernel pxechn.c32 > >> > append 10.14.141.150::boot\x86\wdsnbp.com -W -o 66.x=0a:0e:8d:96 -S > >>