Skip to main content

How to Configure a Route-Based VPN by using Tunnel Interface between two SonicWALL UTM appliances

It is not possible in SonicWall UTM Appliacnes to connect between Spoke to Spoke in Hub and Spoke IPSec VPN topology as Gateway in Spoke can only one time.

We can solve this issue by using Route-Based VPN with Tunnel Interface.

Take a look at below sample network diagram and let's configure route-based vpn in two sonicwall utm appliances.




Step 1:
Log into the SonicWALL
Go to VPN > Settings and click on Add.
The General tab of Tunnel Interface VPN named 'to 2' is shown w/ the IPSec Gateway equal to the other device's X1 IP address, 2.2.2.2





Step 2:
Go to Network > routing and click Add .
The Route Policy example shown below is one in which the source is Any,
and the destination is the "2 Subnets", the service is Any,
and the Interface is set to the name of the previously-created Tunnel Interface VPN, named 'to 2' ; note that the Gateway field is grayed out because SonicOS is smart enough to know that there is already a specific network interface tied to the tunnel interface VPN created above.





I've shown the steps configure on Site 1 here.
You can try to configure on Site 2 by taking reference above steps and sample picture.

Once you've done configuration on both Site 1 and Site 2, you should able to ping both Site LAN network addresses vice versa.

This post is just basice route-based vpn creation among advanced route-based vpn technology for SonicWall.
I'll write how to use Dynamic Routing VPN by using OSPF if I've got some time.

I used NSA 3600 to demostrate this post and note that this route-based vpn is only work SonicWall to SonicWall.
It is not working on 3rd party devices and SonicWall.

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

Comments

  1. Please also keep in mind that the chances also change with the foundations. For instance, a royal flush, which is the rarest mixture, has different probabilities of being dealt and of being drawn. For additional details about the attainable hand rankings, please consult of} the desk below. Keep in mind, nevertheless, that our desk relies on Jacks or Better and most likely not|will not be} legitimate for 다파벳 various video poker online variations.

    ReplyDelete

Post a Comment

Popular posts from this blog

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

Solving the "A general system error occured:Invalid fault" error in vSphere 4

Below error was come out when you try to migrate VM to other host for some reason. Below error was come out when you try to edit VM setting. Below error was come out when you power on the VM. How to solve those error? Here is how I resolve the error! Login to the Host that errored VM exist by using Terminal or Direct Console. Enter below command and press enter. services.sh restart Wait until all VMware Services are restarted. After that try to Power On/Edit Settings or Migrate the errored VM and you will see all you can do without any error pop-up. This kind of errors can occur if you shutdown/restart VM unproperly or shutdown/restart the Host unproperly that VM exist. You can check log file deeply if you willing to know precisely on this. May you all be happy. (Be knowledgeable, pass it on then)

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