search for: niteco

...org/archives/2014-March/021825.html I have my DHCP server set up just like steven from CloneZilla.org does. Any suggestions for this one? Luke Ledgerd / Internal IT Add: 156 Xa Dan II, 14th Floor, ?????????Dong Da District, Hanoi, Vietnam. Mobile Vietnam: +84 (0) 995304270 Email: luke.ledgerd at niteco.se Skype: luke-ledgerd-niteco Web: http://niteco.se

On Mon, Nov 24, 2014 at 3:24 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote: > http://www.niallbrady.com/2014/06/11/when-uefi-network-booting-on-a-hyperv-gen-2-vm-you-might-get-pxe-e99-unexpected-network-error/ > > P.S. It's not this and I'm getting a PXE-E99 tftp failure "Unexepected Network Error", so I'll guess I'll need t...

...Luke -----Original Message----- From: Gene Cumm [mailto:gene.cumm at gmail.com] Sent: Thursday, November 27, 2014 8:50 PM To: Luke Ledgerd Cc: syslinux at zytor.com Subject: Re: [syslinux] pxelinux efi64 boot woes on hyper-v gen 2 On Mon, Nov 24, 2014 at 3:24 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote: > http://www.niallbrady.com/2014/06/11/when-uefi-network-booting-on-a-hy > perv-gen-2-vm-you-might-get-pxe-e99-unexpected-network-error/ > > P.S. It's not this and I'm getting a PXE-E99 tftp failure "Unexepected Network Error", so I'll guess I'll...

On Thu, Nov 27, 2014 at 8:59 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote: > Gene, > > As it happened I started working on this again just as you mailed me. I saw it in IRC. > It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0...

...ay, without appending stuff to the kernel boot argument. That way an unpatched wimboot from ipxe could be made to work. Cheers, Luke Luke Ledgerd / Internal IT Add: 156 Xa Dan II, 14th Floor, ?????????Dong Da District, Hanoi, Vietnam. Mobile Vietnam: +84 (0) 995304270 Email: luke.ledgerd at niteco.se Skype: luke-ledgerd-niteco Web: http://niteco.se

...ay, without appending stuff to the kernel boot argument. That way an unpatched wimboot from ipxe could be made to work. Cheers, Luke Luke Ledgerd / Internal IT Add: 156 Xa Dan II, 14th Floor, ?????????Dong Da District, Hanoi, Vietnam. Mobile Vietnam: +84 (0) 995304270 Email: luke.ledgerd at niteco.se Skype: luke-ledgerd-niteco Web: http://niteco.se

...rg/archives/2014-March/021825.html I have my DHCP server set up just like steven from CloneZilla.org does. Any suggestions for this one? Luke Ledgerd / Internal IT Add: 156 Xa Dan II, 14th Floor, ?????????Dong Da District, Hanoi, Vietnam. Mobile Vietnam: +84 (0) 995304270 Email: luke.ledgerd at niteco.se Skype: luke-ledgerd-niteco Web: http://niteco.se

...}; option PXE.boot-item code 71 = unsigned integer 32; default-lease-time 300; max-lease-time 300; option subnet-mask 255.255.252.0; option domain-name-servers X & Y; option domain-name "niteco.se"; option domain-search "niteco.se"; ddns-update-style none; server-name Z; option arch code 93 = unsigned integer 16; allow booting; allow bootp; # we don't use vendor option space - the ROMS need it too #ve...

...npatched wimboot from ipxe could be made to work. > > Cheers, > > Luke > > > > > Luke Ledgerd / Internal IT > > Add: 156 Xa Dan II, 14th Floor, > ?????????Dong Da District, Hanoi, Vietnam. > Mobile Vietnam: +84 (0) 995304270 > Email: luke.ledgerd at niteco.se > Skype: luke-ledgerd-niteco > Web: http://niteco.se > > > > > > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslin...

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

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

I'm running pxelinux configured to use the path /bios on the tftp server for all the comboot files. The problem is dmi,syslinux,vesa etc modules are not being loaded in lua. Syslinux.version() returns not found in global index as does dmi.supported() For k,v in pairs(package.loaded) do print (k,v) end; shows that these modules that are normally loaded by lua are not loading. I got an idea

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

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

Spike White, Sent: Saturday, December 27, 2014 4:32 AM > > Luke, I have considerable experience with this. We use WDS at work > for PXE (MS-centric shop). I use pxelinux at home. > > I've got WDS working in our test lab w/ UEFI. As you state, it strongly > wishes to do proxyDHCP (port 4011). More on this in a bit. > > It's quite common to segregate the DHCP

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

Ady: You seem to be taking (copy$paste) parts and pieces from different resources. Luke: Nope. The configuration works fine with PXE 2.01 clients, it's the UEFI PXE 3.2 that is having issues with the dhcp requests. The gospel is the Intel PXE 3 spec I'm RTFMing now. No copy and paste, I just started with someone elses configuration file that claims to support UEFI - or at least hopes to

<snip > A: Because it messes up the order in which people normally read text, especially the archives of mailing lists. Q: Why is Top-posting such a bad thing? I apologize in advance for the potentially-dumb comments/questions. _ Do you really need the Vendor Class Identifier option included in the "if option arch" conditions? _ Do you really need the Vendor Class Identifier