Steps to configure Site to Site VPN between SonicWalls

Today, I'd like to share the steps to configure IPSec Site to Site VPN Tunnel with IKEv2 Mode between SonicWalls
Please proceed below steps in Local and Remote site SonicWall Firewall to get your VPN Tunnel

- Create Firewall Address Object and Assign them to the correct Zone Assignment
- By default, VPN setting in SonicWall is disable. So, do not forget to Enable it.
- Add VPN Policy with below details in correct.
(
၁။ Policy Type က Site to Site
1> Policy Type must be Site to Site
2> Authentication Method have to be IKE using Preshared Secret
3> Assign VPN name for ease of understanding.
4> IPSec Primary Gateway Name or Address must be the WAN IP Address of Remote Site Firewall
5> Key in complex and secure Shared Secret
6> Put correct Local and Peer (Remote) WAN IP Addresses as IKE ID for IKEv2 Mode in your two Firewalls
7> Local and Destination (Remote) Network Subnet should be correct in your Network Section of VPN Policy
8> Ensure Phase 1 and Phase 2 Proposal Settings are correct
9> Do not forget to Enable Keep Alive setting
10> By default, VPN Access rule are automatically added in your SonicWall once you've created VPN Policy. But create Manually if you didn't see it in your Access Rules.
)

Well...Your IPSec Site to Site VPN Tunnels should up and running in Monitoring Session as Active if you are configure correctly above configuration on both SonicWall Firewalls.

I've attached configuration screen-shots of Local Site Firewall for your reference.

I believe this post will useful for who start to touch SonicWall Firewall.

Have a good time.
(Be knowledgeable, pass it on then)

Comments

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a...

Why do we need network virtualization?

We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...

Link Aggregating with Synology NAS and Cisco Switch

I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f...

ICT for Myanmar in English

Search This Blog