- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
Watch NowOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
At R80.20 there's a new hack to turn the CoreXL instances on the fly on and off. Here is an example with 3 CoreXL instances!
Now start the command:
# fw ctl multik stop -> stop CoreXL instance 1
![]()

# fw ctl multik stop -> stop CoreXL instance 2
![]()

# fw ctl multik stop -> The last instance cannot be disabled:-)
![]()
You can activate it again per:
# fw ctl multik start
Conclusion:
CoreXL 0 cannot really be deactivated under R80.10+:-)
More see here:
To be honest I’m not sure what benefit this has.
There is nothing in the documentation about the cli command.
In the maintenance window I tested it on a bigger firewall. I could not see any negative impact.
That I only wonder, that the session counter will not be lower.
I just looked it over at the lab. The existing sessions are not affected.
Maybe someone from R&D can tell whether this has a negative impact or not.
I see here only the performance decrease if I disable CoreXL instances.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 12 | |
| 10 | |
| 9 | |
| 8 | |
| 6 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |
Tue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY