There are a few considerations in getting this to work. You will need to consider both tunnel directions for the traffic routing and make sure the routes installed on both sides do what you wish and that the vpn itself will accept the traffic. On the routing, the question will be what direction is the traffic initiated. Are you taking a public address on side A and forwarding requests to this address to a server on site B. Or are you taking outbound traffic from site B and forwarding this to use the ISP outbound on site A. For both cases you need to expand the policies inplace at site A and B to allow the traffic flow in the correct direction of initiation of session. For inbound traffic site A to site B you can set a normal fowarding rule to the address on the existing VPN. Then add a source nat rule to an address on site A already covered in the VPN. This won't require any VPN changes and the return traffic will work using the existing tunnel as is. For the second case you would need to make sure the outbound web addresses on site B point to the tunnel interface of a route based VPN. You should use the open proxy-id on this vpn if at all possible. If not the proxy-id pairs need to expand to include these public addresses as part of the tunnel. On site A you will need to be sure the outbound source nat rule will cover the address range coming from site B going out that ISP.
... View more