- Products
- Learn
- Local User Groups
- Partners
- More
The Great Exposure Reset
24 February 2026 @ 5pm CET / 11am EST
CheckMates Fest 2026
Watch Now!AI Security Masters
Hacking with AI: The Dark Side of Innovation
CheckMates Go:
CheckMates Fest
The VPN Remote Access Client does not support IPv6.
This means that every PC with an installed VPN Remote Access Client can reach the Internet via IPv6. No firewall rules are active for IPv6. All IPv6 traffic is permitted.
In my case, turning off the IPv6 stack under Windows is not a solution.
Is there a way to prevent IPv6 communication with Check Point settings?
This requires firewall functionality in the VPN client, thus you must use Endpoint Security VPN.
And, it should be possible to configure IPv6 rules: https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...
Hi @PhoneBoy,
Thanks!
I no longer understand anything here:-)
The following sk67820: Check Point Remote Access Solutions describes that there is no IPv6 support.
PS:
I find the description of the endpoint VPN clients suboptimal.
The following points should be revised here:
- Clearly structured SK
- Documentations
- List with functions matching the version
- Battle cards to compare with other vendors
...
I believe the quoted table is for VPN functionality. You cannot do IPsec to IPv6 addresses with the clients above. @PhoneBoy is talking about Desktop security rules. No contradiction.
Hello Val,
is this feature on the roadmap? In germany many mobile providers are using dual stack with CGNAT for IPv4 which is not an ideal solution.
Regards,
Jan
Please rase an RFE for that with your local Check Point office.
I will do so.
Any Update regarding the issue? Are Desktop Policys with IPv6 possible?
Expect it to be aligned with the R82 release or there about.
For further details please discuss it with your local SE.
Hi @Chris_Atkinson
The local SEs do not give us any further information here either.
Will IPv6 be supported with R82 and E8x client?
Most likely a new gateway and client version is needed.
Not at present.
As stated by others, this is expected to be addressed as part of the next major release train (R82.x).
For formal timing/commitment, please reach out to your local Check Point office.
@HeikoAnkenbrand and all,
Please point your attention to this post:
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 22 | |
| 21 | |
| 13 | |
| 9 | |
| 9 | |
| 9 | |
| 9 | |
| 8 | |
| 7 | |
| 7 |
Thu 12 Feb 2026 @ 05:00 PM (CET)
AI Security Masters Session 3: AI-Generated Malware - From Experimentation to Operational RealityFri 13 Feb 2026 @ 10:00 AM (CET)
CheckMates Live Netherlands - Sessie 43: Terugblik op de Check Point Sales Kick Off 2026Thu 19 Feb 2026 @ 03:00 PM (EST)
Americas Deep Dive: Check Point Management API Best PracticesThu 12 Feb 2026 @ 05:00 PM (CET)
AI Security Masters Session 3: AI-Generated Malware - From Experimentation to Operational RealityFri 13 Feb 2026 @ 10:00 AM (CET)
CheckMates Live Netherlands - Sessie 43: Terugblik op de Check Point Sales Kick Off 2026Thu 19 Feb 2026 @ 03:00 PM (EST)
Americas Deep Dive: Check Point Management API Best PracticesAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY