We wish to create a L2L VPN with our vendor. They require us that when our Internal traffic goes thru the VPN tunnel, that it must be translated to 10.1.0.8/32. So in other words, traffic sourcing from OUR internal network that is destined to the vendor internal network must seem to them like it's coming from 10.1.0.8/32.
A simple diagram would be like so:
192.168.1.0/24---->translate to 10.1.0.8 only for this VPN tunnel---->192.168.50.0/24 (vendor int. network)
Below is how I think I should configure my ASA. Any suggestions would be appreciated.
ip address 192.168.1.1 255.255.255.0
ip address AA.183.142.222 255.255.255.224
access-list E-MD extended permit ip host 10.1.0.8 192.168.50.0 255.255.255.0
access-list policy-nat extended permit ip 192.168.1.0 255.255.255.0 192.168.50.0 255.255.255.0
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0
global (outside) 5 10.1.0.8 netmask 255.255.255.255
nat (inside) 5 access-list policy-nat
crypto map outside_map 20 match address E-MD
crypto map outside_map 20 set peer BB.179.80.108
crypto map outside_map 20 set transform-set ESP-3DES-SHA
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...