We have a very simple setup an external router which routes a dedicated public ip range (1.1.1.1) to an external Check Point firewall. On this firewall we use public nat range to publish a service however there is no destination nat performed, the packet is forwarded towards the internal interface and spoofing blocks the traffic. The router and firewall are connected via another ip subnet so the check point firewall public interface is configured on another subnet not belonging to 1.1.1.x. The external interface is configured to the internet allowing all source IP.
The original packet is coming in from the correct public interface we validated via tcpdump, so the issue here is that simply the destination nat is not performed.
The global properties are set to perform pre nat so on the interface where is arrives. We tried to move the manual nat rules higher in the rulebase but still no luck with this.
We have similar setup working elsewhere but here the destination nat rule does not seem to be matched, executed, any ideas how to fix this, would could be the problem here?