Re: [Dnsmasq-discuss] [EXTERNAL] Re: UEFI PXE Boot Issue: dhcp-option 60
Hi, Indeed this was due to "pxe-prompt" which I was using that was causing this issue for UEFI. This worked fine for BIOS clients. After removing pxe-prompt, dnsmasq ver. 2.76 worked successfully for PXE booting of UEFI hosts. On the left is DHCP-ACK packet send from server without "pxe-prompt" and on the right the same packet when "pxe-prompt" is specified. Specifying pxe-prompt made dnsmasq send dhcp options 60, 97 and 43. [cid:image002.png@01D6CD87.586E9710] Thank you for your help. -swanand -Original Message- From: Wang Shanker Sent: Monday, December 7, 2020 8:50 PM To: Swanand Vaidya Cc: Geert Stappers ; dnsmasq-discuss@lists.thekelleys.org.uk Subject: Re: [Dnsmasq-discuss] [EXTERNAL] Re: UEFI PXE Boot Issue: dhcp-option 60 Hi, In theory, `dhcp-pxe-vendor` cannot prevent the special handling of dhcp-option 60 when replying to pxe clients. However, dnsmasq identifies a pxe client by matching "PXEClient" string sent in the requests. By using this setting, you can specify a dummy string for this like DUMMY6789, and normal pxe clients won't be seen as pxe clients anymore by dnsmasq and thus the special handling of dhcp-option 60 is disabled. As I wrote in my previous mail. I strongly suspect the `pxe-prompt` option is the cause of the problem. Cheers, Miao Wang > 2020年12月07日 22:04，Swanand Vaidya > mailto:swanand.vai...@veritas.com>> 写道： > > Hi Geert, > > Yes, the source I had taken included this commit. But as I understand it > allow you to send specific value for vendor class in dhcp-option 60. > I want to totally stop dhcp-option 60 from being sent as different clients > may have different requirements. > Does the new setting 'dhcp-pxe-vendor' allow you to stop dhcp-option 60 from > being sent? > > Thanks, > -swanand > > -Original Message- > From: Geert Stappers mailto:stapp...@stappers.nl>> > Sent: Monday, December 7, 2020 7:19 PM > To: Swanand Vaidya > mailto:swanand.vai...@veritas.com>>; > dnsmasq-discuss@lists.thekelleys.org.uk<mailto:dnsmasq-discuss@lists.thekelleys.org.uk> > Subject: [EXTERNAL] Re: [Dnsmasq-discuss] UEFI PXE Boot Issue: > dhcp-option 60 > > On Mon, Dec 07, 2020 at 01:11:18PM +, Swanand Vaidya wrote: >> Hi, >> >> I am trying to PXE boot a UEFI enabled Dell machine with dnsmasq >> acting as both the DHCP and TFTP server. >> The client and server perform the DHCP steps: DHCP Discover, DHCP >> Offer, DHCP Request and DHCP Ack as expected. >> >> But, thereafter, the client simply aborts the protocol (it does not >> do TFTP to download the NBP file syslinux.efi and others) and I can >> see >> error: >> "PXE-E21: Remote boot canceled" on the client console. >> >> The same dnsmasq configuration works for booting a BIOS based machine. >> >> I found that dnsmasq is sending dhcp-option 60 with value as "PXEClient" >> which is causing this issue. >> >> I could not find any way to disable this from being sent to the client. >> >> Finally, I modified the source code in rfc2131.c by adding "return" >> statement at the top of the function pxe_misc(). The dnsmasq binary >> so built now works fine for booting the UEFI machine. >> >> I would like to know: >> >> 1. If this is a known issue? I tried latest 2.82 version of dnsmasq >> as well as building from the latest source snapshot from HEAD. > > Did that include > http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=4ded96209e8346711f9d0b9e13a835d42835853d > ? > Yes, that is a very very fresh commit. And it is 'PXEClient' related ... > > >> 2. Is there any way to disable dhcp-option 60 from being sent over >> to the client by setting some configuration param in >> dnsmasq.conf? We can force certain option to be sent using >> dhcp-option-force directive, but there is nothing for the opposite >> direction to "force disable" a specific DHCP option. (Setting >> dhcp-option = without a value only works for >> certain dhcp options). >> > > > >> Thanks, > > You are welcome. > > > >> -swanand > > Regards > Geert Stappers > > P.S. > I usually don't do "Reply to All", but I do take insults. > -- > Silence is hard to parse > > ___ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk<mailto:Dnsmasq-discuss@lists.thekelleys.org.uk> > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] [EXTERNAL] Re: UEFI PXE Boot Issue: dhcp-option 60
Hi, I was using the following dnsmasq.conf: == port=0 log-dhcp enable-tftp tftp-root = /var/lib/tftpboot/ log-facility = /var/log/dnsmasq.log dhcp-range = 10.10.2.0, static, 255.255.255.0, infinite dhcp-option = option:router, 10.10.2.4 dhcp-hostsfile = /hostsfile pxe-prompt = "PXE Boot.", 3 dhcp-match=set:x86PC,option:client-arch,0 dhcp-match=set:efi-x86_64,option:client-arch,7 dhcp-match=set:efi-x86_64,option:client-arch,9 dhcp-boot=tag:x86PC,pxelinux.0 dhcp-boot=tag:efi-x86_64,syslinux.efi # Prevent boot file fields being used for options dhcp-no-override # Shut off some options dhcp-option = 28 == -swanand -Original Message----- From: Swanand Vaidya Sent: Monday, December 7, 2020 7:51 PM To: Wang Shanker Cc: Geert Stappers ; dnsmasq-discuss@lists.thekelleys.org.uk Subject: RE: [EXTERNAL] Re: [Dnsmasq-discuss] UEFI PXE Boot Issue: dhcp-option 60 Hi, The Dell server was Dell PowerEdge R320 but is not currently available so I can’t provide more details for the same. But I could reproduce the same issue with a UEFI VM running on VMware ESXi 6.5. I checked that the same issue doesn't happen with similar VM running on ESXi 7.0, so there may be something involved with the firmware. I had tested with dnsmasq 2.76, 2.82 as well as HEAD of the source tree but had this same issue. Would your commit http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=4ded96209e8346711f9d0b9e13a835d42835853d help in this case and how? Thanks, -swanand -Original Message- From: Wang Shanker Sent: Monday, December 7, 2020 7:37 PM To: Swanand Vaidya Cc: Geert Stappers ; dnsmasq-discuss@lists.thekelleys.org.uk Subject: [EXTERNAL] Re: [Dnsmasq-discuss] UEFI PXE Boot Issue: dhcp-option 60 Hi, I also noticed your issue. Can you also test your configuration with a stable version? I wonder if you can provide some detailed information about the model of your DELL Server and the version of firmware. It would be nice if you can provide your configuration so I can test it in my environment. Cheers, Miao Wang > 2020年12月07日 21:49，Geert Stappers 写道： > > On Mon, Dec 07, 2020 at 01:11:18PM +0000, Swanand Vaidya wrote: >> Hi, >> >> I am trying to PXE boot a UEFI enabled Dell machine with dnsmasq >> acting as both the DHCP and TFTP server. >> The client and server perform the DHCP steps: DHCP Discover, DHCP >> Offer, DHCP Request and DHCP Ack as expected. >> >> But, thereafter, the client simply aborts the protocol (it does not >> do TFTP to download the NBP file syslinux.efi and others) and I can >> see error: >> "PXE-E21: Remote boot canceled" on the client console. >> >> The same dnsmasq configuration works for booting a BIOS based machine. >> >> I found that dnsmasq is sending dhcp-option 60 with value as "PXEClient" >> which is causing this issue. >> >> I could not find any way to disable this from being sent to the client. >> >> Finally, I modified the source code in rfc2131.c by adding "return" >> statement at the top of the function pxe_misc(). The dnsmasq binary >> so built now works fine for booting the UEFI machine. >> >> I would like to know: >> >> 1. If this is a known issue? I tried latest 2.82 version of dnsmasq >> as well as building from the latest source snapshot from HEAD. > > Did that include > http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=4ded96209e8346711f9d0b9e13a835d42835853d > ? > Yes, that is a very very fresh commit. And it is 'PXEClient' related ... > > >> 2. Is there any way to disable dhcp-option 60 from being sent over >> to the client by setting some configuration param in >> dnsmasq.conf? We can force certain option to be sent using >> dhcp-option-force directive, but there is nothing for the opposite >> direction to "force disable" a specific DHCP option. (Setting >> dhcp-option = without a value only works for >> certain dhcp options). >> > > > >> Thanks, > > You are welcome. > > > >> -swanand > > Regards > Geert Stappers > > P.S. > I usually don't do "Reply to All", but I do take insults. > -- > Silence is hard to parse > > ___ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] [EXTERNAL] Re: UEFI PXE Boot Issue: dhcp-option 60
Hi, The Dell server was Dell PowerEdge R320 but is not currently available so I can’t provide more details for the same. But I could reproduce the same issue with a UEFI VM running on VMware ESXi 6.5. I checked that the same issue doesn't happen with similar VM running on ESXi 7.0, so there may be something involved with the firmware. I had tested with dnsmasq 2.76, 2.82 as well as HEAD of the source tree but had this same issue. Would your commit http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=4ded96209e8346711f9d0b9e13a835d42835853d help in this case and how? Thanks, -swanand -Original Message- From: Wang Shanker Sent: Monday, December 7, 2020 7:37 PM To: Swanand Vaidya Cc: Geert Stappers ; dnsmasq-discuss@lists.thekelleys.org.uk Subject: [EXTERNAL] Re: [Dnsmasq-discuss] UEFI PXE Boot Issue: dhcp-option 60 Hi, I also noticed your issue. Can you also test your configuration with a stable version? I wonder if you can provide some detailed information about the model of your DELL Server and the version of firmware. It would be nice if you can provide your configuration so I can test it in my environment. Cheers, Miao Wang > 2020年12月07日 21:49，Geert Stappers 写道： > > On Mon, Dec 07, 2020 at 01:11:18PM +, Swanand Vaidya wrote: >> Hi, >> >> I am trying to PXE boot a UEFI enabled Dell machine with dnsmasq >> acting as both the DHCP and TFTP server. >> The client and server perform the DHCP steps: DHCP Discover, DHCP >> Offer, DHCP Request and DHCP Ack as expected. >> >> But, thereafter, the client simply aborts the protocol (it does not >> do TFTP to download the NBP file syslinux.efi and others) and I can >> see error: >> "PXE-E21: Remote boot canceled" on the client console. >> >> The same dnsmasq configuration works for booting a BIOS based machine. >> >> I found that dnsmasq is sending dhcp-option 60 with value as "PXEClient" >> which is causing this issue. >> >> I could not find any way to disable this from being sent to the client. >> >> Finally, I modified the source code in rfc2131.c by adding "return" >> statement at the top of the function pxe_misc(). The dnsmasq binary >> so built now works fine for booting the UEFI machine. >> >> I would like to know: >> >> 1. If this is a known issue? I tried latest 2.82 version of dnsmasq >> as well as building from the latest source snapshot from HEAD. > > Did that include > http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=4ded96209e8346711f9d0b9e13a835d42835853d > ? > Yes, that is a very very fresh commit. And it is 'PXEClient' related ... > > >> 2. Is there any way to disable dhcp-option 60 from being sent over >> to the client by setting some configuration param in >> dnsmasq.conf? We can force certain option to be sent using >> dhcp-option-force directive, but there is nothing for the opposite >> direction to "force disable" a specific DHCP option. (Setting >> dhcp-option = without a value only works for >> certain dhcp options). >> > > > >> Thanks, > > You are welcome. > > > >> -swanand > > Regards > Geert Stappers > > P.S. > I usually don't do "Reply to All", but I do take insults. > -- > Silence is hard to parse > > ___ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] [EXTERNAL] Re: UEFI PXE Boot Issue: dhcp-option 60
Hi Geert, Yes, the source I had taken included this commit. But as I understand it allow you to send specific value for vendor class in dhcp-option 60. I want to totally stop dhcp-option 60 from being sent as different clients may have different requirements. Does the new setting 'dhcp-pxe-vendor' allow you to stop dhcp-option 60 from being sent? Thanks, -swanand -Original Message- From: Geert Stappers Sent: Monday, December 7, 2020 7:19 PM To: Swanand Vaidya ; dnsmasq-discuss@lists.thekelleys.org.uk Subject: [EXTERNAL] Re: [Dnsmasq-discuss] UEFI PXE Boot Issue: dhcp-option 60 On Mon, Dec 07, 2020 at 01:11:18PM +, Swanand Vaidya wrote: > Hi, > > I am trying to PXE boot a UEFI enabled Dell machine with dnsmasq > acting as both the DHCP and TFTP server. > The client and server perform the DHCP steps: DHCP Discover, DHCP > Offer, DHCP Request and DHCP Ack as expected. > > But, thereafter, the client simply aborts the protocol (it does not do > TFTP to download the NBP file syslinux.efi and others) and I can see > error: > "PXE-E21: Remote boot canceled" on the client console. > > The same dnsmasq configuration works for booting a BIOS based machine. > > I found that dnsmasq is sending dhcp-option 60 with value as "PXEClient" > which is causing this issue. > > I could not find any way to disable this from being sent to the client. > > Finally, I modified the source code in rfc2131.c by adding "return" > statement at the top of the function pxe_misc(). The dnsmasq binary so > built now works fine for booting the UEFI machine. > > I would like to know: > > 1. If this is a known issue? I tried latest 2.82 version of dnsmasq > as well as building from the latest source snapshot from HEAD. Did that include http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=4ded96209e8346711f9d0b9e13a835d42835853d ? Yes, that is a very very fresh commit. And it is 'PXEClient' related ... > 2. Is there any way to disable dhcp-option 60 from being sent over > to the client by setting some configuration param in > dnsmasq.conf? We can force certain option to be sent using > dhcp-option-force directive, but there is nothing for the opposite > direction to "force disable" a specific DHCP option. (Setting > dhcp-option = without a value only works for > certain dhcp options). > > Thanks, You are welcome. > -swanand Regards Geert Stappers P.S. I usually don't do "Reply to All", but I do take insults. -- Silence is hard to parse ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] UEFI PXE Boot Issue: dhcp-option 60
Hi, I am trying to PXE boot a UEFI enabled Dell machine with dnsmasq acting as both the DHCP and TFTP server. The client and server perform the DHCP steps: DHCP Discover, DHCP Offer, DHCP Request and DHCP Ack as expected. But, thereafter, the client simply aborts the protocol (it does not do TFTP to download the NBP file syslinux.efi and others) and I can see error: "PXE-E21: Remote boot canceled" on the client console. The same dnsmasq configuration works for booting a BIOS based machine. I found that dnsmasq is sending dhcp-option 60 with value as "PXEClient" which is causing this issue. I could not find any way to disable this from being sent to the client. Finally, I modified the source code in rfc2131.c by adding "return" statement at the top of the function pxe_misc(). The dnsmasq binary so built now works fine for booting the UEFI machine. I would like to know: 1. If this is a known issue? I tried latest 2.82 version of dnsmasq as well as building from the latest source snapshot from HEAD. 2. Is there any way to disable dhcp-option 60 from being sent over to the client by setting some configuration param in dnsmasq.conf? We can force certain option to be sent using dhcp-option-force directive, but there is nothing for the opposite direction to "force disable" a specific DHCP option. (Setting dhcp-option = without a value only works for certain dhcp options). Thanks, -swanand ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
