<div dir="ltr"><div dir="ltr"><div><br></div><div>Hi Petr,</div><div><br></div><div>The proposed config (also given below) doesn't work in non-proxy mode. I tested it with a RPi 4B and Intel NUC in non-proxy mode. <br></div><div><br></div><div>
<span style="font-family:monospace"><b>pxe-service=<span>tag:!iPXE,X86PC,ltsp/undionly.kpxe<br>
pxe-service=tag:!iPXE,X86-64_EFI,ltsp/snponly.efi<br>
pxe-service=tag:iPXE,</span><span><span>X86PC,</span>ltsp/ltsp.ipxe<span><br>
pxe-service=tag:iPXE,</span><span><span></span></span></span><span><span><span><span>X86-64_EFI</span>,</span>ltsp/ltsp.ipxe</span></span></b></span></div><span style="font-family:monospace"><b><span><span># fallback for BIOS-only clients without PXE support</span></span></b></span><br><span style="font-family:monospace"><b><span><span></span></span></b></span><div><span style="font-family:monospace"><b><span><span>
dhcp-boot=<span>tag:!iPXE,ltsp/undionly.kpxe</span></span></span></b></span></div><div><span style="font-family:monospace"><b><span><span><span><br></span></span></span></b></span></div><div><span style="font-family:monospace"><span><span><span><font face="arial,sans-serif">On NUC</font></span></span></span><span style="font-family:arial,sans-serif"><b><span><span><span>, </span></span></span></b><span><span><span>we get this after fetching IP -</span></span></span></span></span></div><div><span style="font-family:monospace"><span><span>PXE-E77: Bad or missing discovery server list</span></span></span></div><div><span style="font-family:monospace"><span style="font-family:arial,sans-serif"><span><span><span><br></span></span></span></span></span></div><div><span style="font-family:monospace"><span style="font-family:arial,sans-serif"><span><span><span>On RPi it endlessly loops at -</span></span></span></span></span></div><div><span style="font-family:monospace"><span style="font-family:arial,sans-serif"><span><span><span><span style="font-family:monospace">[43:9]: 'ltsp/undionly.kpxe '</span><br></span></span></span></span></span></div><div><span style="font-family:monospace"><span style="font-family:arial,sans-serif"><span><span><span><br></span></span></span></span></span></div><div><span style="font-family:monospace"><span style="font-family:arial,sans-serif"><span><span><span>However, your proposed config works fine in proxy mode with just one addition for RPi -</span></span></span></span></span></div><div><span style="font-family:monospace"><span style="font-family:arial,sans-serif"><span><span><span><span style="font-family:monospace">pxe-service=tag:rpi,X86PC,unused</span><br></span></span></span></span></span></div><div><span style="font-family:monospace"><span style="font-family:arial,sans-serif"><span><span><span><br></span></span></span></span></span></div><div><span style="font-family:monospace"><span style="font-family:arial,sans-serif"><span><span><span>But this is already known and that's why tag:proxy was introduced to bring into play pxe-service only when using in proxy mode.<br></span></span></span></span></span></div><div><span style="font-family:arial,sans-serif"><span><span><br></span></span></span></div><div><span style="font-family:arial,sans-serif"><span><span>I have this more precise finding and at the risk of repeating myself -</span></span></span></div><div><span style="font-family:arial,sans-serif"><span><span>With the below configuration in non-proxy mode, RPi and Intel NUC boot BIOS boot fine but Intel NUC in UEFI mode doesn't.</span></span></span></div><div><span style="font-family:arial,sans-serif"><span><span>
<span style="font-family:monospace"><span style="font-family:arial,sans-serif"><span><span><span><span style="font-family:monospace">pxe-service=tag:rpi,X86PC,"Raspberry Pi Boot ",unused</span></span></span></span></span></span>
</span></span></span></div><div><span style="font-family:monospace"><span>dhcp-boot=tag:!iPXE,tag:X86PC,ltsp/undionly.kpxe<br>dhcp-boot=tag:!iPXE,tag:X86-64_EFI,ltsp/snponly.efi<br>dhcp-boot=tag:iPXE,ltsp/ltsp.ipxe</span></span></div><div><span style="font-family:monospace"><span><br></span></span></div><div><span style="font-family:monospace"><span><font face="arial,sans-serif">However, if I just comment out the pxe-service line, all works fine for Intel NUC in BIOS and UEFI mode but now RPi won't boot. This is exactly what I had started this thread with. Hence I shared the pcap dump and logs in the previous post.</font><br></span></span></div><div><span style="font-family:monospace"><span><br></span></span></div><div><span style="font-family:arial,sans-serif"><span><span>Best regards,</span></span></span></div><div><span style="font-family:monospace"><span><span><span><font face="arial,sans-serif">Shrenik<br></font></span></span></span></span></div><div><span style="font-family:monospace"><span><span><span></span></span></span><b><span><span><span><br></span></span></span></b></span>
</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 27 Sept 2021 at 19:40, Petr Menšík <<a href="mailto:pemensik@redhat.com">pemensik@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>I think this should have been:</p>
<p>pxe-service=<span>tag:!iPXE,X86PC,ltsp/undionly.kpxe<br>
pxe-service=tag:!iPXE,X86-64_EFI,ltsp/snponly.efi<br>
pxe-service=tag:iPXE,</span><span><span>X86PC,</span>ltsp/ltsp.ipxe<span><br>
pxe-service=tag:iPXE,</span><span><span></span></span></span><span><span><span><span>X86-64_EFI</span>,</span>ltsp/ltsp.ipxe<br>
# fallback for BIOS-only clients without PXE support<br>
dhcp-boot=<span>tag:!iPXE,ltsp/undionly.kpxe</span></span></span></p>
<p><span><span>Does LTSP still support booting outside PXE standard?
Does it need to be supported? I think only non-PXE capable
clients should fall back to to dhcp-boot parameters. All
others should have some pxe-service entry. Current code does
not allow different configuration I think. Even without iPXE,
PXEClient will get boot parameter ONLY from pxe-service. It
would get dhcp-boot parameter only if there is no pxe-service
used at all.<br>
</span></span></p>
<p><span><span>It seems pxe-service is IPv4 only at the moment. Any
device trying to boot over IPv6 would probably boot only
using: <br>
</span></span></p>
<p><span><span>dhcp-option=option6:bootfile-url,</span></span><span><span><span>ltsp/ltsp.ipxe</span></span></span></p>
<p><span><span><span>Which is a bit sad. I guess only input
parameters and output options are somehow different. But it
should offer similar paths also on IPv6. Maybe time would be
found sometime to implement also IPv6 support.</span></span></span></p>
<p><span><span><span>Cheers,<br>
Petr<br>
</span></span></span></p>
<div>On 9/25/21 13:14, Shrenik Bhura wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div dir="auto">Hi Geert,</div>
<div dir="auto"><br>
</div>
<div dir="auto">Your advice doesn't seem to work. Gives an error
on the very first line that has been changed.</div>
<div dir="auto"><span>tag:!iPXE,X86PC,ltsp/undionly.kpxe</span></div>
<div dir="auto"><br>
</div>
<div dir="auto">Thanks,<br>
</div>
<div dir="auto">Shrenik</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, 19 Mar, 2021, 15:54
Geert Stappers via Dnsmasq-discuss, <<a href="mailto:dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">dnsmasq-discuss@lists.thekelleys.org.uk</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, Mar 19, 2021 at
11:05:05AM +0200, Alkis Georgopoulos wrote:<br>
> Hi all,<br>
<br>
;-)<br>
<br>
<br>
> I'm one of the LTSP developers; I asked Shrenik to
contact the dnsmasq<br>
> mailing list because I feel this might be a dnsmasq
issue.<br>
> <br>
> Specifically, success or failure depends on whether these
five lines are<br>
> commented out or not:<br>
> <br>
>
#pxe-service=tag:proxy,tag:!iPXE,X86PC,"undionly.kpxe",ltsp/undionly.kpxe<br>
>
#pxe-service=tag:proxy,tag:!iPXE,X86-64_EFI,"snponly.efi",ltsp/snponly.efi<br>
>
#pxe-service=tag:proxy,tag:iPXE,X86PC,"ltsp.ipxe",ltsp/ltsp.ipxe<br>
>
#pxe-service=tag:proxy,tag:iPXE,X86-64_EFI,"ltsp.ipxe",ltsp/ltsp.ipxe<br>
> #pxe-service=tag:rpi,X86PC,"Raspberry Pi Boot ",unused<br>
> <br>
> You may find the full configuration files and logs at:<br>
> <a href="https://github.com/ltsp/ltsp/pull/417" rel="noreferrer noreferrer" target="_blank">https://github.com/ltsp/ltsp/pull/417</a><br>
> <br>
> The reason I feel it might be a dnsmasq issue, is that
these tags are NOT<br>
> matched in Shrenik's use case. He's not using proxy mode
and he's not<br>
> booting a Raspberry Pi.<br>
> <br>
> So, "pxe-service" lines that are NOT matched, cause the
problem,<br>
> yet if they're commented out, the problem is gone...<br>
> <br>
> Would that be an issue with dnsmasq, or with the UEFI PXE
stack?<br>
<br>
I go for something inbetween:<br>
UEFI PXE stack insisting on something that dnsmasq
**configuration**<br>
doesn't yet provide. Or server side **configuration** is
something<br>
that the client can't handle.<br>
<br>
<br>
Advice:<br>
Leave out `pxe-service`, skip "PXE". Yes, do iPXE ;-)
[1]<br>
<br>
Transform<br>
|
#pxe-service=tag:proxy,tag:!iPXE,X86PC,"undionly.kpxe",ltsp/undionly.kpxe<br>
|
#pxe-service=tag:proxy,tag:!iPXE,X86-64_EFI,"snponly.efi",ltsp/snponly.efi<br>
|
#pxe-service=tag:proxy,tag:iPXE,X86PC,"ltsp.ipxe",ltsp/ltsp.ipxe<br>
|
#pxe-service=tag:proxy,tag:iPXE,X86-64_EFI,"ltsp.ipxe",ltsp/ltsp.ipxe<br>
| #pxe-service=tag:rpi,X86PC,"Raspberry Pi Boot ",unused<br>
into something like[2]:<br>
| tag:!iPXE,X86PC,ltsp/undionly.kpxe<br>
| tag:!iPXE,X86-64_EFI,ltsp/snponly.efi<br>
| tag:iPXE,X86PC,ltsp/ltsp.ipxe<br>
| tag:iPXE,X86-64_EFI,ltsp/ltsp.ipxe<br>
| tag:rpi,X86PC,unused<br>
<br>
<br>
Request:<br>
Report back<br>
<br>
<br>
<br>
Groeten<br>
Geert Stappers<br>
Voetnoten:<br>
[1] iPXE stands for "It doesn't do PXE"<br>
[2] actual syntax not verified<br>
-- <br>
Silence is hard to parse<br>
<br>
_______________________________________________<br>
Dnsmasq-discuss mailing list<br>
<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" rel="noreferrer" target="_blank">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br>
<a href="https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss" rel="noreferrer noreferrer" target="_blank">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a><br>
</blockquote>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Dnsmasq-discuss mailing list
<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">Dnsmasq-discuss@lists.thekelleys.org.uk</a>
<a href="https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss" target="_blank">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a>
</pre>
</blockquote>
<pre cols="72">--
Petr Menšík
Software Engineer
Red Hat, <a href="http://www.redhat.com/" target="_blank">http://www.redhat.com/</a>
email: <a href="mailto:pemensik@redhat.com" target="_blank">pemensik@redhat.com</a>
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB</pre>
</div>
_______________________________________________<br>
Dnsmasq-discuss mailing list<br>
<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br>
<a href="https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a><br>
</blockquote></div></div>