[Dnsmasq-discuss] Specific treatment of Class C addresses

[Jan Ceuleers]

Dear dnsmasq community,

The changelog for version 2.47 contains the following:

	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.

Unless I'm mistaken the listed Microsoft KB applies only to Windows versions that are long since past end of support. Furthermore, CIDR was introduced by the IETF more than 30 years ago.

I was therefore wondering whether it is time to retire the special treatment of addresses ending in .0 or .255 in Class C address ranges.

Many thanks, Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20240918/0558b15f/attachment.htm>