Okay – this isn’t really adding a true class-c subnet, but rather more like treating a private class c as a class b.
Our small network is reaching the available threshold of dhcp/all addresses. We have a private network at address: 192.168.1.0.All of the servers, several print servers, and the router/switches occupy static addresses in the lower numbers. Above about .70, we have a scope of DHCP addresses.
Question: If we want to avoid migrating to a class b (or a) private address, canwe simply add the 192.168.0.0 or 192.168.2.0 addresses to the dhcp server, and change the subnet mask on the DHCP server from 255.255.255.0 to 255.255.254.0 or drop more bits for future ranges?
Reason: We have devices spread city-wide with staticaddresses. Migration would cost some down-time. Our firewall supports addresses: 192.168.any.any for internal routing. If we could do this, we would have more addresses than necessary.
Possible Implications: Would devices assigned a .0.0 address communicate with the .1.0 devices, as long as the subnet mask is the same and allows for both?
