- Products
- Learn
- Local User Groups
- Partners
- More
The State of Ransomware Q1 2026
Key Trends and Their Impact
Good, Better, Best:
Prioritizing Defenses Against Credential Abuse
AI Security Masters E7:
How CPR Broke ChatGPT's Isolation and What It Means for You
Blueprint Architecture for Securing
The AI Factory & AI Data Center
Call For Papers
Your Expertise. Our Stage
CheckMates Go:
CheckMates Fest
I solved this issue by installing keepalived on Linux. Here's my working configuration:
global_defs {
router_id XXXX
enable_script_security
script_user root
}
# Monitor Firewall 1 via ens6f0
vrrp_script check_fw1 {
script "/usr/bin/fping -I ens6f0 -c 2 -t 500 x.x.x.x"
interval 3
weight -50
fall 2
rise 2
}
# Monitor Firewall 2 via ens6f1
vrrp_script check_fw2 {
script "/usr/bin/fping -I ens6f1 -c 2 -t 500 x.x.x.y"
interval 3
weight -30
fall 2
rise 2
}
vrrp_instance GW_FAILOVER {
state MASTER
interface ens6f0
virtual_router_id 51
priority 100
advert_int 1
virtual_ipaddress {
169.254.1.1/32 dev ens6f0
}
track_script {
check_fw1
check_fw2
}
notify_master "/etc/keepalived/use_fw1.sh"
notify_backup "/etc/keepalived/use_fw2.sh"
}#!/bin/bash logger -t KEEPALIVED "Using FW1 via ens6f0" ip route replace default via x.x.x.x dev ens6f0 metric 10
#!/bin/bash logger -t KEEPALIVED "Switching to FW2 via ens6f1" ip route replace default via x.x.x.y dev ens6f1 metric 20
chmod +x /etc/keepalived/*.sh systemctl restart keepalived
The solution uses weighted priorities to determine failover:
When an interface goes down, the fping check automatically fails (can't ping through a down interface), triggering the appropriate failover.
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY