Oracle OCI Site-to-Site VPN to Meraki Switch – Part 1 – Eclipsys

Site-to-Site VPN offers a simple and secure way to connect your on-premises network to Oracle Cloud Infrastructure over your existing internet connection. The data is encrypted using industry-standard encryption algorithms called IPSec and is then tunneled through the public internet for enhanced security and privacy.

In this workshop, we will see the steps to set up a Site-to-Site VPN to Meraki Cisco switch with a simple layout that you might use for a proof of concept (PoC). The workshop will be covered over two blog posts. 

Prerequisites:

• An Oracle Cloud free trial or paid account
• OCI VCN with a private subnet and a route table
• OCI Linux compute instance located in a VCN’s private subnet

Assumptions:

• OCI VCN’s CIDR: 172.40.0.0/16
• OCI private subnet CIDR: 172.40.40.0/24
• OCI VM private IP: 172.40.40.60
• The public IP address of your CPE device: is 142.35.140.32
• On-premises private subnet CIDR: 10.8.8.0/24
• Routing Type: Policy-based
• Cisco Device: Meraki

Step #1: Create Dynamic Routing Gateway (DRG)

1. Open the navigation menu and click “Networking”. Under “Customer connectivity”, click “Dynamic routing gateway”

2. In the Dynamic routing gateway screen, click “Create Dynamic Routing Gateways”.

3. In the “Create Dynamic Routing Gateways” dialog window, enter the DRG name and select the compartment where you want to put your DRG, then click “Create Dynamic Routing Gateways”.

Step #2: Attach the DRG to the VCN

1. Click the name of the DRG you created
2. Under the “Resources” section, click “Virtual Cloud Networks Attachment”
3. Click “Create Virtual Cloud Network Attachment”.

4. In the “Create Virtual Cloud Network Attachment” dialog window, enter “attachment name” and select the VCN. Ignore the section for advanced options, which is only for an advanced routing scenario called transit routing, which is not relevant here. Click “Create Virtual Cloud Network Attachment”.

Step #3: Update the Existing Private Subnet’s Route Table

If you already have an existing VCN with a subnet, you don’t need to create a route table or subnet. Instead, you can update the existing subnet’s route table to include the route rule for the DRG.

 
We need to add a below route rule.

1. Open the navigation menu, click “Networking”, and then click “Virtual cloud networks”
2. Click your VCN
3. Under the “Resources” section, click “Route Tables”. Click the private subnet’s route table name

4. In the Route Table screen, click “Add Route Rules”

5. In the “Add Route Rules” dialog window, enter the below information then click “Add Route Rules”

• Target Type: Dynamic Routing Gateway
• Destination Type: CIDR Block
• Destination CIDR Block: On-premises private subnet CIDR. In our example, 10.8.8.0/24

Step #4: Create a Security List

By default, incoming traffic to the instances in your VCN is set to DENY on all ports and all protocols. In this task, you set up two ingress rules and one egress rule to allow basic required network traffic.

We need to add the below Ingress and Egress rules.

1. Open the navigation menu, click “Networking”, and then click “Virtual cloud networks”

2. Click your VCN

3. Under the “Resources” section, click “Security Lists”. Click “Create Security List”

4. In the “Create Security List” dialog window, enter the security list name, select the same compartment as VCN, and enter the Ingress & Egress rules listed in the above table. Click “Create Security List”

Step 5: Add Security List to Existing Private Subnet

1. Open the navigation menu, click “Networking”, and then click “Virtual cloud networks”
2. Click your VCN
3. Under the “Resources” section, click “Subnets”. Click private subnet name

4. In private subnet screen, click “Add Security List”.

5. In the “Add Security List” dialog window, select the security list’s compartment and select the security list created in step #4. Click “Add Security List”