-----BEGIN PGP SIGNED MESSAGE-----
Below is the reply I sent to your original mail to me. The reply
bounced, seemingly due to a misconfiguration of the MX record for your
domain. Hopefully this will get to you via the list.
I can shed some light on this, but not give you a complete answer.
Firstly, your 2-not-working example fails because it's not using PXE.
PXE clients do sensible things when the "bootfile name" is set in DHCP
replies, which is what dhcp-boot does, but this isn't the complete PXE
protocol. Hence example one works. That trick doesn't work for
PXE-proxy, since you need the PXE protocol to do proxy. Any
configuration without pxe-service enabled will never work for PXE
proxy. That explains config 2.
Your example 3 - I'm confused why that shouldn't work - the PXE client
seems to be making further requests which are bring ignored. Would it
be possible for you to get a packet dump of that exchange using tcpdump?
Example 4 looks quite hopeful - the client is succerssfully
downloading the bootx64.efi file (ignore the error before, that's just
testing for the existance of the file.
Can you see what's displayed on the client system at this point?
On 18/01/17 14:36, Jr-Huang Shiau wrote:
> Dear all, I am having the same issue as Juan García-Pardo described
> On Ubuntu 16.04, I use dnsmasq which is backported from Ubuntu
> 16.10: dpkg -l dnsmasq Desired=Unknown/Install/Remove/Purge/Hold |
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name Version Architecture
ii dnsmasq 2.76-5 all Small
> caching DNS proxy and DHCP/TFTP server
> I configured a PXE server, and disabled the isc-dhcp-server and
> tftpd-hpa so that I can test the DHCP proxy function of dnsmasq.
> 1. When the attached config file "1-working-local.conf" is used as
> /etc/dnsmasq.conf without DHCP proxy, both PXE or uEFI client boot
> 2. When the attached config file "2-not-working-proxy.conf" is used
> as /etc/dnsmasq.conf with DHCP proxy, both PXE or uEFI client can
> _NOT_ boot successfully. In the log file "2-not-working-proxy.log"
> you can see either PXE or uEFI client fails to enter network
> 3. When the attached config file "3-partial-working-local.conf" is
> used as /etc/dnsmasq.conf without DHCP proxy, PXE client can boot
> successfully. However, EFI client did not. The log file was
> attached as "3-not-working-efi-local.log".
> 4. When the attached config file "4-partial-working-proxy.conf" is
> used as /etc/dnsmasq.conf with DHCP proxy, PXE client can
> successfully enter network booting, as shown in
> "4a-working-pxe-client-proxy.log". However, for EFI network client,
> just "bootx64.efi" was downloaded, no other files were downloaded,
> as shown in "4b-not-working-efi-client-proxy.log". For comparison,
> you can see in "1-working-efi-no-proxy.log", without DHCP proxy,
> the clients should download grub config file "grub.cfg" and other
> Therefore it seems there is some uEFI network booting issues, no
> matter it's using proxy or not.
> If you need me to do more tests or more info, please let me know.
> Thank you very much.
> _______________________________________________ Dnsmasq-discuss
> mailing list Dnsmasqemail@example.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
-----END PGP SIGNATURE-----
Dnsmasq-discuss mailing list