- Products
- Learn
- Local User Groups
- Partners
- More
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
Good, Better, Best:
Prioritizing Defenses Against Credential Abuse
Ink Dragon: A Major Nation-State Campaign
Watch HereCheckMates Go:
CheckMates Fest
Hi Mates,
A VPN has been configured between a Check Point R81 and Fortinet version 7.6 firewalls. After the initial VPN configuration, traffic is successfully traversing the two firewalls. If there is no traffic continually traversing the VPN for more than an hour, then the VPN appears to be broken and does not allow any traffic outbound from Check Point, unless the VPN reconfiguration is carried out on the Check Point firewall, however inbound traffic to the Check Point firewall is working fine.
Any suggestions to fix this?
Enable permanent tunnel option with specific community and test.
The Permanent Tunnels feature will send a UPD 18234 packet (tunnel testing) which is proprietary, so the FN gateway will not understand it. It may work just because of the traffic flow in the tunnel.
What do the logs say?
Ah, fortiOS 7.6.x, lots of new features, but still feature release, so I would stick with 7.4, which is latest mature code : - )
Anywho...make sure on Fortigate, setting auto keep alive is enabled and on CP exactly what the guys mentioned.
Andy
Sounds like VPN timers are not the same on both sides. Would check p1 and p2 on both side and make sure they match.
Are you sure you run R81? and not R81.10 or R81.20? If so upgrade due EOL status
Always great sk to refer to, Don.
On hour is default phase2 re-key timer (as @Lesley noted. Be sure your implied rules enable VPN control connections and that you aren't trying to control IKE, IPsec, and (if applicable) NAT-T connections in your security policy.
Personally, I would never change those without checking with TAC first.
Andy
You have Remote Access control connections disabled. This needs to be enabled for all of IPsec to function. You also have Accept ICMP Requests enabled, which is not the default (and you almost certainly do not want this). Someone has modified these implied rules in the past. You should review the defaults again and re-align these.. Here's a screenshot from sk179346.
https://sc1.checkpoint.com/sc/SolutionsStatics/sk179346/implied%20rules202205261210461.png
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 64 | |
| 21 | |
| 13 | |
| 12 | |
| 12 | |
| 9 | |
| 8 | |
| 7 | |
| 7 | |
| 7 |
Tue 21 Apr 2026 @ 05:00 PM (IDT)
AI Security Masters E7: How CPR Broke ChatGPT's Isolation and What It Means for YouTue 28 Apr 2026 @ 06:00 PM (IDT)
Under the Hood: Securing your GenAI-enabled Web Applications with Check Point WAFTue 21 Apr 2026 @ 05:00 PM (IDT)
AI Security Masters E7: How CPR Broke ChatGPT's Isolation and What It Means for YouTue 28 Apr 2026 @ 06:00 PM (IDT)
Under the Hood: Securing your GenAI-enabled Web Applications with Check Point WAFThu 30 Apr 2026 @ 03:00 PM (PDT)
Hillsboro, OR: Securing The AI Transformation and Exposure ManagementAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY