Yes. You can achieve that using the NAT on your end VPN device. For that you need to create an access-list with Source as your LAN(Private) IP and have the actual destination as it is (54.x.x.168) in your scenario. You just have the NAT created for this access-list with some public IP.
You crypto-map ACL should have the NATed Public IP of your local LAN IP as source and destination is already a public zone. So no change is required. On the other end they have to create the crypto map to your public IP only.
If you do like that your scenario will work without any issue.
You have to make changes @ both the ends if you have any rule....
Juniper Srx Side:
You have to NAT the 10.x.x.70 to a public IP using NAT. At the same time you have to make the required changes in crypto-map ACL of that or similar in Junos Platform. There Source is x.x.x.x (NAT IP of 10.x.x.x) & Destination would be 54.x.x.168.
On Cisco ASA side:
access-list outside_cryptomap_2 extended permit ip 54.x.x.168 host x.x.x.x ( NAT IP of 10.x.x.x)
So both the end crypto ACL negotiation will go through and communication heppens in the form of public IP to the Public IP..... That gives you the solution.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...