similar to: Issue with pxe chainloading and grub2

On Mon, Jun 16, 2014 at 10:23 AM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > When chainloading one pxelinux from another (e.g., chainloading from say > pxelinux 4.07 to pxelinux 6.02), can one pass parameters or somehow control > the root directory and/or server IP address? > > Here's the need: we have a loaded-up PXE server working great under 4.07, > and

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.

I've spent a lot more time with this today, trying to get this working with 4.07, 5.01, and 5.10 ... no luck, but I did have a few follow-up questions. (1) Should it be possible to use the newer (e.g. 5.10) version of syslinux and use http:// URLs for both the initial vmlinuz image and also the initrd? -- As I was doing before with gpxelinux.0? A naive attempt to use lpxelinux.0 on our

On Dec 25, 2014 2:11 AM, "Luke Ledgerd" <luke.ledgerd at niteco.se> wrote: > > Hey guys, > > We are going with WDS to fire up first to get the benefits of targeted M$ deployments. If you have the "handle unknown computers" off on your M$ Distribution point, then you can still use regular WDS which runs next as a PXE filter (DLL linked into WDS) to fire off

On Wed, Aug 7, 2013 at 3:58 PM, Hans Lellelid <hans at velum.net> wrote: > 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

On 10/07/17 19:13, Jelle de Jong via Syslinux wrote: > Thank you Gene! > > On 10/07/17 17:54, Gene Cumm wrote: >> On Mon, Jul 10, 2017 at 11:25 AM, Jelle de Jong via Syslinux >> <syslinux at zytor.com> wrote: >>> Windows 2012 WDS server: 10.87.0.202 >>> Windows DHCP server: 10.87.0.152 >>> 066 (Boot Server Host Name): 10.87.3.19 >>>

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

I was able to solve the problem with the following configuration: label custom1 MENU custom1 kernel pxechain.com append ::custom1/pxelinux.0 label custom2 MENU custom2 kernel pxechain.com append ::custom2/pxelinux.0 configdir1/pxelinux.cfg/default configdir2/pxelinux.cfg/default Then I dropped the custom pxelinux.0 files in their respective directories, confgdir1 and configdir2. On Tue, Nov

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

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

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 Mon, Jul 10, 2017 at 11:25 AM, Jelle de Jong via Syslinux <syslinux at zytor.com> wrote: > Windows 2012 WDS server: 10.87.0.202 > Windows DHCP server: 10.87.0.152 > 066 (Boot Server Host Name): 10.87.3.19 > 067 (Bootfile Name): pxelinux.0 > > PXELinux CentOS 7 server : 10.87.3.19 > > # cat /srv/tftp/pxelinux.cfg/default > DEFAULT menu.c32 > PROMPT 0 > MENU

Thank you Gene! On 10/07/17 17:54, Gene Cumm wrote: > On Mon, Jul 10, 2017 at 11:25 AM, Jelle de Jong via Syslinux > <syslinux at zytor.com> wrote: >> Windows 2012 WDS server: 10.87.0.202 >> Windows DHCP server: 10.87.0.152 >> 066 (Boot Server Host Name): 10.87.3.19 >> 067 (Bootfile Name): pxelinux.0 >> >> PXELinux CentOS 7 server : 10.87.3.19

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

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

Hey guys, We are going with WDS to fire up first to get the benefits of targeted M$ deployments. If you have the "handle unknown computers" off on your M$ Distribution point, then you can still use regular WDS which runs next as a PXE filter (DLL linked into WDS) to fire off anything you want to including PXELinux. The stuff I was talking about before with PXELinux not working in

On Mon, Jun 16, 2014 at 5:57 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > 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

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