similar to: UEFI PXE boot & Microsoft DHCP

A small how-to for encapsulating option 210 inside option 43 on Windows DHCP servers would be welcome then :-) And as far as UEFI x86 system go, one would simply have to create another vendor class with the value PXEClient:Arch:00006 On Wed, Jan 15, 2014 at 12:05 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Tue, Jan 14, 2014 at 8:52 PM, Alexandre Blanchette > <blanalex at

I've found a way to support PXE booting both UEFI and BIOS architectures with Windows Server DHCP. This method uses a feature introduced in WinServer 2012: DHCP policies. First, in the the DHCP console, at the IPv4 root of the server, create a vendor class named PXEClient (UEFI x64) with the following value: PXEClient:Arch:00007 Then create your configuration for your BIOS clients in your

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

Op 2013-08-16 om 06:39 schreef Alexandre Blanchette: > I'm currently using Microsoft DHCP to enable PXE booting. I've set options > 66 and 67 for the relevant scopes and it's all fine and dandy. > > However, UEFI machines won't initiate PXE boot, they don't seem to > recognize the options. Is there another setting that need to be set? > > And how to I

Alexandre Blanchette <blanalex at gmail.com> writes: > On Wed, Dec 10, 2014 at 10:14 AM, Ferenc Wagner <wferi at niif.hu> wrote: > >> Alexandre Blanchette <blanalex at gmail.com> writes: >> >>> We are doing a deployment across many sites, we're doing one site at >>> a time and we're bringing a "mobile server" (a laptop,

We are doing a deployment across many sites, we're doing one site at a time and we're bringing a "mobile server" (a laptop, really) to keep traffic local instead saturating the WAN link of each site. I'd like to make a script so each client can determine if the mobile server is on the same subnet either with a ping with a zero TTL value, with the ip/netmask and a bit of

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

I successfully encapsulated option 210 inside 43 with Microsoft DHCP servers. I followed the template in the PXELINUX documentation, at the "using vendor options, handcrafted" heading. On Wed, Jan 15, 2014 at 6:45 AM, Alexandre Blanchette <blanalex at gmail.com>wrote: > A small how-to for encapsulating option 210 inside option 43 on Windows > DHCP servers would be welcome

On Fri, Feb 21, 2014 at 2:50 AM, Ferenc Wagner <wferi at niif.hu> wrote: > Alexandre Blanchette <blanalex at gmail.com> writes: > > > Is there a way to show some bits of information in the menu, like > > Syslinux version, MAC address and IP address? When the menu is loaded > > at startup, this information is quickly erased and is not easily > > readable.

Is there a way to show some bits of information in the menu, like Syslinux version, MAC address and IP address? When the menu is loaded at startup, this information is quickly erased and is not easily readable. -- Alexandre Blanchette <blanalex at gmail.com>

On Tue, Jan 14, 2014 at 8:52 PM, Alexandre Blanchette <blanalex at gmail.com> wrote: > I've found a way to support PXE booting both UEFI and BIOS architectures > with Windows Server DHCP. > > This method uses a feature introduced in WinServer 2012: DHCP policies. > > First, in the the DHCP console, at the IPv4 root of the server, create a > vendor class named

Correction: Ctrl-J Bypasses labels and tries to load file So at the prompt if one inputs foo<Ctrl-J>, pxelinux looks for a file in the following order: foo.c32 foo.img foo.bss foo.bin foo.bs foo.0 foo On Sat, Feb 22, 2014 at 2:12 PM, Alexandre Blanchette <blanalex at gmail.com>wrote: > On Fri, Feb 21, 2014 at 2:50 AM, Ferenc Wagner <wferi at niif.hu> wrote: >

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 >

With the BIOS architecture, I was used to boot WinPE from PXELINUX. I used 4 different ways: 1- Calling windows' native PXE loader directly from the config file with a 'kernel' line. 2- Calling windows' native PXE loader with pxechn.c32. 3- Loading an ISO with memdisk 4- iPXE project's wimboot, which relies on memdisk Methods 1 and 2 are slow because loading the bulk of the

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

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

Mattias Schlenker <ms at mattiasschlenker.de> wrote: > Is ifcpu.c32 or ifcpu64.c32 sufficient for your task? No. I need to detect a given machine by something unique. E.g. the MAC-address of the Ethernet Interface CPU-id or such, because I have custom kernels for all the machines. Sven -- If you can spend five minutes on the Internet and do not run Linux, you're a genius. (Dirk

I saw Geoff Lywood's patch to check gPXE functionnality, it is very interesting. Would it make sense to make add the gPXE availability flag inside the Lua interpreter? In my case, I would use it to detect if I can boot Windows PE the old-fashioned way by tftp or if I can download an ISO by http and boot it with memdisk. -- Alexandre Blanchette <blanalex at gmail.com>

I'm bringing back an old thread, but I'm still having problem with this: http://etherboot.org/pipermail/gpxe/2010-March/000571.html The summary of that thread is that with gpxelinux.0, on some computers the command LOCALBOOT 0 will hang the computer. Around the same time as the original thread, there was a patch to add localboot -1. Also in the original thread, it was proposed to use

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 >