Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Danny
Champion Champion
Champion

HowTo: Configure a VPN between FortiGate & Check Point

Step 1:  Fill out a VPN setup sheet with your FortiGate VPN partner and agree on the VPN settings.


See here: VPN setup sheet template


Step 2:
Start configuring your Check Point.


In Check Point SmartConsole you have to create an Interoperable Device (your FortiGate).

New > Network Object > More > Interoperable Device

There you have to fill in information like the WAN-IP of your FortiGate.

1.png

And the local subnet you want to tunnel from the FortiGate to the Check Point under “Topology”.

1-2.png

I would generally advise you to create Network Objects for both, your Check Point local subnet and your FortiGate local subnet to be reachable by VPN.

Best practice:
Use Object Names that are self-explanatory.

New > Network

1-3.png
1-4.png

Best practice: Create a host Object with the IP of the WAN interface of your Check Point, in case the main IP of your Check Point Object is the internal IP address. This object can be used in the rulebase when configuring access rules.

New > Host
1-5.png


Step 3:
Create a VPN community object within Check Point's SmartConsole and then head over to the FortiGate and configure the VPN there as well.


Securely configure the VPN Community, install the Security Policy to your Check Point VPN Gateway and you should then see the VPN tunnel Status: Down. After completing the VPN configuration on your FortiGate, the VPN Tunnel should go up.

Before you create a VPN-Community, make sure that your IPsec VPN blade is enabled on your Check Point:

General Properties > Network Security IPsec > VPN 

1-6.png

Next step is to create a new VPN Community. (This can be either Star or Mesh VPN)

New > More > VPN Community > Star Community

Best practice: Use a name that is self-explanatory.

Define your Check Point VPN gateway as the Center Gateway and the FortiGate as the Satellite Gateway:
1-7.png

Select the correct encryption parameters that you've exchanged with your VPN partner.
1-8.png

Set the shared secret.
1-9.png

Set the correct IKE/IPsec renegotiation times and toggle "Disable NAT inside the VPN" according to your requirements.
1-10.png

After you saved the configuration you’ll be able to check the state of your VPN tunnel with this SmartConsole Extension.
This should show the VPN tunnel as "Down" because you haven’t configured your FortiGate yet.

1-11.png

Step 4: Configure a custom VPN tunnel on your FortiGate.


Custom selector(s) are required because Check Point will not accept 0.0.0.0/0 as encryption domain from the FortiGate in its usual domain-based VPN set up.


On your FortiGate WebUI, enter a name for your VPN:

VPN > IPsec Wizard

1-12.png

Enter the Remote Gateways IP Address and the outgoing interface.

1-13.png

Enter the Pre-shared Key you agreed upon as well as IKE-version.

1-14.png

For Phase 1 select the Encryption and Authentication you agreed upon as well as the Diffie-Hellman Group and the Key Lifetime.

1-15.png

For Phase 2 enter the Local and Remote Address space.

1-16.png

Under Advanced options you can select the Encryption and Authentication method you agreed upon as well as the Diffie-Hellman Group and the Key Lifetime.

1-17.png

In the next step you add new Address objects under
Policy & Objects > Addresses > Create New > Address

1-18.png

For your local subnet:

1-19.png

and for the remote subnet:

1-20.png

for the remote wan:

1-21.png

for your local wan:

1-22.png

You can also add Address Groups if you want to add them to the Firewall Policies instead of the direct Subnets.

Add a static route for your remote subnet pointing to the VPN-Tunnel Interface.
Network > Static Routes > Create New

1-23.png

Add another static Route this time pointing to the Blackhole interface.

1-24.png

Last step is to add Firewall Policies to allow the VPN traffic to pass trough.
Add a New Policies Policy & Objects > Firewall Policy > Create New

1-25.png

First for the traffic going to the VPN-Tunnel from the Port of your Subnet. In this case, NAT is not required.

1-26.png

Then for the traffic coming from the VPN-Tunnel going to the Port of your destination Subnet. In this case NAT not required.

1-27.png

After that, monitor your VPN-tunnel. To check your VPN tunnel health you have to add a new Dashboard-Widget called IPsec
Dashboard > Status > Add Widget

1-28.png

Check the VPN Phase 1 and Phase 2 status:

1-29.png

You can then test the connection by sending a ping through it.
Phase 2 should be brought up automatically, provided Phase 1 has been brought up properly.

1-30.png

Let's verify on your FortiGate and Check Point if the tunnel has been established successfully.

1-31.png

In your Check Point SmartConsole, you can easily check your VPN tunnel state with this SmartConsole Extension.

1-32.png

Enjoy!

1 Reply
the_rock
Legend
Legend

Great work @Danny 

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events