How To's: Configure Site-to-Site VPN between Check Point firewall and Cisco ASA firewall
In this article we'll deploy a VPN Site-to-Site between Cisco ASA Firewall and Checkpoint Firewall.
The configuration will be based on the following topology:
This topology is made of 4 sites. The HQ has a cluster of Check Point firewalls, the Branch-02 has another cluster of Check Point firewalls, Branch-03 and Branch-04 both have Cisco ASA firewall.
We'll build the VPN between Branch-04 and HQ. If you read my previous post, you should be familiar with configuration on Cisco ASA by now. This scenario, assumes that you already have a Check Point environment running. If you don't have, don't worry. In the next posts I'll show how to deploy a topology running Check Point firewalls (gateways) in a clustered fashion (Cluster_XL and Load Sharing).
Let the fun begin...
ISP
hostname ISP
interface e0/0
no shut
ip add 203.0.113.254 255.255.255.0
!
interface e0/3
no shut
ip add 172.16.2.254 255.255.255.0
wr
BR4-FW-01
hostname BR4-FW-01
interface GigabitEthernet0/0
nameif outside
security-level 0
ip address 172.16.2.1 255.255.255.0
no shut
!
interface GigabitEthernet0/1
no shut
nameif inside
security-level 100
ip address 10.10.20.1 255.255.255.0
!
route outside 0.0.0.0 0.0.0.0 172.16.2.254
At this point there is nothing to test yet. Now let's configure Check Point firewall.
Check Point VPN feature have to be licensed and enabled!
First we have to add BR4-FW-01 and it's internal network on SMS (Security Management Server) as objects. In the Object Categories pane, we'll add a new Interoperable Device
We'll name it BR4-FW-01 with IP address 172.16.2.1
Next let's add branch internal network 10.10.20.0/24
Now let's configure the community. We'll create a new Meshed Community.
We'll name it CP-ASA-VPN-Site-to-Site
We'll add both firewalls to the community by clicking on plus sign, and set the vpn domain on each firewall by clicking on the pencil sign and choosing the internal network of each firewall.
Now let's proceed to the Encryption tab, and match the same parameters we configured on Cisco ASA firewall for IKEv1.
Moving to the Shared Secret tab, we'll type the vpn key by enabling Shared Secret box and clicking in the pencil.
Finally in the Advanced tab, we'll change IKE parameters and disable NAT inside the VPN community.
Press OK.
Now we have to create a policy/rule allowing our interest traffic and disable NAT from the two networks:
To prevent traffic from both internal networks being translated we have to create a Network Group and add both networks to it. Then we create a static NAT rule on the top of NAT rule.
At last Publish and Install policy.
In ASA you already now how to verify the tunnel status. In Check Point you can verify the tunnels status and the logs from end hosts using different tools.
In Logs & Monitor tab, we'll filter both hosts IP address: 192.168.234.133 OR 10.10.20.2.
Once we send interest traffic from one of the hosts, we'll see the logs in this tab.
We can monitor the tunnel status by using Smartview Monitor or through cli using the command vpn tu.
BR4-INT-2 successfully connected to HQ_MGMT_133.
Hope you enjoyed this post, leave your comments below and I'll see you on the next post.
References:
Senior System Engineer at VERTEXMON
4yGood job.