- 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
What'll happened when i'll perform "fwaccel off"? Gateway just will more slowly process new connections?
As per sk162492 it will depend on the gateway version.
It will disable acceleration until turned back on or the gateway is rebooted, are you trying to troubleshoot something in particular?
Typically it is recommend to do this (only temporarily) out of peak times or with headroom to cater for a load increase.
If after running fwaccel off you find that whatever issue you have is solved, instead of turning of SecureXL for all traffic permanently via cpconfig, consider excluding the problematic IP address(es) from acceleration as described here:
sk104468: How to disable SecureXL for specific IP addresses
After defining this exclusion everything matching it will always go F2F/slowpath, which has the side effect of making the matched traffic fully visible if using fw monitor.
I have a TAC case right now where 3 specific IP addresses are involved all over port 8080, so I may use this. This traffic started misbehaving right when we went from 5800 to 9300 appliances. That being said what kind of debugs would be helpful in figuring out why acceleration isn't working for that traffic?
I assume you mean why these connections are misbehaving when partially/fully accelerated, this is not generally something you can troubleshoot easily without TAC as it can involve sim debugs which can easily hurt performance or kill the firewall.
What you could do is get a packet capture with fw monitor -F and also run fw ctl zdebug + drop while trying the problematic accelerated connections. Now put them into the slowpath via sk104468, run the debug commands again with the test traffic and see what is different. However you need to be mindful of the order in which you run these two debugging commands as they can interfere with each other, see here: Max Capture Update 2: Debug Filter Battle -- fw monitor -F vs. fw ctl zdebug + drop
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 10 | |
| 9 | |
| 7 | |
| 6 | |
| 6 | |
| 6 | |
| 4 | |
| 3 | |
| 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 defensaThu 26 Nov 2026 @ 10:00 AM (CET)
The Cloud Architects Series: Cloud Security State in 2026 – Lessons Learned and a Look AheadWed 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