Hi Petr, Thanks for all your help. Have done a build from the fork shared above. Herein are the test results.
Now: Rpi + proxy success Rpi + noproxy success Efi + proxy failure Efi + noproxy success BIOS + proxy failure BIOS + noproxy success Earlier it was only: Efi + noproxy failure I believe that unless you can find a way to replicate all the scenarios at your end, it will be very difficult for you to nail the exact problem area in the code. Hence, I have attached the pcap and logs for all scenarios as well as the ipxe files and dnsmasq (proxy and noproxy) conf and build options used in this archive - https://drive.google.com/file/d/1-nwKXxqor2nNEYDyIFg1T1OwhFAXv19O/view?usp=sharing The names of the files in the archive should be self-explanatory. Yet do let me know if you need any further information. Regards, Shrenik On Thu, 7 Oct, 2021, 05:12 Petr Menšík, <pemen...@redhat.com> wrote: > Hi guys, > > I configured something on my laptop and tried few requests with my > raspberry. I think I have found weird state. It checks only matching > dhcp-range context, not pxe-service, when adding PXE stuff to requests. > So I made it require also pxe-service. It seems it might do what you > have requested, at least on the first glance. > > Patch #2 is just small tuning, unifying dhcp-boot and pxe-service way of > setting boot files. There is slight chance it might break something. In > that case, either dhcp-boot or pxe-service needs fixing. > > Could you please try success with patched version? I made new COPR > builds [1] for Fedora, including these changes. But I think that is not > your distribution. Can you try local build? Pushed also to our fork [2]. > > 1. https://copr.fedorainfracloud.org/coprs/pemensik/dnsmasq/ > > 2. https://github.com/InfrastructureServices/dnsmasq/tree/pxe-services > > >
_______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
