Re: [Dnsmasq-discuss] pxe-service line for UEFI system?

[P W]

On Sun, Jan 19, 2020 at 07:30:44PM +0100, Michal Zatloukal wrote:
> On Wed, 8 Jan 2020 at 00:16, Michal Zatloukal  wrote:
> >
> > In the meantime, I tried a simpler case [1] of UEFI PXE services
> > config, which I confirmed to work.
> >
> > I intended to replace my config with this and work up towards the
> > fancier tag-operated version, but made a wrong assumption and _added_
> > the trivial config to existing set of config files (adding .bak to the
> > filename didn't stop the original from being loaded). Strangely, now
> > option 43 contained all services for CSA 7 - both conditional, and
> > unconditional ones, which were previosly missing. This actually
> > happens even when the new config file is reduced to a single,
> > unconditional pxe-service line. That's not how this should work, or is
> > it? Is there a particular order to these pxe-* config options? IMHO
> > the fact that only the menu items are missing, but prompt is sent,
> > should indicate that setting tags is correct.
> >
> > I'll do from-the-ground-up experiment soon, hopefully finding at which
> > point dnsmasq stops sending the boot options.
> >
> > Cheers,
> > MZ
> >
> > [1]
> > # Commented out to use my existing config, must be included if using 
> > standalone.
> > #dhcp-range=10.0.0.10,10.0.0.240,2h
> > #log-dhcp
> > #tftp-root=/tftpboot
> > #dhcp-no-override
> > pxe-prompt="dnsmasq menu"
> > pxe-service=0, "Boot BIOS PXElinux", bios/pxelinux
> > pxe-service=0, "Boot BIOS iPXE", ipxe/undionly.kpxe
> > pxe-service=7, "Boot UEFI CSA 7", efi64/syslinux.efi
> > pxe-service=7, "Other item CSA 7",etc/other.efi
> > pxe-service=9, "Boot UEFI CSA 9", efi64/syslinux.efi
> > pxe-service=9, "Other item CSA 9",etc/other.efi
> > pxe-service=0, "Exit menu"
> > pxe-service=7, "Exit menu"
> > pxe-service=9, "Exit menu"
> 
> 
> Finally got to troubleshoot this today...
> The issue arises when there's only a single "proper" pxe-service
> configured (one that actually has a boot-filename defined). Is this
> expected?
> 
> So this works:
> pxe-prompt="dnsmasq menu"
> pxe-service=7, "Boot UEFI CSA 7", efi64/syslinux.efi
> pxe-service=7, "Other item CSA 7",etc/other.efi
> pxe-service=7, "Exit menu"
> 
> But this does not:
> pxe-prompt="dnsmasq menu"
> pxe-service=7, "Boot UEFI CSA 7", efi64/syslinux.efi
> pxe-service=7, "Exit menu"
> 

Patches welcome

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] DHCPv6 with dnsmasq for automated deployments

[P W]

On Fri, May 25, 2018 at 03:34:08PM +0200, Oliver Freyermuth wrote:
> Am 25.05.2018 um 15:30 schrieb Kevin Darbyshire-Bryant:
> >> On 25 May 2018, at 13:07, Oliver Freyermuth wrote:
> >>
> >> Dear dnsmasqers,
> >>
> >> I fear the following is a design issue of DHCPv6, but I wonder if there's 
> >> a way to overcome it with dnsmasq...
> > 
> > 
> > Hi Oliver,
> > 
> > I???ve a similar/same problem when rebooting some QNAP NAS boxen,
> > first boot/introduction to dnsmasq and they get both IPv4 & v6
> > addresses set to fixed values based on MAC address.  On reboot whilst
> > IPv4 is fine, IPv6 is not reallocated to the original address but
> > rather a new one.  By curious co-incidence I just started looking
> > into this problem today though it has been bugging me for months :-)
> > Have tried various combinations of MAC address & DUID.
> > 
> 
> Dear Kevin, 
> 
> I think it's exactly the same issue. 
> Comparing:
> > Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 
> > DHCPREQUEST(br-lan) 00:01:00:01:22:9a:b4:43:24:5e:be:0c:bc:ba
> with
> > Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 
> > DHCPSOLICIT(br-lan) 00:01:00:01:22:9a:b7:2b:24:5e:be:0c:bc:ba
> it seems the QNAP NAS box is using a fresh client DUID each reboot... 


Patches Welcome

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss