I come back with my NAT story...
I have a problem.
Please watch the diagram attached.
My site (green) is connected to my customer (violet) thru a VPN IPsec.
My Encryption Domain is my public range (188.8.131.52/28) and the remote Encryption Domain is 184.108.40.206/24.
My Peer is 220.127.116.11 and the remote peer is 18.104.22.168.
VPN are mounted between a CheckPoint and an ASA Cisco 5555.
The CheckPoint is carrying the virtual IP (22.214.171.124) for the NAT of SRV001 with an ARP Proxy.
My customer thru the VPN has to communicate with SRV001 via the NATed IP 126.96.36.199.
Then the check has to NAT it to 192.168.1.100.
On the other sense, SRV001 has to communicate with SRV_CUSTOMERS (188.8.131.52, 184.108.40.206)
When SRV001 initiate the communication, the CheckPoint has to NAT is IP from 192.168.1.100 to 220.127.116.11 and then to send it thru the VPN.
On the other case SRV001 no need to be NATed for corporate communication.
Right now, my VPN Tunnel is UP.
When I am pinging the 18.104.22.168 or 22.214.171.124 with the CheckPoint it's working going thru the VPN Tunnel.
When I am pinging the 126.96.36.199 or 188.8.131.52 from SRV001, I saw with TCPDUMP that the firwall on the customer interface make the NAT and replace the 192.168.1.100 with the 184.108.40.206 but the trafic is not going thru the VPN.
How to force to send the NATed packet thru the VPN?
Support NAT-Traversal is enabled.
I saw the option in the VPN Communities the option "Disable NAT inside the VPN communitie", what is it doing?