- Products
- Learn
- Local User Groups
- Partners
- More
What’s New in Device Diagnostics?
Dec 2nd @ 5pm CET / 11am EST
AI Security Masters
Security in the Pace of AI:
From Threat to Force Multiplier
CPX is Back!
Join us in Las Vegas, Vienna, and/or Bangkok!
Check Point Named a Leader
The Forrester Wave:
Enterprise Firewall Solutions, Q4 2026
What’s New in Agentic Network Orchestration
CheckMates Go:
Fun Ding
Hi!
Has anyone seen following:
Gaia gw has about 150 VLAN interfaces.
Now 2 VLAN interfaces has started to function as proxy arp and they respond to every arp request. Causes duplicate address errors on hosts in those VLANs. Same in both cluster members.
/proc/sys/net/ipv4/conf/<interface>/proxy_arp files all show 0
fw ctl arp shows a lot of entries, local.arp -file has no entries
Any ideas?
Actually found a configuration mistake, where large network was accidentally configured with automatic Static NAT instead of hide nat...and naturally large range of public addresses(partially overlapped these two networks) were taken to this. Fixed it to hide NAT.
Hi,
Do you have more information for us? Version, hotfix, VSX or non-VSX.
Did you configure NAT on objects and enabled Automatic Proxy ARP in the Global Properties?
Maybe the wrong NAT address is configured causing the gateway to Proxy ARP for those addresses.
Martijn
Automatic static NAT on a network or address range object can result in a LOT of proxy ARP entries for what seems like a very small amount of config.
Agreed have seen this many times, there really should be some kind of warning or popup when an automatic static NAT is configured on a network object instead of a host object.
With fw ctl arp you should see only the proxy arp configured on your firewall; you should also check in CLISH with the command show configuration proxy arp if there are any proxy arp configuration.
And as suggested by @Martijn check the automatic nat configuration.
Actually found a configuration mistake, where large network was accidentally configured with automatic Static NAT instead of hide nat...and naturally large range of public addresses(partially overlapped these two networks) were taken to this. Fixed it to hide NAT.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 30 | |
| 8 | |
| 7 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |
Tue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseThu 03 Dec 2026 @ 11:00 AM (EST)
Under the Hood: Check Point Cloud Firewall for Nutanix - How to Secure your AI WorkloadsTue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseThu 03 Dec 2026 @ 11:00 AM (EST)
Under the Hood: Check Point Cloud Firewall for Nutanix - How to Secure your AI WorkloadsAbout CheckMates
Learn Check Point
Advanced Learning
WE SECURE YOUR AI TRANSFORMATION