We (my company) has had a private network that is 192.168.1.0/24 for some time now. We also have a co-location with networks
192.168.3.0/24, 192.168.4.0/24 and 192.168.5.0/24. The 192.168.4.0/24 network is only for the routers at the edge of the MPLS cloud at that site. The subnets 192.168.3.0/24 and 192.168.5.0/24 are unable to route back to 192.168.1.0/24 due to restrictions at the co-location. So, we translate our outgoing 192.168.1.0/24 traffic to 192.168.239.0/24. With the same configuration line (ip nat inside source static network 192.168.1.0 192.168.239.0 /24), we are able to initiate any traffic from the 192.168.3.0/24 and 192.168.5.0/24 to any host on the 192.168.1.0/24 network, as long as we remember to point to the same address with a 192.168.239 prefix.This solution has worked for a couple of months. However, now we need to add new subnets as our network has grown-192.168.236.0/24 and
192.168.237.0/24 have been offered as subnets without restrictions by our co-location. I can ping either of the new subnets from the 192.168.4.0/24 network. However, when I attempt to ping from the 192.168.3.0/24 or 192.168.5.0/24 networks, I get no response. I think the problem lies in the response getting stuck in routing on the 192.168.1.0/24 network and not being allowed by the co-location. Is there a way to use the current nat command with a route-map to NAT only when the traffic is bound for the 192.168.239.0/24 network from the 192.168.3.0/24 and 192.168.5.0/24 networks or bound for the 192.168.3.0/24 and 192.168.5.0/24 networks from 192.168.1.0/24? Any help would be greatly appreciated. Thanks.