Basically, Peer 1 (VPN 1) needs my internal address nat'd to my public address prior to being encrypted,
and currently it is working the way it is setup. Of course, the permit ip any any guarantees that,
but also exludes getting the second tunnel properly setup.
So, for VPN1:
ip access-list extended NAT_VPN_1
permit ip 10.10.10.0 0.0.0.255 REMOTE_LAN
route-map VPN_1
match ip address NAT_VPN_1
set ip next-hop x.x.x.x
ip nat inside source route-map VPN_1 interface FastEthernet0/1 overload
access-list crypto1 permit ip host OUTSIDE_IP REMOTE_LAN
The above configuration, will NAT the traffic from 10.10.10.0/24 to the outside public IP of the router ONLY when going to the REMOTE_LAN
Peer 2 (VPN 2) needs to have my internal address nat'd to 10.139.40.0 prior to being encrypted
and sent to his network. The only host in his network that i need to talk to is 10.10.131.63.
ip access-list extended NAT_VPN_2
permit ip 10.10.10.0 0.0.0.255 host 10.10.131.63
route-map VPN_2
match ip address NAT_VPN_2
set ip next-hop x.x.x.x
ip nat pool newpool 10.139.40.1 10.139.40.254 netmask 255.255.255.0
ip nat inside source route-map VPN_2 pool newpool
access-list crypto2 permit ip host 10.139.40.0 0.0.0.255 REMOTE_LAN
The above configuration will NAT the 10.10.10.0/24 to 10.139.40.0/24 when going to 10.10.131.63
Please check the configuration to see if it meets what you need.
Federico.
