[Dnsmasq-discuss] Release candidate dnsmasq-2.47rc1

[Carlos Carvalho]

Olaf Westrik (weizen_42 at ipcop-forum.de) wrote on 28 January 2009 08:03:
 >Carlos Carvalho wrote:
 >> Simon Kelley (simon at thekelleys.org.uk) wrote on 27 January 2009 22:03:
 >>  >             Don't dynamically allocate DHCP addresses which may break
 >>  >             Windows.  Addresses which end in .255 or .0 are broken in
 >>  >             Windows even when using supernetting.
 >>  >             --dhcp-range=192.168.0.1,192.168.1.254,255,255,254.0 means
 >>  >             192.168.0.255 is a valid IP address, but not for Windows.
 >>  >             See Microsoft KB281579. We therefore no longer allocate
 >>  >             these addresses to avoid hard-to-diagnose problems.
 >>
 >> Which in turn may produce hard-to-understand no-free-leases
 >> problems... Please make it an option.
[...]
 >If it will be an option (say 
 >--break-windows-client-caused-by-strange-concept-of-supernets), I want 
 >the default to be to not break the windows dhcp client(s).

Fine for me, with the option I don't mind what the default is.