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
Hi Geert,
Thanks for your reply. I'm not sure I understand the full meaning of
your comments; allow me to dig a little deeper.
On 21/09/2024 09:29, Geert Stappers wrote:
> And it is OK to render the special treatment of address ending in .0 or
> .255 in /23 networks or even larger networks as "to
Signed-off-by: Jan Ceuleers
Reviewed-by: Wang Xiaobo
---
src/dhcp.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/src/dhcp.c b/src/dhcp.c
index b65facd..586117d 100644
--- a/src/dhcp.c
+++ b/src/dhcp.c
@@ -821,16 +821,9 @@ int address_allocate(struct dhcp_context
On 25/09/2024 11:06, Simon Kelley wrote:
> Downsides to this proposed change.
>
> 1) Old versions of Windows might break.
> 2) Newer versions of windows might break - we've not done testing on
> which do and don't.
> 3) Other platforms which have made the same mistake might break.
> 4) Dnsmasq inst
On 25/09/2024 11:06, Simon Kelley wrote:
> Downsides to this proposed change.
>
> 1) Old versions of Windows might break.
> 2) Newer versions of windows might break - we've not done testing on
> which do and don't.
> 3) Other platforms which have made the same mistake might break.
> 4) Dnsmasq inst
