- Products
- Learn
- Local User Groups
- Partners
-
More
Celebrate the New Year
With CheckMates!
Value of Security
Vendor Self-Awareness
Join Us for CPX 360
23-24 February 2021
Important certificate update to CloudGuard Controller, CME,
and Azure HA Security Gateways
How to Remediate Endpoint & VPN
Issues (in versions E81.10 or earlier)
Mobile Security
Buyer's Guide Out Now
Important! R80 and R80.10
End Of Support around the corner (May 2021)
Hi,
my GW cluster is R80.10. I captured the following CCP traffic on one interface:
Network: 192.168.60.64/27
VIP: 192.168.60.65/27
Member1: 192.168.60.66/27
Member2: 192.168.60.67/27
Packets captured:
Source: 0.0.0.0 -> Destination: 192.168.60.64 - Port UDP8116
From all SKs and infos I read about CCP the packets should go to the broadcast IP 192.168.60.95, right ?
Regards Tom
Hi @TomShanti
That's all correct.
With Broadcast CCP the network IP address is always used as destination. In your case 192.168.60.64. It's not layer 3 broadcast, it's layer 2 broadcast.
Here only the broadcast MAC ff:ff:ff:ff:ff:ff is used.
Here I describe the important broadcast and multicast CCP parameters in a picture. More read here.
R80.x - cheat sheet - ClusterXL
Hi Heiko,
still not sure if this is correct 🙂
Check Point CCP packets are not able to pass through the switch when CCP is working in multicast mode (by default, the destination IP address of CCP packets is broadcast IP address for the relevant subnet).
All my readings say "broadcast IP" not "network IP".
Regards
Tom
About CheckMates
Learn Check Point
Advanced Learning
WELCOME TO THE FUTURE OF CYBER SECURITY