search for: blanalex

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 relevant portion of my PXELinux config looks like this: &g...

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

...t 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 binary logic, or any other mean. Currently, PXELINUX is calling an iPXE script, so the solution can be at either level. -- Alexandre Blanchette <blanalex at gmail.com>

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

...#39;ve tried with pxelinux.0 and pxechn.c32 from 6.01 with the same result. Also, while we're on the subject of pxechn.c32, in the documentation, the purpose and the usage of the -f option is unclear: what is a 'modifier'? There is no example of its usage. -- Alexandre Blanchette <blanalex at gmail.com>

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

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 then :-) > 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...

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: > >> Alexandre Blanchette <blanalex at gmail.com> writes: >> >> > Is there a way to show some bits of information in the menu, like >> > Syslinux versio...

...es not send option 210 (path prefix). Microsoft DHCP servers will only send options listed in the Parameter Request List in the DHCPDISCOVER packet. One could make a cleaner setup by creating a BIOS PXEClient vendor class and putting their options within a policy too. -- Alexandre Blanchette <blanalex at gmail.com>

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

...es 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 filter UEFI clients so I set option 67 to the right value (lpxelinux.efi)? -- Alexandre Blanchette <blanalex at gmail.com>

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

...00 SFF). For now, my fix is to filter out localboot 0-incompatible machine in a lua script by looking up DMI informations and exiting pxelinux with the chain.c32 module, but that means that I have to update the script for every new computer model I have on my network. -- Alexandre Blanchette <blanalex at gmail.com>

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

...WinPE50 MENU LABEL Windows Boot Manager COM32 pxechn.c32 APPEND \boot\x64\bootmgfw.efi I get: pxechn.c32: ERROR: Unable to retrieve first packet Could not unpack packet Using SYSLINUX 6.02-pre16 I could not use SYSLINUX 6.02-final because of the TFTP port bug. -- 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...

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. I suppose you use menu.c32. Exit the men...

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