Nat rule over tunnel/community

[PIAndre]

Hi.  Im trying to redirect traffic going out a gateway.  I want to change the traffic flow from:

host_a (port 443) -> checkpoint_gateway -> internet -> public ip on host_b

to:

host_a (port 443) -> checkpoint_gateway -> nat from public ip on host_b to private ip on host_b -> s2s ipsec tunnel -> private ip on host_b

The tunnel works fine for normal traffic flow over the tunnel and all the security domains are defined properly.  There are rules in the policy that the traffic should hit to go over the tunnel.  When I try to create a nat rule to change the public ip to the private ip of host_b the traffic is allowed and I see the translation but It doesnt get encrypted.  Its also skipping my tunnel rule and hitting my default outbound rule at the bottom.  What am I missing in my nat rule to get this traffic flow working?

[PhoneBoy]

Is the Public IP included in your encryption domain for the remote site?

[PIAndre]

I just tested with one host behind the gateway.  So the nat rule looks like this:

original source - test_host

original destination - public ip on host_b

original services - any

translated source - original

translated destination - private ip on host_b

translated services - original

install on - checkpoint_gateway

I see the traffic getting encrypted but the nat isnt getting applied.  Anything else im missing?

[PhoneBoy · Accepted solution]

There's an option to disable NAT in the VPN Community--see if that's set.

[PIAndre]

That did it. Had that box checked and unchecked it. Thanks.

[Maarten_Sjouw]

You need to make sure that the Public ip host_b and translated IP for Host_b is part of the remote VPN domain.
NAT finds place as one of the last parts in the outbound chain and this traffic should already be seen as traffic to send to the other side of the tunnel before that NAT takes place.