- Products
- Learn
- Local User Groups
- Partners
- More
Step Into the Future of
AI-Powered Cyber Security
What's New in R82.10?
Register HereWhen the Agents Attack
A Live Look at Agentic Exposure Validation
AI Security Masters E8:
Claude Mythos: New Era in Cyber Security
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 |
|---|---|
| 10 | |
| 9 | |
| 8 | |
| 8 | |
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 3 | |
| 3 |
Tue 16 Jun 2026 @ 05:00 PM (CEST)
Under the Hood: Check Point SASE | Internet Access Optimization & Performance TuningThu 18 Jun 2026 @ 10:00 AM (CEST)
The Cloud Architects Series: Check Point WAF - The Next Generation of AI powered protectionTue 23 Jun 2026 @ 05:00 PM (CEST)
Under the Hood: Check Point Cloud Firewall | Securing all of your clouds: Art of the possibleTue 16 Jun 2026 @ 05:00 PM (CEST)
Under the Hood: Check Point SASE | Internet Access Optimization & Performance TuningThu 18 Jun 2026 @ 10:00 AM (CEST)
The Cloud Architects Series: Check Point WAF - The Next Generation of AI powered protectionTue 23 Jun 2026 @ 05:00 PM (CEST)
Under the Hood: Check Point Cloud Firewall | Securing all of your clouds: Art of the possibleThu 25 Jun 2026 @ 10:00 AM (PDT)
AI Security Masters E10: READY OR NOT: Securing the AI Enterprise 2/5 - AI Red TeamingAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY