Getting Started with Site-to-Site VPN

In This Section: Setting up Site-to-Site VPN between Gateways Confirming that a VPN Tunnel Opens Successfully

Setting up Site-to-Site VPN between Gateways

Scenario: Two Check Point gateways are managed by the same Security Management Server. How do you create a site-to-site VPN between the two gateways so that they can communicate securely?

Overview of the Workflow:

1. Create the gateway objects in SmartConsole and make sure that IPsec VPN is enabled on each one.
2. Generate internal CA certificates for each gateway (done automatically).
3. Create the VPN Community.
4. Define the VPN Domain.
5. Make sure that the VPN will work with your configured routing, or change the routing or link selection settings as necessary.
6. Create rules for the traffic.
7. Install the Access Control Policy.

Enabling IPsec VPN on a Gateway

Site to Site VPN requires two or more gateways with the IPsec VPN Software Blade enabled. Other Software Blades can be enabled on the same gateway.

Make sure that Trusted Communication is established between all gateways and the Security Management Server.

To enable the IPsec VPN Software Blade on a gateway:

1. In SmartConsole, open a gateway object.
2. On the General Properties page, in the Network Security tab, select IPsec VPN.
3. Click OK.

   An internal CA certificate for the gateway is created automatically.

Creating a VPN Community

You can create a Meshed or Star VPN Community. The procedure below shows an example of a Star Community.

To create a new VPN community:

1. In SmartConsole > Security Policies tab, in the Access Tools area, click VPN Communities.
2. Click the New icon and select Star Community.

   A New Star Community window opens.

3. Enter a name for the VPN Community.
4. In the Center Gateways area, click the plus icon to add one or more gateways to be in the center of the community.
5. In the Satellite Gateways area, click the plus icon to add one or more gateways to be around the center gateway.
6. Click OK.

   The Community uses the default encryption and VPN Routing settings.

7. Optional: Edit more settings for the VPN Community in the community object.

More VPN Community Settings

In addition to the gateway members, you can edit these settings for the VPN Community in the community object:

• Encrypted Traffic - Select Accept all encrypted traffic to encrypt and decrypt all traffic between the Security Gateways. If this is not selected, create rules in the Security Policy Rule Base to allow encrypted traffic between community members
• Encryption - Select encryption settings that include the Encryption Method and Encryption Suite. See VPN Community Object - Encryption Settings.
• Tunnel Management - Select settings VPN tunnels that include Permanent Tunnels and Tunnel Sharing. See Configuring Tunnel Features.
• VPN Routing -For Star Communities, select how VPN traffic is routed between the center and satellite gateways. By default this is always set to To center only. See Configuring Domain Based VPN.
• MEP (Multiple Entry Points) - For Star Communities, select how the entry gateway for VPN traffic is chosen. This only applies when you have multiple center gateways in the community. See Configuring MEP.
• Excluded Services - Add services that are not to be encrypted, for example Firewall control connections. VPN tunnels are not created for the Services included here.
• Shared Secret - Configure shared secret authentication to use for communication with external gateways that are part of a VPN community. See Configuring a VPN with External Security Gateways Using Pre-Shared Secret.
• Wire Mode - Select to define internal interfaces and communities as trusted and bypass the firewall for some communication. See Configuring Wire Mode.
• Advanced - Configure advanced settings related to IKE, IPsec, and NAT. You can also Reset All VPN Properties to revert all VPN Community settings to their default values. See Configuring Advanced IKE Properties.

Defining the VPN Domain for a Gateway

The VPN Domain defines the networks and IP addresses that are included in the VPN community. It is also called the Encryption Domain. When you create a Check Point gateway object, the VPN Domain is automatically defined as all IP Addresses behind the gateway, based on the topology information.

You can manually define the VPN domain to include one or more networks. You must have a Network object or Network Group object that represents the domain.

To manually define the VPN Domain:

1. In SmartConsole, open a gateway object.
2. Open the Network Management > VPN Domain page.
3. Select Manually defined and:
   • Browse to the object list and select an object that represents the domain.
   • Browse to the object list and click New > Group or Network to define a new group of machines or network.
4. Click OK.

Confirming VPN Routing

By default, IPsec VPN uses the main IPv4 Address, defined in the General Properties page of the Gateway, for the VPN tunnel connection.

If you want to use this IP address for the VPN communication, and it is an external interface, you do not need additional routing.

If the main IP address is an internal interface, or if you want VPN communication on a different interface, make sure that:

• The Link Selection settings for the gateway are configured. Choose which gateway links are used by VPN to route traffic correctly.
• VPN Routing is configured to allow the connections. For information how to configure routing in Gaia OS, see the R80.30 Gaia Administration Guide - Chapter Network Management.

Configuring Site to Site VPN Rules in the Access Policy

You must configure rules to allow traffic to and from VPN Communities. Configure rules in SmartConsole > Security Policies > Access Control. All layers of the Access Control Policy can contain VPN rules.

To make a rule apply to a VPN Community, the VPN column of the Rule Base must contain one of these:

• Any - The rules applies to all VPN Communities and to non-VPN related traffic. If you configure a new VPN Community after the rule was created, the rule also applies to the new VPN Community.
• One or more specified VPN communities - For example, MyIntranet. Right-click in the VPN column of a rule and select Specific VPN Communities. The rule applies to the communities shown in the VPN column.

Examples:

• This rule allows encrypted traffic between domains of member gateways of "community_X."

  Name	Source	Destination	VPN	Services & Applications
  Allow traffic within community	* Any	*Any	MyCommunity	* Any

• This rule allows traffic from all VPN Communities to the internal network on all services.

  Name	Source	Destination	VPN	Services & Applications
  Allow all VPN	* Any	Internal_Network	* Any	* Any

• This rule allows traffic between two VPN domains with all services.

  Name	Source	Destination	VPN	Services & Applications
  Site to Site VPN	Local_VPN_Domain Peer_VPN_Domain	Local_VPN_Domain Peer_VPN_Domain	Site2Site	* Any

Confirming that a VPN Tunnel Opens Successfully

To make sure that a VPN tunnel has successfully opened:

1. Edit the VPN rule and select Log as the Track option.
2. Click Logs & Monitor > New Tab.
3. From the bottom of the window, click Tunnel and User Monitoring.

   Check Point SmartView Monitor opens

4. Click the gateway to see IPsec VPN traffic and tunnels opened. A successful connection shows encrypt, decrypt and key install logs.

   Alternatively:

   1. In SmartConsole click Logs & Monitor.
   2. On the Logs tab, search for VPN to see the applicable logs.
5. Open SmartView Monitor and see that VPN tunnels are up.