asked on

NATing

Two simple networks connected by two cisco 1711s. Both networks are using class c addresses. So... when data moves from one site to another and the destination IP is used at both sites will I have a conflict? And if so how do I setup NATTing to ensure it doesn't happen?

ASKER CERTIFIED SOLUTION

Les Moore

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

pseudocyber

>>destination IP is used at both sites will I have a conflict YES

http://www.cisco.com/en/US/tech/tk648/tk361/tk438/tsd_technology_support_sub-protocol_home.html

NETWORK ADDRESS TRANSLATION (NAT)
Network Address Translation allows a single device, such as a router, to act as agent between the Internet (or ""public network"") and a local (or ""private"") network

glebn

I assume you mean you're using the same private IP at both sites. For example, both sites might have a network 10.10.10.0/255.255.255.0 with hosts with the IP 10.10.10.10. Assuming these networks are connected to one another exclusively via the Internet (without a VPN or similar tunnelling technology) then you will not have a problem as the two hosts never see the internal IP of each other, they only see the IP's of the router for the other computer's network. However, you will have a problem if either these two network are connected directly together via their routers (e.g. using a direct WAN connection) or if you try to VPN from within one network to the other network. Therefore, it is best if you can do it to subnet the two networks separately. For example, setup one with 10.10.10.0/255.255.255.0 and the other 10.10.11.0/255.255.255.0.

harbor235

Or you could just readdress one end into a unique address range to eliminate the overlap. I am not sure if this is doable
but it would make things easier in the long run. (just my 2 cents). ;}

harbor235

glebn

harbor235's advice is exactly right, but I too suggested this in my response. It is definitely best to keep two sites with any kind of relationship (technological or any other) subnetted differently. As there is no shortage of available private addressing you should not have a problem doing this.

Unless you have a very large network or your network is being used by a lot of users 24/365 then it shouldn't be too hard to switch. As a first step I would reduce your DHCP lease time to a very short time. Then wait at least 1/2 the current least time (e.g. if the current lease time is 7 days, wait at least 4 days) before switching. If you switch on a Friday night all hosts should get new IP's before anyone notices. If you could force a reboot or "ipconfig /renew" for all hosts after the change that would be even better.