- Products
- Learn
- Local User Groups
- Partners
- More
AI Security Masters
E1: How AI is Reshaping Our World
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
Hi
I recently made a VPN connection between Check Point and AWS.
The method was Static-Route, and fortunately the tunnel comes up normally and communication is normal.
All that remains are detailed settings for tunnel stability, but I have a question about the TCP MSS Clamp setting
The customer previously operated by connecting Cisco equipment and IPsec VPN on a domain basis, and recently connected AWS and VPN with Routed-Base.
In this situation, it is thought that setting the TCP MSS clamp will affect the existing VPN communication as well.
So, I am curious about how the above settings affect general traffic other than existing IPSec communication and VPN communication.
If anyone has tried the TCP MSS Clamp setting, please let me know if it has any effect on the service or what I am concerned about.
Refer to sk101219 for TCP MSS Clamp setting
Yes, this impacts all VPNs.
The main thing it accomplishes is ensuring IPsec packets aren’t getting fragmented because an application communicating through it is trying to use packets larger than can be accommodated.
Unless an particular system or application is especially poorly behaved, enabling this session should not cause a negative impact.
If you review sk101219 closely, you'll see there are separate clamping settings for VPN and non-VPN traffic.
Which means that these settings won't affect non-VPN traffic unless you configure it to do so.
The main reason for this feature is to solve the problem described here: https://support.checkpoint.com/results/sk/sk98074
I haven't heard of any issues caused by using this feature, except perhaps through misconfiguration (i.e. forcing a specific MSS value that is problematic).
As you said, I'm trying to change only VPN-related settings.
However, I am concerned that there may be an impact on the existing IPSec VPN
Yes, this impacts all VPNs.
The main thing it accomplishes is ensuring IPsec packets aren’t getting fragmented because an application communicating through it is trying to use packets larger than can be accommodated.
Unless an particular system or application is especially poorly behaved, enabling this session should not cause a negative impact.
Thank you for your reply, it helped me a lot
In general you should be able to determine this for yourself with ping tests and the df-bit set in regards to validating MTU / MSS settings etc.
From tests inside and outside the VPN you should be able to correlate accordingly.
Tools like psping should allow TCP based probes rather than just ICMP also.
thank you for your reply
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 20 | |
| 17 | |
| 13 | |
| 8 | |
| 7 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 3 |
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 cloudsThu 08 Jan 2026 @ 05:00 PM (CET)
AI Security Masters Session 1: How AI is Reshaping Our WorldAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY