CR1000A: more restrictive subnetmask causes DHCP server to fall over

Mike386

Since I'm never going to have 254 hosts on my home network, I thought I'd restrict the number of hosts to 62 by changing the IPv4 subnetmask to 255.255.255.192 for the local LAN . It seemed to be working fine, until I realized that the DHCP server was no longer responding to requests, so I restored the class C subnetmask. Note that I did the typical router reboots after I made these changes.

Has anyone else tried this and had it work? (I'm wondering if I have to do a factory reset and start over to get this to work).

Thanks.

Mike386

I forgot to mention in the original posts that wifi and wired devices with manually set IP addresses worked fine with the 255.255.255.192 subnetmask. Clients that needed a DHCP server were out of luck.