I have a rather interesting design dilema at a client site. The client is preparing to install a router betweent themselves and a business partner for some data exchange. While discussing this with my collegues, we determined the best place to put the Business Partner router was in our WAN network. Our WAN network operates in address space 192.168.15.0/24. We currently have three other routers in that WAN network (one for MPLS, one for Frame, and one for the backup ISDN. The addresses are 15.50 (MPLS rtr), 15.4 (Frame) and 15.5 (ISDN).
This WAN network has a gateway to get to the clients INside networks at the client ASA (WAN interface IP 192.168.15.1). During planning sessions with the Business Partner a month ago, we told them that we were assigning them the IP address 192.168.15.10 and placing them into the WAN network. We were then going to NAT the devices on the Inside networks that need to talk to the BP and add the appropriate ACL entries to the ACL which we already have in place inbound on the WAN interface on the ASA.
During turn up activities with the business partner today, we found out that they cannot use the 192.168.15.10 address because there company policy mandates that they use IP address scheme 172.27.X.X.
There is a 3750 switch in between the routers and the ASA. We have a VLAN created on the switch for the WAN network.
I am not sure how to get the IP address 172.27.6.130 on the BP router to route to the 192.168.15.1 interface on the ASA.
If need be I guess we could always create another VLAN on the switch and give it a 172.27.X.X address. Then the switch would have to route to the 15.0 WAN network.
DIAGRAM IS ATTACHED
I am open for any suggestions here.
The one thing I have not been able to resolve yet is the NAT issue. They need to be able to talk to address 172.27.6.133. For us on the inside this is ip address 192.168.3.2.
Are you saying that when they access 172.27.6.133 that this should resolve to 192.168.3.2? on your end.