[Bug 1813541] Re: Shim uses wrong TFTP server IP in proxyDHCP mode

[Alkis Georgopoulos]

The PXE specification, which also describes proxyDHCP, can be found for example at:
http://www.pix.net/software/pxeboot/archive/pxespec.pdf

The "proof" that the proxyDHCP server should be used as the TFTP server,
is the fact that shimx64.efi was indeed downloaded by the UEFI firmware
from the proxyDHCP server. This is true for all UEFI and BIOS firmwares,
and for iPXE and any other client that understands PXE services.

Shim just needs to follow suit and use the same TFTP server where it's
located at.

** Changed in: shim (Ubuntu)
       Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim in Ubuntu.
https://bugs.launchpad.net/bugs/1813541

Title:
  Shim uses wrong TFTP server IP in proxyDHCP mode

Status in shim package in Ubuntu:
  New

Bug description:
  This works fine:
  UEFI > real DHCP > shimx64.efi over TFTP > grubx64.efi over TFTP.

  In the scenario above, if we change "real" with "proxy", it fails,
  because it's trying to download grubx64.efi from the real DHCP server
  instead of the proxy one.

  A proxy DHCP server is one that only sends the boot filename, and
  leaves the IP assignments to the real DHCP server. We use that a lot
  in the ltsp.org and in other netbooting projects, as it avoids the
  need for a special network setup.

  Sample dnsmasq.conf for proxy setup:

  enable-tftp
  tftp-root=/var/lib/tftpboot
  dhcp-range=10.161.254.0,proxy,255.255.255.0
  pxe-service=X86-64_EFI,"Boot from network",shimx64.efi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1813541/+subscriptions