Out of IP's

I’ve pretty much talked myself into this, but just want a little community sign-off.

The original admin setup our network as a 192.168.0.0/24 sub net thus giving me .1 to .254 of addresses. Well we’ve been bumping pretty hard against that. I understand what all needs to be done, and I can just move us to a 192.168.0.0/23 to get twice the addressing. However what complicates things are our remote sites on VPN tunnels to our ASA. There are about 15 of them subnetted to 192.168.X.0/24 (192.168.1.0, 192.168.2.0, etc), so if I just flip us to /23 and a client here needs to see 192.168.1.20 it won’t know if that is 192.168.1.20 here or the VPN tunnel to 192.168.1.20. I know could probably tunnel using externals IPs or some funky stuff but that seems like it could get cumbersome. To make matters worse we have a local VLAN on 192.168.2.0/24 for our VoIP, that I don’t really want to touch.

So my gut tells me to pick a higher subnet say 192.168.200.0/22 giving me 192.168.200.1 to 192.168.202.254 for future-proofing (hah! Like it’s possible in IT lets say future resisting). That would put it far out enough that none of the VPN tunnels would interfere, and my VLAN wouldn’t be impacted either. Either that or move up to a 20bit 172 subnet but that seems overkill and may tax my equipment too much on broadcast traffic.

If this all makes sense and passes mustard here is my plan.

1.

Obviously starting at the ASA I have to reconfigure the internal interface. While I’m in there reconfigure all VPN connections, and reconfigure them on the remote end as well. Plus any NAT or other dozen things that could need my attention in there.

2.

Then reconfigure every statically assigned device.

3.

Setup a new DHCP scope.

4.

Detox from all the caffine and finally sleep.
Little misc info. We are a Windows 2008 shop. We use a Cisco ASA and Cisco 3560G's for the bulk of the work (there are a few workgroup switches here and there).

Anything I'm missing here??? Or any suggestions.
bhiebAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
I think you have covered all the bases.  Don't forget to make changes on your default gateway.
0
bhiebAuthor Commented:
The ASA is the gateway in our setup, sounds reasonable to me as well but I cannot overstate the glorious PITA that step 1 is going to be.
0
Chris MillardCommented:
Don't forget any changes to DNS, and if you have web services and email servers, you might have to change the IP addresses that those services listen on too.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Chris MillardCommented:
Also as you are going through this now, rather than have static IPs on some devices, why not just set them up with reserved addresses in DHCP?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bhiebAuthor Commented:
Thanks Roy, I didn't think about the other programs that use SMTP and such like you said they would all need to be changed. The reservations are a good idea as well, but most of the statics are servers and switches. Printers too of course, but I may be better served just using hostnames there.

Lots of "little" things here that I'm sure will crop up.
0
bhiebAuthor Commented:
One more thing. I was bouncing ideas around, and it wouldn't be too hard to change the one VPN site at 192.168.1.0/24. Then I could just change ours to 192.168.0.0/23. It would eliminate some of the changes needed, although if I ever need to go more than this I'd be back to this same scenario.

For example.

DNS would be fine.

Other web services Roy mentioned would be fine.

Here is the part I'm a little foggy on? VPN tunnels and NAT would need to be changed, but not necessarily right away since they would see the 192.168.0.0 subnet and as long as they don't need something in 192.168.1.0 or something in 192.168.1.0 doesn't need them. They would be fine until I get around to it.

Static boxes would be similar to VPN in that they'd see what they see now but not the .1, however there aren't that many so I'd change them.

My gut tells me this is the safer way to minimize something breaking, however it does limit me to just /23 since .2 is on a VLAN that I really don't want to fool with.

Are my assumptions here correct?
0
Chris MillardCommented:
I concur....
0
bhiebAuthor Commented:
Sorry for the slow post here, but one last question.

I've setup a test network, and all is working as suspected.

Router 192.168.0.253/23
Server 192.168.1.22/24
Printer 192.168.0.98/24
Client1 192.168.0.100/23
Client2 192.168.0.9/24

The odd thing is that client2 can see 192.168.1.22 even though the client subnet is still /24. This begs the question, what do I push as a subnet mask via DHCP to my clients. Since either /23 or /24 work fine.

In other words since either .1/24 or .0/24 both see each other, is the only place I need to change it to /23 in the gateway/router?
0
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
You need to make a decision that either everything will be part of /23 or that you will have /24  networks and in that case, you will need a sub interfaces on your router for 192.168.0.0/24 and 192.168.1.0/24 networks.
0
Chris MillardCommented:
I take it the server only has one NIC and not two?
0
bhiebAuthor Commented:
Yes the server only has one, but in production some have more.

And mnkhawajaj that is what I thought too, but then I setup client2 as .0/24 and it was able to ping 192.168.1.22. Which is what gave me pause since I thought 192.168.0.X 255.255.255.0 should NOT be able to ping 192.168.1.22 255.255.255.0 but it did just fine. The conclusion is that the gateway/route/switch routed the traffic because it viewed both class C's as one net.
0
bhiebAuthor Commented:
Bumping this up a bit to see if anyone has any answers as to why a device on 192.168.0.X/24 can see a device on 192.168.1.X/24, when only the router has been changed to 192.168.0.X/23.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Cisco

From novice to tech pro — start learning today.