-
Products
-
SonicPlatform
SonicPlatform is the cybersecurity platform purpose-built for MSPs, making managing complex security environments among multiple tenants easy and streamlined.
Discover More
-
-
Solutions
-
Federal
Protect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
Learn MoreFederalProtect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
Learn More - Industries
- Use Cases
-
-
Partners
-
Partner Portal
Access to deal registration, MDF, sales and marketing tools, training and more
Learn MorePartner PortalAccess to deal registration, MDF, sales and marketing tools, training and more
Learn More - SonicWall Partners
- Partner Resources
-
-
Support
-
Support Portal
Find answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
Learn MoreSupport PortalFind answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
Learn More - Support
- Resources
- Capture Labs
-
- Company
- Contact Us
Adding a subnet to an existing Site to Site VPN Tunnel (SonicOS Enhanced)(KB Article and
03/26/2020 
881 People found this article helpful
494,222 Views
Description
VPN: Adding a subnet to an existing Site to Site VPN Tunnel (SonicOS Enhanced)(KB Article and Video Tutorial)
Resolution
To watch a video tutorial on this topic, click here
Feature/Application:
Adding a subnet or subnets to an existing Site to Site VPN Tunnel (SonicOS Enhanced). This scenario based article illustrates how additional subnet/s can be added to an active Site to Site VPN tunnel between two Sonicwall appliances.
In this scenario we have an active VPN tunnel between a NSA 2400 (Site A) at the central site and a NSA 240 (Site B) at the remote site with the following configuration:
Site A : NSA 2400: X1: WAN - 1.1.1.1
X0: LAN - 192.168.1.0/24
Site B: NSA 240: X1: WAN - 2.2.2.2
X0: LAN - 10.10.10.0/24
The Tunnel is up and both sites are able to access the other site's LAN segment.
Site A has expanded their network to include a DMZ segment to their local network: X2: DMZ - 192.168.2.0/24. In order to add the new subnets to the site to site VPN tunnel follow these directions:
Procedure:
Central Site Configuration (Site A)
Step 1. Create a group called Central Site Network and add the default Address Objects X0 Subnets and X2 Subnets to it.
Step 2. Edit the VPN Policy and select the group Central Site Network from the "Choose local network from list" drop-down list under Local Networks in the Network tab.
Step 3. Click on OK to save the settings.
Remote Site Configuration (Site B)
Step 1. Create an Address Object called Central Site DMZ with the following settings:
Name: Central Site DMZ
Zone: VPN
Type: Network
Network: 192.168.2.0
Net Mask: 255.255.255.0
Step 2. Create a group called Central Site Network and add Address Objects Central Site LAN and Central Site DMZ to it. Here it is assumed that an address object Central Site LAN was created when configuring the Site to Site VPN.
Step 3. Edit the VPN Policy and select the group Central Site Network from the "Choose destination network from list" drop-down list under Desination Networks in the Network tab.
Step 4. Click on OK to save the settings.
How to Test:
Ping from a workstation on the Remote Site to a workstation in the X2 subnet on the Central Site, for eg. 192.168.2.2. Refresh the VPN > Settings page on both side and you should see a green icon on both LAN and DMZ segments.
Related Articles
- How to Block Google QUIC Protocol on SonicOSX 7.0?
- How to block certain Keywords on SonicOSX 7.0?
- How internal Interfaces can obtain Global IPv6 Addresses using DHCPv6 Prefix Delegation
Categories
- Firewalls > TZ Series
- Firewalls > SonicWall SuperMassive E10000 Series
- Firewalls > SonicWall SuperMassive 9000 Series
- Firewalls > SonicWall NSA Series
YES
NO