-
Products
-
Gen 7 Firewalls
SonicWall's Gen 7 platform-ready firewalls offer performance with stability and superior threat protection — all at an industry-leading TCO.
Read 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
How to control / restrict traffic over a site to site VPN tunnel using Access Rules
10/14/2021 
940 People found this article helpful
483,704 Views
Description
VPN: How to control / restrict traffic over a site to site VPN tunnel using Access Rules (SonicOS Enhanced)
This article illustrates how to restrict traffic to a particular IP Address and /or a Server over a site to site VPN tunnel. This way of controlling VPN traffic can be achieved by Access Rules.
For this scenario it is assumed that a site to site VPN tunnel between an NSA 2700 and a TZ 470 has been established and the tunnel up with traffic flowing both ways.
Now, all traffic from the the hosts behind the TZ 470 should be blocked except Terminal Services (RDP traffic to a Terminal Server behind the NSA 2700).
On the other hand, the hosts behind the NSA 2700 should be able to access everything behind the TZ 470 . The configuration of each firewall is the following:
| Site A (NSA 2700/ NSA 2600 ) WAN (X1) IP: 1.1.1.1 LAN: 192.168.1.0/24 | Site B (TZ 470/ TZ 600) WAN (X1) IP: 2.2.2.2 LAN: 10.10.10.0/24 |
Terminal Server IP: 192.168.1.2 | Default gateway of hosts: 10.10.10.1 (X0 ip) |
Resolution
Resolution for SonicOS 7.X
This release includes significant user interface changes and many new features that are different from the SonicOS 6.5 and earlier firmware. The below resolution is for customers using SonicOS 7.X firmware.
- Login to the SonicWall Management Interface on the NSA 2700 device.
- Click Object in the top navigation menu
- Navigate to the Match Objects |Addresses . Create a new Address Object for the Terminal Server IP Address 192.168.1.2.
- Navigate to the Policy | Rules and policies | Access Rules page.
- Select From VPN To LAN as shown in the screenshot.
- Create an Allow rule with Source as the address object for the Remote Site(Destination Network), Destination as the address object for the Terminal Server IP Address and Service as Terminal Services.
How to Test:
- From a host behind the TZ 470 , RDP to the Terminal Server IP 192.168.1.2.
- Pinging other hosts behind the NSA 2700 should fail.
- Likewise, hosts behind the NSA 2700 will be able to ping all hosts behind the TZ 470 .
Resolution for SonicOS 6.5
This release includes significant user interface changes and many new features that are different from the SonicOS 6.2 and earlier firmware. The below resolution is for customers using SonicOS 6.5 firmware.
- Login to the SonicWall Management Interface on the NSA 2600 device.
- Click Manage in the top navigation menu
- Navigate to the Policies | Objects | Address Objects page. Create a new Address Object for the Terminal Server IP Address 192.168.1.2.
- Navigate to the Policies | Rules | Access Rules page.
- Select From VPN To LAN as shown in the screenshot
- Ceate a Deny rule blocking all traffic from the remote site with details as per the screenshot. This will override the auto-created allow rule.
- Create an Allow rule with Source as the address object for the Remote Site, Destination as the address object for the Terminal Server IP Address and Service as Terminal Services.
How to Test:
- From a host behind the TZ 600 , RDP to the Terminal Server IP 192.168.1.2.
- Pinging other hosts behind the NSA 2600 should fail.
- Likewise, hosts behind the NSA 2600 will be able to ping all hosts behind the TZ 600 .
Resolution for SonicOS 6.2 and Below
The below resolution is for customers using SonicOS 6.2 and earlier firmware. For firewalls that are generation 6 and newer we suggest to upgrade to the latest general release of SonicOS 6.5 firmware.
- Login to the SonicWall Management Interface.
- Navigate to the Network | Address Objects page.
- Create a new Address Object for the Terminal Server IP Address 192.168.1.2.
- Navigate to the Firewall | Access Rules page.
- Select From VPN | To LAN from the drop-down list or matrix.
- Create a Deny rule blocking all traffic from the remote site with details as per the screenshot. This will override the auto-created allow rule.
- Create an Allow rule with Source as the address object for the Remote Site, Destination as the address object for the Terminal Server IP Address and Service as Terminal Services.
How to Test:
- From a host behind the TZ 600 , RDP to the Terminal Server IP 192.168.1.2.
- Pinging other hosts behind the NSA 2600 should fail.
- Likewise, hosts behind the NSA 2600 will be able to ping all hosts behind the TZ 600 .
Related Articles
- How to access a more specific network over VPN tunnel while having another Route All VPN policy
- How to limit bandwidth usage when playing YouTube videos using App Rules
- SonicWall TZ80 In-Product settings migration
Categories
- Firewalls > SonicWall NSA Series
- Firewalls > SonicWall SuperMassive 9000 Series
- Firewalls > SonicWall SuperMassive E10000 Series
- Firewalls > TZ Series
YES
NO