<div dir="ltr">Klaus, Jorell and Francis,<div><br></div><div>Let me start by saying I have never tested or tried anything but classic PXE in my lab. But thanks for providing your configurations as a point of reference if I ever need them. I looked at the configuration I have for the PXE, iPXE, UEFI, etc, and I found it interesting how different it was. To Francis' point, I am using option 93, rather than 60. </div><div><br></div><div><div> "client-classes": [</div><div> {</div><div> "boot-file-name": "pxelinux.0",</div><div> "name": "pxe_x86",</div><div> "next-server": "10.50.32.95",</div><div> "server-hostname": "labtools",</div><div> "test": "option[93].hex == 0x0000"</div><div> },</div><div> {</div><div> "boot-file-name": "syslinux.efi",</div><div> "name": "pxe_efi_ia32",</div><div> "next-server": "10.50.32.95",</div><div> "server-hostname": "labtools",</div><div> "test": "option[93].hex == 0x0006"</div><div> },</div><div> {</div><div> "boot-file-name": "syslinux.efi",</div><div> "name": "ipxe_efi_bc",</div><div> "next-server": "10.50.32.95",</div><div> "server-hostname": "labtools",</div><div> "test": "option[93].hex == 0x0007"</div><div> },</div><div> {</div><div> "boot-file-name": "syslinux.efi",</div><div> "name": "ipxe_efi_x86_64",</div><div> "next-server": "10.50.32.95",</div><div> "server-hostname": "labtools",</div><div> "test": "option[93].hex == 0x0009"</div><div> },</div></div><div><br></div><div>I think I created this based on some internet research, and these were classifications for isc-dhcp. Then I converted it to work with Kea... I cannot remember. It certainly works for PXE_x86, but perhaps this will offer a different point of view of a way to work with iPXE.</div><div><br></div><div>Francis, I was thinking that it would be cool to put stuff like this in a knowledge base or something on the wiki to pull together how to do things like this. Alternately we could have a GIT repo of contributed configuration examples that have been validated by users who know what they are doing. :) Obviously this would need to be treated like any other open source project, but would be really cool way to share example configs to increase adoption velocity. Something to consider... Perhaps this is something Victoria would be interested in looking at?</div><div><br></div><div>Thanks,</div><div>Jason</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 5, 2018 at 7:24 PM, Francis Dupont <span dir="ltr"><<a href="mailto:fdupont@isc.org" target="_blank">fdupont@isc.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I looked at for possible candidates fro client-architecture options.<br>
One is the option 93 (client-system in Kea which BTW does not allow<br>
to redefine options). The value 16 is not in RFC 4578 table but it is<br>
11 year old...<br>
<div class="HOEnZb"><div class="h5"><br>
Regards<br>
<br>
Francis Dupont <<a href="mailto:fdupont@isc.org">fdupont@isc.org</a>><br>
______________________________<wbr>_________________<br>
Kea-users mailing list<br>
<a href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/kea-users</a><br>
</div></div></blockquote></div><br></div>