-
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
Routing MPLS network and Internet traffic through same WAN/X1 interface
09/19/2022 
52 People found this article helpful
487,878 Views
Description
Scenario:
MPLS and WAN on same interface. Have X1 as primary WAN connection, want to route MPLS traffic over the same interface.
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.
Step 1: Create a NAT to NOT translate the traffic when going to MPLS remote network, default route will take care of that and send it over to X1 default gateway.
Navigate to Policy|Rules and Policies > NAT Rules.
Step 2: ISP router should be configured to receive traffic for Internet with public ip as well as with private ip destined for MPLS remote network.
Step 3: Add a Access Rule from WAN to LAN.
Navigate to Policy|Rules and Policies|Access Rules.
Step 4: Click on Add.
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.
Step 1: Create a NAT to NOT translate the traffic when going to MPLS remote network, default route will take care of that and send it over to X1 default gateway.
Navigate to Manage | Rules > NAT Policies.
Step 2: ISP router should be configured to receive traffic for Internet with public ip as well as with private ip destined for MPLS remote network.
Step 3: Add a Access Rule from WAN to LAN.
Navigate to Rules > Access Rules.
Step 4: Click on Add.
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.
Step 1: Create a NAT to NOT translate the traffic when going to MPLS remote network, default route will take care of that and send it over to X1 default gateway.
Navigate to Manage | Rules > NAT Policies.
Step 2: ISP router should be configured to receive traffic for Internet with public ip as well as with private ip destined for MPLS remote network.
Step 3: Add a Access Rule from WAN to LAN.
Step 4: Click on Add.
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 > SonicWall NSA Series
- Firewalls > SonicWall SuperMassive 9000 Series
- Firewalls > SonicWall SuperMassive E10000 Series
- Firewalls > TZ Series
YES
NO