Sorry, seems not to be a bug at all.
After some research:
- didnt work with "dhcp-range=192.168.0.0,proxy" because of pxe-client problems:
/Compatibility
"Real" PXE clients do support the proxy DHCP specification, as do recent (> May 2009) gPXE clients. But older etherboot clients may be unable to get their boot information from a proxy DHCP server, so for those clients a normal DHCP server is needed (either dhcp3-server or dnsmasq in normal DHCP mode). /
Maybe this should be metioned in the dhcp-proxy comment? It took me a long time to find this info.
- it worked with "dhcp-range=192.168.0.1,192.168.0.10,proxy" because dnsmasq works as normal dhcp-server and not as proxy
Sorry, seems not to be a bug at all. 192.168. 0.0,proxy" because of pxe-client problems:
After some research:
- didnt work with "dhcp-range=
/Compatibility
"Real" PXE clients do support the proxy DHCP specification, as do recent (> May 2009) gPXE clients. But older etherboot clients may be unable to get their boot information from a proxy DHCP server, so for those clients a normal DHCP server is needed (either dhcp3-server or dnsmasq in normal DHCP mode). /
Maybe this should be metioned in the dhcp-proxy comment? It took me a long time to find this info.
- it worked with "dhcp-range= 192.168. 0.1,192. 168.0.10, proxy" because dnsmasq works as normal dhcp-server and not as proxy