similar to: [git-pull] pxechn: change debug and add to NEWS

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

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

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:

OK, another prelease. This one is looking pretty good and the shortlog is appended below. Any testing that you can do would be greatly appreciated. In particular, Matt, could you try out this prerelease and see whether your disabled entries are no longer highlighted/selectable? If things stay looking good over the next few days we can hopefully cut a 4.06 final release at the weekend or early

I've changed my repo from git://github.com/geneC1/syslinux.git to git://github.com/geneC/syslinux.git and still have several git-pull requests pending. Change from native compiled C application to Perl to remove the platform association: git://github.com/geneC/syslinux.git diag-geodsp-perl-for-hpa Add AsciiDoc documentation and minor fixes to cptime.c32 and prdhcp.c32:

On Sat, 20 Jul, at 09:48:38AM, Victor Sudakov wrote: > Negative. > > I have changed the stanza into > > label WDS > menu LABEL ^4. Windows Deployment Service > com32 pxechn.c32 > append 10.14.140.128::boot\x86\wdsnbp.com -W > > and got the following result on VirtualBox: > > pxechn.c32: Attempting to load '10.14.140.128::boot\x86\wdsnbp.com':

Hi, ________________________________________ From: Gene Cumm <gene.cumm at gmail.com> Sent: Wednesday, March 16, 2016 00:56 To: Jan Frode J?ger Cc: syslinux at zytor.com Subject: Re: [syslinux] Updated status on UEFI compliant version of the pxechn-module On Tue, Mar 15, 2016 at 9:32 AM, Jan Frode J?ger <jan.frode.jaeger at ntnu.no> wrote: Without trying to figure out where data is

On Jul 14, 2013 10:02 PM, "Victor Sudakov" <vas at mpeks.tomsk.su> wrote: > > I have tried replacing the IP address with a DNS name like this: > > LABEL WDS1 > Menu LABEL WDS1 > com32 pxechn.c32 > append ws150.sibptus.transneft.ru::boot\x86\wdsnbp.com -W -o 66.x=0a:0e:8d:96 Did you try without "-o 66..."? Any chance for a packet capture from a

Right now, I almost have pxechn.c32 in a fully functional state by adding a parameter to allow pure hex input of an option and its data. It allows uppercase and lowercase entry with or without octet delimiters (which must not match [0-9A-Fa-f]) and requires 2-digit entry for the octet. This is an extremely loose input format such that users may utilize it in their preferred format. After adding

Digging more, loadfile("192.0.2.1::pxe.0", &file.data, &file.size), queries DNS, which sounds like it doesn't follow the same call path as a COM32 calling pxe_dns(). If the DNS won't resolve the IP, things won't load properly. pxechn.c32 sets sname in the intended packet to "192.0.2.1" which may be confusing something. More debugging needed. -- -Gene

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.

Hello I'm currently working on a project to rolling out a new TFTP boot server, for a fairly large infrastructure (>200 servers, >1500 clients, with heterogeneous configurations/setups). We are using Syslinux version 6.03 for all the function within our TFTP server. We are using Ubuntu as our main TFTP server for most deployments and WDS for our

Folks, I've just pushed out another prerelease for the 5.00 branch. The idea behind this -pre was to merge in the final 4.06 release. I'm aiming for a final 5.00 release next week, but as we saw with the 4.06 branch, anything can happen and these deadlines can get pushed backwards. Please, test if you can. One thing that is going to happen next week is a Syslinux-6.00-pre1, which will

Hi, Ok, when can we then anticipate pxe-chaining to be possible with syslinux under the UEFI architecture? Are there any plans to implement both correct interfacing to UEFI as well as the issue of arbitrary UEFI images? Haven't tried to read the UEFI-specification as it is sub 3000-pages long, so I am a bit in the dark as to the changes in architecture from BIOS to UEFI. It has been

On Sat, Sep 19, 2015 at 4:32 PM, BALATON Zoltan <balaton at eik.bme.hu> wrote: > On Fri, 18 Sep 2015, Gene Cumm via Syslinux wrote: >> >> On Sep 18, 2015 7:07 AM, "Ady via Syslinux" <syslinux at zytor.com> wrote: >> >>> I doubt there has been any update to pxechn.c32 for UEFI support. Maybe >>> Gene can confirm. >> >>

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 Jul 13, 2013 9:00 AM, "Victor Sudakov" <vas at mpeks.tomsk.su> wrote: > > Gene Cumm wrote: > > >> pxelinux.0 since Syslinux-5.10 won't return the IP of a string like > > >> "192.0.2.1" (which is the source of the issue). > > > > > > Which means the correct syntax for the pxechn.c32 command line > > > should

On Tue, Jul 16, 2013 at 12:51 AM, Victor Sudakov <vas at mpeks.tomsk.su> wrote: > Gene Cumm wrote: >> >> Did you try without "-o 66..."? Any chance for a packet capture from a >> mirrored port or the dhcpd+tftpd-old+tftpd-new+dnsd? > > OK, I have tried the following: > > label WDS > menu LABEL ^4. Windows Deployment Service > com32

On Fri, 19 Jul, at 04:24:52PM, Victor Sudakov wrote: > Gene Cumm wrote: > > > > The big thing I notice is just that since 5.10, the > > > > code in pxelinux.0 does DNS queries for specific calls rather than a > > > > dotted quad conversion first. > > > > > > That *was* relevant. It did not work until I replaced the dotted quad > > >