Hi folks,
Would it make sense to have an option to explicitly enable PXE without having
to use or enabling pxe-prompt or pxe-service?
I'd like the following to work, and then it would end up being a minimal
command for PXE booting using proxyDHCP, without having to do seemingly
arbitrary / unnecessary things (which by their arbitraryness are non-intuitive):
dnsmasq -d --bind-interface --port=0 -l leases --dhcp-range=192.168.101.1,proxy
--enable-tftp --tftp-root="$(realpath ./files)" --dhcp-boot=pxelinux.0
Currently what the command actually needs to be is:
dnsmasq -d --bind-interface --port=0 -l leases --dhcp-range=192.168.101.1,proxy
--enable-tftp --tftp-root="$(realpath ./files)" --pxe-service=254,dummy
--dhcp-boot=pxelinux.0,,192.168.101.1
Currently
1. https://github.com/ipxe/ipxe/issues/954 , if it is indeed a bug in dnsmasq,
would need to get fixed to shorten dhcp-boot, and
2. the other issue is is that (proxy dhcp) pxe mode is only enabled if
pxe-prompt or pxe-service is passed. Is this really necessary? Also, shouldn't
proxy mode enable it? I'm not sure a --enable-pxe option makes much sense for
proxy mode, though maybe it does for normal dhcp.
Unrelated:
3. dnsmasq seems to pass pxe prompt suboptions (IIRC) 6 and 10 even when
pxe-prompt isnt set / suboption 9 isn't sent (i.e. pxe-prompt isnt set, I
think). Is this necessary?
Regards,
_______________________________________________
Dnsmasq-discuss mailing list
[email protected]
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
