This just doesn't look right. Should probably change the design.

[Tarrant64]

Setup:

10.10.1.x - Location A. DHCP 10.10.1.100 - 254
10.10.2.x - Location B. DHCP ""
10.10.3.x - Location C. DHCP ""

Any devices requiring static address basically get the first 100 IPs and the rest are DHCP (workstations, etc.).

The locations are remote networks, state to state WANs, not really local ares. Think they're connected via VPN.

I don't think there is room for growth on these local networks, period. In Location A they've already used 100-211. I really don't think it'd be good to lower the range either to say 50-75 to 254. I think it would be better to just redo the design as this isn't going to cut it.

How much of a change would be worth it? Scrapping the whole thing and going with a Class A or B setup?

 

[spidey07]

You should be using DHCP reservations for devices that need an address, never hard code an address unless it's a server.

You could do 10.10.0.0/23
10.10.2.0/23
10.10.4.0/23

That would give over 500 addresses per site. At that size you really should be doing routing and further subnetting anyway. Just go with /22 for each site and alocate any point to point addressing as well.

 

[Tarrant64]

Originally posted by: spidey07
You should be using DHCP reservations for devices that need an address, never hard code an address unless it's a server.
You could do 10.10.0.0/23
10.10.2.0/23
10.10.4.0/23

That would give over 500 addresses per site. At that size you really should be doing routing and further subnetting anyway. Just go with /22 for each site and alocate any point to point addressing as well.

Using static IPs for not just servers, but routers, printers, etc. is fine though, right?

 

[spidey07]

Originally posted by: Tarrant64

Originally posted by: spidey07
You should be using DHCP reservations for devices that need an address, never hard code an address unless it's a server.
You could do 10.10.0.0/23
10.10.2.0/23
10.10.4.0/23

That would give over 500 addresses per site. At that size you really should be doing routing and further subnetting anyway. Just go with /22 for each site and alocate any point to point addressing as well.

Using static IPs for not just servers, but routers, printers, etc. is fine though, right?

Sorry, I meant any end device. That includes printers.

For the exact reason your OP describes - you may have to readdress and having to touch the end devices is a pain. Routers DEFINE the network, so of course they are hard coded.

 

[Tarrant64]

That's what I thought. :beer:

 

[spidey07]

Originally posted by: Tarrant64
That's what I thought. :beer:

Also DNS is your friend. Never access something by IP alone.