Jarek Polok
2016-03-02 09:17:45 UTC
Hello
I've seen in list mail archives that the problem
of UEFI systems not booting while using PXE boot menu
has been discussed in the past already:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2015q4/010007.html
and a patch was proposed.
I tried that patch but for some UEFI firmwares it
did not work for me.
Tracing reply proxyDHCP packet from a Microsoft WDS
server I was able to change the patch a little and
it seems to make proxyDHCP work for all clients I've
been able to test with (4 different hardware models
and qemu-kvm with OVMF (Tianocore) firmware).
In addition to filling in siaddr and bootfile in the
reply header my version fills also sname then
avoids adding option 43 (some clients did not boot
without sname set..)
This is how WDS replies on 4011 for PXE requests
for all BIOS/EFI clients ..
(WDS also adds option 252, filled with text
representation of data possibly needed by
WDS bootloader , seems to contain architecture path,
some (G)UUID and BCD location ?)
In the attachment you will find my version of the patch,
adding 'pxe-menu-skip=<CSA>' option which makes dnsmasq
to 'shortcut' boot process sending back to pxe client
first matching (by tag and CSA) pxe-service when
acting in proxy-DHCP mode.
Dear maintainer: would you please consider adding this
patch to dnsmasq ?
Best Regards
Jarek
__
-------------------------------------------------------
_ Jaroslaw_Polok ___________________ CERN - IT/CM/LCS _
_ http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _
______________________________________+41_75_411_9487 _
I've seen in list mail archives that the problem
of UEFI systems not booting while using PXE boot menu
has been discussed in the past already:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2015q4/010007.html
and a patch was proposed.
I tried that patch but for some UEFI firmwares it
did not work for me.
Tracing reply proxyDHCP packet from a Microsoft WDS
server I was able to change the patch a little and
it seems to make proxyDHCP work for all clients I've
been able to test with (4 different hardware models
and qemu-kvm with OVMF (Tianocore) firmware).
In addition to filling in siaddr and bootfile in the
reply header my version fills also sname then
avoids adding option 43 (some clients did not boot
without sname set..)
This is how WDS replies on 4011 for PXE requests
for all BIOS/EFI clients ..
(WDS also adds option 252, filled with text
representation of data possibly needed by
WDS bootloader , seems to contain architecture path,
some (G)UUID and BCD location ?)
In the attachment you will find my version of the patch,
adding 'pxe-menu-skip=<CSA>' option which makes dnsmasq
to 'shortcut' boot process sending back to pxe client
first matching (by tag and CSA) pxe-service when
acting in proxy-DHCP mode.
Dear maintainer: would you please consider adding this
patch to dnsmasq ?
Best Regards
Jarek
__
-------------------------------------------------------
_ Jaroslaw_Polok ___________________ CERN - IT/CM/LCS _
_ http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _
______________________________________+41_75_411_9487 _