- Products
- Learn
- Local User Groups
- Partners
- More
AI Security Masters E7:
How CPR Broke ChatGPT's Isolation and What It Means for You
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
We are happy to announce Check Point Quantum Spark R82.00.10 has been released!
This Release extend R82 support for Pro appliance, includes more R82 features, alongside a suite of other features and enhancements for both locally and centrally managed gateways.
The Release also adds support for the upcoming 2550 5G and 2570 5G Appliances.
Key Version Highlights:
R82 features
Networking Enhancements
SDWAN Enhancements
IPV6 enhancements
New Hardware
For additional information and release notes, please refer to: sk184357
Click here to see the general playlist of feature videos
Not sure if it is related but build 2110 apparently has an issue and they are going to be releasing build 1660. Not sure if this is a roll back type of situation but I would open a TAC case.
Hi,
Let me explain.
Build 2110 is completely safe to use for protecting your gateway against recent CRL issues, though it is a targeted fix rather than a comprehensive update. We plan to release a fully unified public firmware update in roughly two weeks that will replace it.
To give you the full picture, Build 2110 is based on R82.00.10 GA and focuses specifically on resolving the CRL problem, It does not include the broader resolutions currently found in our ongoing Jumbo Hotfix (JHF), which we provide exclusively to CFG customers to address their unique environments. We are currently finalizing our QA and performance testing on this broader JHF, and it will soon be released to the public to replace 2110.
If your system is running smoothly and you have never been instructed by TAC or CFG to install custom firmware, you can confidently use Build 2110 right now. However, if you rely on custom firmware provided by our teams for past issues, Build 2110 lacks those specific fixes. In that scenario, you should request the CFG Jumbo instead to ensure all your previous issues remain resolved while we finish testing the upcoming unified release.
Ok thanks for the message. I was told by my TAC engineer that 2110 has an issue and to not upgrade to it. They then gave me build 1660.
My personal experience with build 2110 on a 1535 appliance, is that the stability issues were not fixed on this build. After around 24 hours of initial stability, we experienced multiple crashes within a few hours which took the cluster entirely offline each time.
Hi @J_admin12
Please contact me directly and share your SR number.
I would like to review the case and provide a solution for the freeze and crash issues.
Ohad
Ohad,
We are running 2000 appliances running the latest build, now I don't know if this is issue or not, but we've had to reboot the firewalls twices now for FQDN objects to work.
First time round dns lookups just stopped (this was in all fairness on the last build), we had to reboot to get this working again.
Now we have had a strange issue where resolution seemed to be out of sync between the client and the firewall even though they are both using the same DNS, again rebooted the firewall and everything worked. I'm suspecting this cleared the cache.
Is there a way to clear the DNS cache without rebooting the firewalls? So I can confirm this behavior is actually related to DNS caching?
Hi,
You can check this DNS article for R82.00.X:
Quantum Spark R82.00.X – Configuring DNS Settings
In R82, DNS servers can be configured directly from CLI or WebUI, and you can define up to three DNS servers (primary, secondary, tertiary) for the gateway.
However, I need to understand your issue in more detail. Please share SR with all relevant information:
Firmware build you are using
Network topology
Management type (Locally managed / Cloud / Centrally managed)
Also, for troubleshooting purposes, please test with global DNS servers, such as:
8.8.8.8
1.1.1.1
and let me know if the issue persists.
Ohad
Hi Ohad,
We have three DNS entries, all public. This was working fine with client testing. The latest symptom we have seen is activate GW can resolve queries, standby device could not, and the end client was unable to access, which I believe is due to a mismatch in IPs resolved.
Its not something that happens all the time so its hard to pinpoint that this stage. I don't have an SR open at this point as we are still testing. If it happens again I will raise, run a Dr Spark, and cpinfo from both devices, then raise a S/R, and try to keep the GWs in the same state.
We are running R82.00.10 build 2110.
Only change we did was to reboot both GWs and it all started to work.
Hi,
When the setup is working fine and DNS resolved correctly, do you also see problems with Standby member access to the Internet?
Thanks.
When its working fine, I can do nslookup from both GWs in the cluster, when its not I cannot do an nslookup from the standby device.
Additionally I've ensured the GWs can ping the upstream internet router.
Thanks for your reply.
The next time you see this issue, in addition to opening SR and collecting the relevant data, I will appreciate it if you can clear the connections table on both cluster members by running:
fw tab -t connections -x -y
and see if it makes any difference.
Will do, to be fair it it happens again I will need to raise a TAC case.
We just got the problem again, after clearing the connections table it worked.
Hi @sx8n20394
Build 2110 is the official GA version, which includes the CRL fix:
https://support.checkpoint.com/results/sk/sk184357
Build 1660 is a hotfix build.
The appropriate build depends on the specific gateway issue and whether R&D provided a targeted fix.
There are no known issues with build 2110.
Ohad
Ok, we were told by support that there was an issue with 2110 which is why I posted my original reply.
Hi everyone.
Please note that we recently released Build 998002133, which integrates several fixes previously available in separate builds.
This consolidated release resolves the rare freeze issue under heavy load, includes multiple CFG fixes, and incorporates the CRL fix (the same one detailed in the CRL SK).
Is this also applicable to 2000 appliances?
I should have checked on the support site first!
I've upgraded a couple of devices we have and updated the various TAC cases.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
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 WAFTue 12 May 2026 @ 10:00 AM (CEST)
The Cloud Architects Series: Check Point Cloud Firewall delivered as a serviceThu 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