On Wed, 22 Jan 2020 at 21:43, Geert Stappers <stapp...@stappers.nl> wrote: >... > > FWIW > Over here is "PXE service" not used. I have no idea what I might be > missing. My reason for involvement in this thread is finding what use > case O.P. has for dnsmasq. Finding out if it can improve my use case, > finding out if it can improve dnsmasq (which also benefits me). > At this point its mostly curiosity - I am migrating from an older pxelinux, BIOS-only setup to iPXE for BIOS and UEFI, with possible expansion into direct-booting specific clients like a Raspberry Pi. I wanted to keep the option of booting into the old setup. Also, having read the documentation, it should be possible to use dnsmasq to provide PXE boot service independently of the DHCP server in the network, which would be particularly useful for making an appliance-like setup that is dropped into the network and provides tools like clonezilla, memtest, etc. I haven't tried that mode yet.
> > > The idea of it is getting a "shared problem". And from > > > a shared problem to get to a shared solution. > > > > A shared problem: Make UEFI PXE client display 2 boot options - one > > for an existing boot image, and one to exit PXE (boot from disk, > > etc.). > > My approach is default boot from disk and netbooting for a (re)install. > > Back to "pxe service". It is a server-client-combo-issue. > Here on this mailinglist is dnsmasq the only common factor. > Dnsmasq is at server side. The explain the server-client-combo-issue > needs the client side extra care. So tell about client site. > That includes the risk of losing audience here due "I don't have such > clients". Increase audience numbers by "The seen behaviour can be > reproduced with this libre virtualisation platform". Oh, so you can't induce the issue/reproduce the preconditions. Now it's clear to me :) Sorry, I'm not keeping up with libre VM solutions, so I'm not sure which, if any, can do PXE UEFI boot. I'm using vmware (Fusion, HW version 14) to test this. Google finds this article [1], which suggests it is possible to do in KVM. VirtualBox which I have installed, does not support network boot in UEFI mode. If you have UEFI hardware and don't mind using it for this, I would suggest using the three-service config and seeing if that works correctly. I can send a packet capture if needed. I _think_ you should be able to replicate at least the PXE-menu part of the issue with just a config for dhclient [2] - haven't tested this, as §it requires the normal dhclient instance to be disabled. Cheers, MZ > Groeten > Geert Stappers > -- > Leven en laten leven > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss [1] https://eatpeppershothot.blogspot.com/2016/07/enable-pxe-netboot-in-kvm-guests-for.html [2] # dhclient.conf: send vendor-class-identifier "PXEClient:Arch:00007:UNDI:003016"; option client-system-architecture code 93 = unsigned integer 16; send client-system-architecture 7; _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
