[Dnsmasq-discuss] DHCP Proxy and UEFI HTTP boot

[michael at albert-hetzles.de]

It is incomplete. => Thanks for your detailed answer.

Michael

Am 08.06.2022 10:31, schrieb Geert Stappers via Dnsmasq-discuss:

> On Tue, Jun 07, 2022 at 11:35:26AM +0200, Michael via Dnsmasq-discuss 
> wrote:
> 
>> Hi dnsmasq-discuss Groupmembers,
>> 
>> I tried to get working dnsmasq as DHCP Proxy for UEFI HTTP boot.
>> 
>> The following configuration, dnsmasq as DHCP Server, works (but we 
>> have
>> another DHCP Server running):
>> 
>> dhcp-range=efi-http,192.168.1.200,192.168.1.220
>> 
>> dhcp-option=tag:efi-http,option:vendor-class,HTTPClient
>> dhcp-option=tag:efi-http,option:bootfile-name,http://192.168.1.100/esxi/mboot.efi
>> 
>> But when i tried to setup dnsmasq as  DHCP Proxy it does not respond 
>> to any
>> requests:
>> 
>> dhcp-range=efi-http,192.168.1.0,proxy,255.255.255.0
>> 
>> dhcp-option=tag:efi-http,option:vendor-class,HTTPClient
>> dhcp-option=tag:efi-http,option:bootfile-name,http://192.168.1.100/esxi/mboot.efi
>> 
>> After further investigations I found out that dnsmasq does only 
>> responds
>> (send packets) to DHCP Requests, when configured as DHCP Proxy, when 
>> the
>> options  pxe-service and dhcp-boot are set (to some "default", useless
>> values, and therefore UEFI HTTP Boot not work). But in my opinion 
>> these
>> options are not necessary for booting UEFI HTTP Clients and makes no 
>> sense
>> to set.
>> 
>> Anybody a hint for me whats wrong in my configuration?
> 
> It is incomplete.
> 
>> Or is the combination DHCP Proxy and UEFI HTTP boot not RFC like?
>> 
>> THx in advance
> 
> Yeah, the answer was send in advance.
> Now wait for the next monthly posting.
> 
>> Michael
> 
> Groeten
> Geert Stappers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20220608/c832efb9/attachment.htm>