Hi
Mattias has covered how to NAT your source IP addresses but it is not quite as simple as that.
If you are both using the 10.0.0.0/24 network then lets say a client in your lan eg. 10.0.0.5 wants to communicate with a client in the partner network eg 10.0.0.8.
Your client will think that the 10.0.0.8 machine is on your local network and will arp out for it. It would never know that 10.0.0.8 was down the VPN tunnel. Indeed if you have a machine with 10.0.0.8 in your local network it will talk to that instead.
It also depends on which way the communications are intiated. If they are initiated both ways then you need to setup static translations for these at your end.
So to keep it simple lets say you always initiate the connection (if this is not the case we can cover that later).
Further lets say you need access to
10.0.0.10, 11, 15 & 27 at the partner site.
Now you can use the NAT that mattias has provided for your clients.
As for the destaintion addresses, you need to present the partner IP addresses as something else to your internal clients.
static (outside,inside) 10.40.40.10 10.0.0.10 netmask 255.255.255.255
static (outside,inside) 10.40.40.11 10.0.0.11 netmask 255.255.255.255
static (outside,inside) 10.40.40.15 10.0.0.15 netmask 255.255.255.255
static (outside,inside) 10.40.40.27 10.0.0.27 netmask 255.255.255.255
Your clients now need to point to the 10.40.40.x addresses when they want to communicate with the remote site.
Hope this makes sense
Jon
** Edit - apologies i didn't read the entire thread. I assumed you needed to talk to 10.0.0.0/24 network at the partner site and having re-read the thread i realise this isn't the case. Please ignore post - very sorry to the OP and to Mattias ***
