- Products
- Learn
- Local User Groups
- Partners
- More
CheckMates Fifth Birthday
Celebrate with Us!
days
hours
minutes
seconds
Join the CHECKMATES Everywhere Competition
Submit your picture to win!
Check Point Proactive support
Free trial available for 90 Days!
As YOU DESERVE THE BEST SECURITY
Upgrade to our latest GA Jumbo
The 2022 MITRE Engenuity ATT&CK®
Evaluations Results Are In!
Now Available: SmartAwareness Security Training
Training Built to Educate and Engage
MITRE ATT&CK
Inside Check Point products!
CheckFlix!
All Videos In One Space
Customer builds Site-To-Site VPN between Check Point and 3rd party device. VPN domain of 3rd party device overlaps with a network from internal scope so we want to translate it. I saw an option "disable NAT inside VPN community" but I think we want an opposite option: make NAT rule work only if traffic is within VPN community. Is there such possibility?
As long as "disable NAT in VPN Community" is unchecked, traffic entering or leaving a VPN tunnel is subject to the NAT policy just like any other traffic. To set up NAT for VPN traffic only you'll need to make sure the box is unchecked then set up a manual NAT rule at the top of the NAT policy. Be sure to set the Original Source and Original Destination Fields as tight and specific as possible to avoid catching unintended traffic in that NAT rule.
As long as "disable NAT in VPN Community" is unchecked, traffic entering or leaving a VPN tunnel is subject to the NAT policy just like any other traffic. To set up NAT for VPN traffic only you'll need to make sure the box is unchecked then set up a manual NAT rule at the top of the NAT policy. Be sure to set the Original Source and Original Destination Fields as tight and specific as possible to avoid catching unintended traffic in that NAT rule.
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY