<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <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 class="moz-cite-prefix">On 9/25/21 13:14, Shrenik Bhura wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CANKp9xdLvbygEt6cznvBJ=KkQpeMZ6DNS0xrz0URUuhGMxb-iA@mail.gmail.com">
      <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"
            moz-do-not-send="true" class="moz-txt-link-freetext">dnsmasq-discuss@lists.thekelleys.org.uk</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote">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"
            moz-do-not-send="true" class="moz-txt-link-freetext">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"
            target="_blank" rel="noreferrer" moz-do-not-send="true"
            class="moz-txt-link-freetext">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"
            moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Dnsmasq-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.thekelleys.org.uk</a>
<a class="moz-txt-link-freetext" href="https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a>
</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Petr Menšík
Software Engineer
Red Hat, <a class="moz-txt-link-freetext" href="http://www.redhat.com/">http://www.redhat.com/</a>
email: <a class="moz-txt-link-abbreviated" href="mailto:pemensik@redhat.com">pemensik@redhat.com</a>
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB</pre>
  </body>
</html>