Expanding IP range on DHCP server for 800+ devices
We are expanding the internet access to the entire school body and we will need 800+ ip addresses to accommodate them all. the existing DHCP range is 192.168.1.0 with a Mask of 255.255.255.0 the default Gateway is at 192.168.1.254. if i open the mask to 255.255.248.0 it moves it to a class B network, so does that mean i have to change my existing ip address range from 192.168.x.x to a class B range? If i set the range from 192.168.1.0 to 192.168.7.255 using subnet mask of 255.255.248.0 I will have to move the Default Gateway from 192.168.1.254 to something outside the range. i tried to start the rang at 192.168.2.1 to keep the DFGW at 192.168.1.254 but i get an error saying the gateway is not on the correct subnet? Is there a better way to do this?
Thank you
DHCPWindows NetworkingNetworking
Last Comment
Qlemo
8/22/2022 - Mon
masnrock
if i open the mask to 255.255.248.0 it moves it to a class B network, so does that mean i have to change my existing ip address range from 192.168.x.x to a class B range?
If by that you mean whether you need to update the subnet mask on existing devices, then yes. You definitely will need to figure out how you want to have your DHCP scopes working.
If i set the range from 192.168.1.0 to 192.168.7.255 using subnet mask of 255.255.248.0 I will have to move the Default Gateway from 192.168.1.254 to something outside the range.
You don't *have* to, but you do need to be sure that the gateway address stays out of the DHCP range.
How is the school laid out? VLANs may make more sense. You might have VLANs by floor, by type (wired, wireless, security devices, etc). It adds complexity, but also introduces better organization if done correctly.
mspencer100
ASKER
i guess the question is do i have to change the IP address to a proper Class B address 172.x.x.x or can i keep the 192.168.1.x range if i change the subnet mask to 255.255.248.0?
Peter Hutchison
You can convert to a Class B range (ie 172.16.0.0/12 ) or go fully to a Class A range (10.0.0.0/8). As masnrock says, switching to proper VLANs would make sense in a medium to large organisation.
Best practise is using a VLAN, but that requires appropriate hardware. I think you should not improvise because the last thing you want is a network as a bottleneck in the system.
You did not mentioned what kind of hardware you have and if DHCP is on router/firewall or some Server.
If you can consider server based DHCP the simplest way is to create multiscope.
This will require to have a firewall with 4 LAN connections that you can assign as a gateways for each scope in superscope, but it's very easy to set and is working very good.
masnrock
While this question has been abandoned, the OP's question has certainly been answered (even though it isn't known what approach was taken at the end of the day).
#a42416997 correct answer #a42417009 correct and important expansion on that answer #a42417064 is summarizing both, and might receive some points (or not)
I recommend an equal split between the first two comments listed.
You don't *have* to, but you do need to be sure that the gateway address stays out of the DHCP range.
How is the school laid out? VLANs may make more sense. You might have VLANs by floor, by type (wired, wireless, security devices, etc). It adds complexity, but also introduces better organization if done correctly.