Undionly.kpxe and ipxe.efi
Working on something for Linux DHCP because I have a need for it. Just all research at this point… Again, if I succeed, I’ll update the aforementioned WiKi article.
Just created this article:
Just found an Awesome article, I’m posting all of what I found because I’d hate for the resource to go away…
Going to try this out next week!
[syslinux] Windows Server DHCP + UEFI recipe
Alexandre Blanchetteblanalex at gmail.com
Wed Jan 15 03:45:05 PST 2014
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
I’ve found a way to support PXE booting both UEFI and BIOS architecturesvwith 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 scope or as global settings as usual by setting options 66 (IP or hostname of your > TFTP > > host) and 67 (pxelinux.0). For the UEFI clients, you must then create a policy. In the condition > page > > of the wizard, add a condition with the following settings: > > Criteria: Vendor Class > > Operator: Equals > > Value: PXEClient (UEFI x64) > > Tick Append wildcard(*) > > > > Do not configure an IP address range for the policy. > > > > Finally configure options 66 (TFTP server) and 67 (syslinux.efi). You > must > > separate TFTP servers for your BIOS and UEFI clients because Microsoft > DHCP > > server does 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. >> I haven’t tried WS2012 yet but PXELINUX will parse DHCP option 43 > (vendor-specific information) nicely and I have encapsulated 210 > inside 43 successfully (can’t recall if I tried WS2008R2 and/or > ISC-DHCPd but I did at least one). >> The one oddball missing from your recipe is the UEFI x86 systems that > are not 64 bit. They are rare but exist. >> – > -Gene > _______________________________________________ > Syslinux mailing list > Submissions to [URL=‘http://www.zytor.com/mailman/listinfo/syslinux’]Syslinux at zytor.com[/URL] > Unsubscribe or set options at: > [url]http://www.zytor.com/mailman/listinfo/syslinux[/url] > Please do not send private replies to mailing list traffic. >>
Still researching this… This thread is likely to get very jumbled up as I do this.
Tech Net article: Introduction to DHCP policies:
So, I have to get this working on my Windows Server DHCP service.
I did some digging, and there’s different ways.
For Windows Server 2008, you must use option 003 as stated here:
For Windows Server 2012, you must use DHCP Policies, as shown here:
I’m going to look further into this, as it applies to just soo many things within my environment. It’s the key to getting a Mac & PC Bios environment to work, and to support PC UEFI based booting also.
[quote=“Uncle Frank, post: 44033, member: 28116”]You’d probably best use DHCP user classes. There is one example for this in the wiki in Macintosh: [url]http://fogproject.org/wiki/index.php/FOG_on_a_MAC[/url]
Something similar can be done not just for Mac but for other platforms. The tricky bit will be to find a check that will reliably distinguish between those with EFI and those without…[/quote]
Thank you Uncle Frank. This seems really important, and I’ve gotta tackle it somehow, or at least become very familiar.
You’d probably best use DHCP user classes. There is one example for this in the wiki in Macintosh: [url]http://fogproject.org/wiki/index.php/FOG_on_a_MAC[/url]
Something similar can be done not just for Mac but for other platforms. The tricky bit will be to find a check that will reliably distinguish between those with EFI and those without…