misleading documentation "dhcp-range..proxy" in examples/dhcpd-dnsmasq

[cyborg]

I tryed to install ltsp in conjunction with dnsmasq. I have an running dnsmasq on an other machine so I tried to configure dnsmasq with "proxy" instead of "leasetime". I used the examples/dhcpd-dnsmasq file but the line
#dhcp-range=192.168.0.0,proxy
should be replaced with a real range like
#dhcp-range=192.168.0.1,192.168.0.10,proxy
because at least I needed a real range. The dnsmasq logs are to short to note this error.

[Alkis Georgopoulos (alkisg)]

The example dhcpd-dnsmasq contains a normal dhcp range, which is in effect,
and a proxy dhcp range, which is commented out.

So I'm not sure I understand what you're saying; to modify the proxy dhcp range so that we have 2 identical examples?

# ip ranges to hand out
dhcp-range=192.168.0.20,192.168.0.250,1h

# If another DHCP server is present on the network, you may use a proxy range
# instead. This makes dnsmasq provide boot information but not IP leases.
# (needs dnsmasq 2.48+)
#dhcp-range=192.168.0.0,proxy

[cyborg (florian-cyborgsociety)]

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

[Alkis Georgopoulos (alkisg)]

> Sorry, seems not to be a bug at all.

OK, closing the bug report.