- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
10 December @ 5pm CET / 11am ET
Improve Your Security Posture with
Threat Prevention and Policy Insights
Overlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Hi All
We had an issues yesterday whereby we created a static NAT on the object but it didnt work.
We found that we needed to manually put the proxy arp entry on the gateway.
We have the global properties set to automatic arp configuration and merge manual proxy arp configuration set.
I thought that when doing automatic rules such as on the object you dont need to add it manually on the gateway? why would this not have worked ?
Cheers
The automatic static NAT rule adds the proxy arp during policy install and as long as there are no typos then the expected behaviour is that the gateway/cluster 'takes responsibility' for the static NAT IP address. Meaning that it replies to the ARP WHO HAS with the interface in the relevant subnet.
If you double checked everything, which I am sure you did, and maybe some packet captures to see the behaviours on the network (looking for ARP WHO HAS and ARP IS AT), then it may be a problem with the software (bug).
The fact that it worked with a Gaia level proxy arp seems to point to a software of config error.
Sounds like one for TAC if you have done all the checks.
Automatic static NAT rules should add a proxy arp entry into the kernel running config.
The command to check it on the gateway/s after the policy installation is:
fw ctl arp
Was it a Host object and a standard configuration? Meaning nothing complicated, just a normal host static NAT.
Hi, yes it was a host object with the static NAT config applied, it only seemed to work if we added the manual proxy arp entry on Gaia.
If i removed the manual proxy arp entry and typed fw ctl arp, it was actually showing in there
Did you install policy after making the change?
Was the mac-address the expected one for the given cluster member?
Hi Chris, yes and yes
Hey Carl,
I would agree with Don on this one. If you checked everything, TAC case sounds like the best idea at this point.
The automatic static NAT rule adds the proxy arp during policy install and as long as there are no typos then the expected behaviour is that the gateway/cluster 'takes responsibility' for the static NAT IP address. Meaning that it replies to the ARP WHO HAS with the interface in the relevant subnet.
If you double checked everything, which I am sure you did, and maybe some packet captures to see the behaviours on the network (looking for ARP WHO HAS and ARP IS AT), then it may be a problem with the software (bug).
The fact that it worked with a Gaia level proxy arp seems to point to a software of config error.
Sounds like one for TAC if you have done all the checks.
share screenshot to make sure no mistakes are made from the host object
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 22 | |
| 21 | |
| 8 | |
| 7 | |
| 5 | |
| 5 | |
| 4 | |
| 3 | |
| 2 | |
| 2 |
Thu 04 Dec 2025 @ 02:00 PM (EST)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - AmericasThu 04 Dec 2025 @ 02:00 PM (EST)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - AmericasFri 12 Dec 2025 @ 10:00 AM (CET)
Check Mates Live Netherlands: #41 AI & Multi Context ProtocolTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY