Hi Simon,
thanks, it’s working fine for me now. Before releasing 2.76, it would be good
if more people could test this on actual hardware.
Also, there’s one more item that needs to go into the release notes: we now
redirect all clients to port 4011, including the BIOS clients. This is a change
I have included a patch below that makes essentially two modifications to get
PXE working with the UEFI firmware in VMware.
- It only appends the layer number to the file name on BIOS x86.
- It always redirects the client to port 4011. To do that, only the siaddr is
set and neither a boot file no
> - I think that this is just a workaround (because what
> dnsmasq implements should be working for PXE/UEFI ...)
> and it may not be needed in the future .. so kind more 'elegant' to
> implement it this way (option could be called 'pxe-menu-workaround'
> perhaps ?
This workaround will be req
> The difference between Michael's patch and Jarek's seems to be that
> Michael's works automatically when there is precisely one valid boot
> service line, but Jarek's needs explicit configuration. What situation
> does Jarek's approach cover, that Michael's doesn’t?
I’ve also been wondering abou
I’ve posted a patch to make it work:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2015q4/010007.html
It works perfectly for a single PXE service. It only uses the PXE menu system
if multiple PXE services are specified as most firmware implementations don’t
fully support it. Make sur
newer uefi I get a ip assigned and get to the "Press F8 for
> the Menu." After that everything quits and returns to the bios. Here is some
> info. If there are more debugging options let me know? I am running
> dnsmasq-2.75 with a patch from Michael Kuron earlier on this
As it turns out, UEFI does support PXE menus, but the implementations are
rather buggy in that regard. VMware often does not render the menu on the
screen, but you can blindly select the menu entry using the arrow keys and boot
it with the return key. A recent Asus laptop renders the menu, but i
if (pxearch == service->CSA &&
match_netid(service->netid, netid, 1))
> On 24.10.2015, at 15:21, Michael Kuron
> wrote:
>
> More wiresharking helped me figure this out. So when UEFI receives a DHCP
> Offer or Proxy DHCP Offer with Vendor Class Identifier (opt
More wiresharking helped me figure this out. So when UEFI receives a DHCP Offer
or Proxy DHCP Offer with Vendor Class Identifier (option 60) set to PXEClient,
it sends a DHCP Request to the siaddr from the offer, but on port 4011. If the
server then sends a DHCP ACK back to port 4011, containing
I made some changes to dnsmasq (patch below) that remove the PXE menu system
(the option 43 stuff) if there’s only one menu entry and put the boot file name
and server address directly into the file and siaddr fields. This works fine
for BIOS systems, but doesn’t work for UEFI either.
Next thing
10 matches
Mail list logo