Mip and Destination NAT in the same rule
I have a route based VPN that i have a bit of a messy request for.
The servers on my side will both have to be source translated (i guess by mip) and i also need to make a destination translation.
Se my example, Server A (for example 192.168.0.1) is the server on my site, i translate that to 192.168.1.1) and it connects to NAT address (10.0.0.1) is the address the server are connected to, and server B (184.108.40.206) is the server it acctuly connect to.
192.168.0.1 (192.168.1.1) -> 10.0.0.1-> 220.127.116.11
So server A thinks its connecting to 10.0.0.1 but in reallity it connects to 212.212.212 and 18.104.22.168 see it as the source 192.168.1.1.
I cant get both MIP and Destination nat to work. It just do the destination NAT and not the mip stuff.
Any idea of how to accomplish this?
I dont “control” the other side of the VPN its a other partner/client. Im migrating all the VPN:s from a other vendor to a netscreen cluster. In the old enviorment this (weird) setup with both source and destionation NAT is working, so i would prefer to solve it without have to involve the other client/partner so much.
So wouldn’t a mip from 192.168.1.1 to 192.168.0.1 on on sideand a MIP from 10.0.0.1 to 22.214.171.124 on the other side of the vpn work?