DHCP Superscope

[Sanm2009]

I think I understand how a Superscope will work, but just want to make sure I am not missing anything.

 

We were given an IP range on a 255.255.255.0 subnet which gives us 254 clients. We are getting close to maxing out on the addresses available.

 

We are moving to an external internet provider soon and will be able to choose the IP range. I don't want to change the current IP range, but I want to future proof us. It seems superscoping will do what we need (we can keep our current range and also add other ranges)

 

So if currently we have 172.66.23.1 - 172.66.23.254 on 255.255.255.0

 

Could I add 172.66.24.1 - 172.66.24.254 on 255.255.255.0

and 172.66.25.1 - 172.66.25.254 on 255.255.255.0

and 172.66.26.1 - 172.66.26.254 on 255.255.255.0

 

So as long as all these ranges are configured on the router and I create a superscope on DHCP, all should work? or have a missed something.

[pantscat]

Do you currently have 172.66.23.1 - 254? Those are public IP addresses, not private internal ones.

[Jamman960]

you may be better off changing as that range isn't part of the ranges reserved for private networks (172.16.0.0 -- 172.31.255.255 is) so either your existing ISP owns that particular range or they've just assigned it anyway(for some stupid reason our network is using the 147.0.0.0 range and I've never had the time to change it)

 

the only time you'd run into problems is if you needed to access resources on a host within that range, in your case if you were to one day link networks with a local school that had been assigned one of your new ranges you'd run into issues so it may be slightly more likely.

[Sanm2009]

I made a mistake. The range is 172.18.x.x and we are part of a LEA network. These are our internal IP addresses. I want to keep this range and add a few other ranges.

 

so 172.18.1.x & 172.18.2.x 172.18.3.x and so on....

[pantscat]

Do you particularly want to maintain separate subnets? or will you be implementing VLANs to segregate traffic?

 

If so - then a superscope is an option... otherwise I'd just change the subnet mask and adjust your DHCP scope.

[Sanm2009]

I just don't want to change the subnet right now (While other changes will be taking place.)

 

Maybe I can stay on the current range while the internet connection is setup and get another IP bigger range configured on the router, which we can start using at a later stage.

 

Are there any issues with using a superscope? Can all devices on the different scopes of the superscope see each other? If so, then what is the issue with using it?

[pantscat]

Are there any issues with using a superscope? Can all devices on the different scopes of the superscope see each other? If so, then what is the issue with using it?

 

Because the devices will be on different subnets they won't be able to see each other or communicate with each other unless you setup routing between them either on your router or a suitable layer 3 switch.

[Roberto]

Are there any issues with using a superscope? Can all devices on the different scopes of the superscope see each other? If so, then what is the issue with using it?

 

As has been pointed out, creating a superscope will do nothing for routing, which will need to be addressed too.

 

Superscopes are rarely a good idea in my opinion. They are a complex way of solving a problem like this, it's nearly always preferable to just create a "proper" DHCP scope of the correct size.