R82.10 approximate release date?

[the_rock]

Hey guys,

Any idea when R82.10 will be out as generic availability?

Best,

Andy

[the_rock · Accepted solution]

Asked our SE and was told hopefully end of 2025, but if not, first quarter of 2026.

Regards,

Andy

[ccsjnw]

Isn't R82.10 already considered GA for the new ARM based appliances?

[the_rock]

Not sure...

Andy

[Chris_Atkinson]

3900 series already have a special release of R82.10 see: https://support.checkpoint.com/results/sk/sk183199

Don't believe I've seen the public EA for it yet otherwise which would include the feature additions and support of other appliances.

[the_rock]

I just worked with customer that replaced 4 of their firewalls (3 were 3920) and they all came with R81.20.

Andy

[Chris_Atkinson]

They're not supported with the earlier kernel so worth double checking that.

[the_rock]

I will ask them, but Im 99% sure that was the version on all 3 of those.

Andy

[Timothy_Hall]

I don't think that the Gaia kernel 4.18 used by R81.20 supports ARM, but I could be wrong.

[the_rock]

Im fairly positive you are correct.

Andy

[_Val_]

You are right. The kernel version in R82.10 is 5.14

[Steffen_Appel]

RHEL (the base of GAIA) supports ARM since release 7.4 (kernel 3.10.0-693). 

R81.20 is RHEL 7.9 based.

R82 is RHEL 8.6 based.

[JohnHaynes]

3920s ship with R82.10 - Build 407.  This is to support the 5.14 kernel.

[the_rock]

I never really ran uname -a command on one of theirs 3920, since I dont have the access to them myself, but below is output from one of my VMs...

Andy

[Expert@CP-GW:0]# uname -a
Linux CP-GW 4.18.0-372.9.1cpx86_64 #1 SMP Thu Aug 28 16:01:06 IDT 2025 x86_64 x86_64 x86_64 GNU/Linux
[Expert@CP-GW:0]# fw ver
This is Check Point's software version R82 - Build 008
[Expert@CP-GW:0]#

[Expert@CP-GW:0]# cpinfo -yfw1

This is Check Point CPinfo Build 914000250 for GAIA
[FW1]
HOTFIX_R80_40_MAAS_TUNNEL_AUTOUPDATE
HOTFIX_R82_JUMBO_HF_MAIN Take: 41
HOTFIX_UCA_SSH_TUNNELING_SERVICE_AUTOUPDATE
HOTFIX_UCA_SSH_TUNNELING_APP_AUTOUPDATE
HOTFIX_UCA_INFRA_MONITOR_SERVICE_AUTOUPDATE
HOTFIX_UCA_INFRA_LOG_SERVICE_AUTOUPDATE
HOTFIX_UCA_INFRA_AUTOUPDATE
HOTFIX_PUBLIC_CLOUD_CA_BUNDLE_AUTOUPDATE
HOTFIX_INEXT_NANO_EGG_AUTOUPDATE
HOTFIX_GOT_TPCONF_AUTOUPDATE

[Timothy_Hall]

Yeah, way too easy to mix up R81.20 and R82.10, keep doing it in my class lectures and I have to correct myself.  🙂

[Paul_Hagyard]

What is the situation with support? All of the 3900 appliances (based on https://www.checkpoint.com/support-services/support-life-cycle-policy/) only support R82.10, it seems a very odd move to release new hardware that runs an operating system still classified as early availability. Will they get the same priority as R82 and R81.20 for JHF updates? As of today there is only a single JHF (22) for the 3900 appliances (https://support.checkpoint.com/results/sk/sk183557).

[Chris_Atkinson]

It could of gone the way of the 3.10 kernel version of R80.30 but actually I believe we will have GA1 and GA2 as a result on this occasion.

[Paul_Hagyard]

It appears that R82.10 is not getting the same priority for JHF updates as R81.20 and R82. On a recent deployment we ran into the issue where the initial policy install fails because the updatable objects are not available (workaround is to copy the files from another working gateway). This has been fixed in R81.20 and R82 JHF's but not in R82.10 JHF 22.

[the_rock]

Lets see once its gA.

[Chris_Atkinson]

I've asked about the timeline for the next JHF and will update pending feedback.

/Edit: This is now dependent on confirmation of the GA2 release date.

[the_rock]

Thanks Chris, we appreciate it.

[the_rock]

From discussion with our SE, what Chris said sounds right.

Andy

[the_rock]

Hey Chris,

Just wanted to apologize (as I always do when Im wrong) and I was 100% wrong. As @Timothy_Hall , I totally confused R82.10 with R81.20. I just saw an email from customer and it clearly shows on the screenshot that all 3 3920 fws are on R82.10

Regards,

Andy

[Chris_Atkinson]

No apology needed 🙂

[the_rock]

Its just the right thing to do! As my mom used to say to my brother and I when we were kids "Dont pretend magic fairy ate the icecream, just admit you did and say you are sorry, thats it" : - )

Andy

[Paul_Hagyard]

This morning I received an email about R82.10 take 464, advising that we need to install this over the one which shipped with the 3900 appliances (take 271). This is the first time I can ever recall being asked to install another release/take of the same major version over itself.

Could this not be better achieved with a revised JHF replacing the current (old) take 22 with a newer one incorporating the changes in the release/take 464?

The R82.10 page (sk183506) now has a dedicated section on upgrading the 3900 appliances, which says to start with JHF 22 installed, upgrade to release/take 464, but then has no mention of installing JHF 22 again. The R82.10 JHF for 3900 page (sk183557) still refers to this JHF being for R82.10 take 271, so presumably release/take 464 incorporates any fixes in JHF 22?

This is getting a bit unclear...

[the_rock]

I was told same by a customer as well, but to me, thats also bit unclear, since its not referring to jumbo take, so I asked them to open TAC case to confirm.

[RickLin]

I believe the underlying reason is that the 3900 series is Check Point's first attempt at using ARM architecture hardware. Back when the 3900 was released in Q2 2025 (during the R82 era), it couldn't be used as a Standalone unit because the Management (SMS) code is x86/x64 based. This resulted in R82-era SMS managing the specialized R82.10 ARM appliances.

Now that the ARM firmware has been optimized and the maintrain R82.10 is officially GA, Check Point is pushing for unification. The Take 22 mentioned in the SK was just a transitional phase.

One important thing missing from the email is the SMS requirement. Since you are upgrading the gateway to the latest R82.10, you definitely need to schedule an upgrade for your SMS to R82.10 as well.

[Paul_Hagyard]

As R82.10 is not yet the recommended release, it isn't particularly desirable to update the SmartCenter server to R82.10 in all environments. In one environment we have a 3950 off Smart-1 Cloud, which is still R82 (at least for now, for this specific account.)

sk183199 still mentions managing with R82 JHF 19 or higher, but perhaps that article just hasn't been updated yet.

If this is a requirement for managing R82.10 release/take 464 then it would be important to get that officially communicated ASAP, or upgrades would fail with the SmartCenter being on R82.

[Chris_Atkinson]

Upgrading the Management would be a requirement to specifically leverage new R82.10 features, otherwise it shouldn't be mandatory.