[Dnsmasq-discuss] Release candidate dnsmasq-2.47rc1

[Olaf Westrik]

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.
>   

really?

Unless you are doing something like

--dhcp-range=192.168.0.254,192.168.1.1,255,255,254.0

(which is a pretty weird thing to do if you ask me), you have a fairly 
large dynamic IP range.
Now *I* am not going to sit down and look which IP addresses are left 
unused in a /23 network.
When 500-something IP addresses are used, it is time to either enlarge 
the supernet or split the network into two (or more) networks.


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).


Olaf

-- 

A weizen a day helps keep the doctor away.