Using a DHCP range of /23 does not seem to work correctly #282

New issue

Open

opened 2026-02-20 08:21:43 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-20 08:21:43 -05:00

Owner

Originally created by @thomasaldershof on GitHub (May 23, 2025).

Hello all,

I changed my DHCP range to /23 to increase the number of devices and allow static ips in another range. I can see the KVM popup on my DHCP server, however the ip I see there does not work, and the KVM itself displays 192.168.1.255 (my range is 192.168.0.1 to 192.168.1.254) and the IP my DHCP assigns is 192.168.0.9. Setting a static IP does not seem to help. It seems the IP it reports is the broadcast ip. Hooking it up to my Windows pc with internet sharing enabled works fine.

The DHCP server I'm using is technitium, if there is anything I can check let me know.

Originally created by @thomasaldershof on GitHub (May 23, 2025). Hello all, I changed my DHCP range to /23 to increase the number of devices and allow static ips in another range. I can see the KVM popup on my DHCP server, however the ip I see there does not work, and the KVM itself displays 192.168.1.255 (my range is 192.168.0.1 to 192.168.1.254) and the IP my DHCP assigns is 192.168.0.9. Setting a static IP does not seem to help. It seems the IP it reports is the broadcast ip. Hooking it up to my Windows pc with internet sharing enabled works fine. The DHCP server I'm using is technitium, if there is anything I can check let me know.

deekerman added the

component: network

label

2026-02-20 08:21:43 -05:00

deekerman commented

2026-02-20 08:21:43 -05:00

Author

Owner

@solemnwarning commented on GitHub (May 23, 2025):

FWIW, I got mine today and its working fine on a /23 subnet using ISC DHCP server.

@solemnwarning commented on GitHub (May 23, 2025): FWIW, I got mine today and its working fine on a /23 subnet using ISC DHCP server.

deekerman commented

2026-02-20 08:21:43 -05:00

Author

Owner

@thomasaldershof commented on GitHub (May 23, 2025):

Hmm then I wonder why it gives me the broadcast ip. Since 192.168.1.255 is not a valid IP it shouldn't even get it. Interesting to hear that you don't have any issues with it...

@thomasaldershof commented on GitHub (May 23, 2025): Hmm then I wonder why it gives me the broadcast ip. Since 192.168.1.255 is not a valid IP it shouldn't even get it. Interesting to hear that you don't have any issues with it...

deekerman commented

2026-02-20 08:21:44 -05:00

Author

Owner

@solemnwarning commented on GitHub (May 24, 2025):

You mentioned changing it - I wonder if the DHCP client cached something of the previous /24 subnet and didn't handle the subnet size changing correctly.

@solemnwarning commented on GitHub (May 24, 2025): You mentioned changing it - I wonder if the DHCP client cached something of the previous /24 subnet and didn't handle the subnet size changing correctly.

deekerman commented

2026-02-20 08:21:44 -05:00

Author

Owner

@thomasaldershof commented on GitHub (May 28, 2025):

Maybe, but it seems to switch between DHCP ranges on /24 okay. Any idea how I can debug this?

@thomasaldershof commented on GitHub (May 28, 2025): Maybe, but it seems to switch between DHCP ranges on /24 okay. Any idea how I can debug this?