Configuring Layer 2 Bridge Mode in SonicOS Enhanced

10/14/2021 186 People found this article helpful 60,531 Views

Download

Print

Share

• LinkedIn
• Twitter
• Facebook
• Email
• Copy URL The link has been copied to clipboard

Description

SonicOS Enhanced firmware versions 4.0 and higher includes L2 (Layer 2) Bridge Mode, a new method of unobtrusively integrating a SonicWall security appliance into any Ethernet network. L2 Bridge Mode is ostensibly similar to SonicOS Enhanced Transparent Mode in that it enables a SonicWall security appliance to share a common subnet across two interfaces, and to perform Stateful and deep-packet inspection on all traversing IP traffic, but it is functionally more versatile.

In particular, L2 Bridge Mode employs a secure learning bridge architecture, enabling it to pass and inspect traffic types that cannot be handled by many other methods of transparent security appliance integration. Using L2 Bridge Mode, a SonicWall security appliance can be non-disruptively added to any Ethernet network to provide in-line deep-packet inspection for all traversing IPv4 TCP and UDP traffic. In this scenario the SonicWall UTM appliance is not used for security enforcement, but instead for bidirectional scanning, blocking viruses and spyware, and stopping intrusion attempts.

Unlike other transparent solutions, L2 Bridge Mode can pass all traffic types, including IEEE 802.1Q VLANs (on SonicWall NSA appliances), Spanning Tree Protocol, multicast, broadcast, and IPv6, ensuring that all network communications will continue uninterrupted.

Resolution

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.

Configuring the Primary Bridge Interface

Choose an interface to act as the Primary Bridge Interface. In this example, we will use X2 interface (WAN). Follow below steps to configure X2 interface as WAN.

1. Login to your SonicWall management page and click Manage tab on top of the page.
2. Navigate to Network | Interfaces page, click configure button of X2 interface.
3. Zone: WAN.
4. IP Assignment: Static.
5. IP Address: 192.168.160.50 (In this example we configured 192.168.160.0/24 subnet).
6. Configure Subnet Mask, Default Gateway, DNS Server 1, DNS Server 2 & DNS Server 3.
7. Enable or Disable Management & User login of new zone based on your requirement.
8. Click OK .
   .
    NOTE: The Primary Bridge Interface must have a Static IP assignment.

Configuring the Secondary Bridge Interface

Choose an interface to act as the Secondary Bridge Interface. In this example, we will use X0 (automatically assigned to the LAN).

1. Login to your SonicWall management page and click on Manage tab on top of the page.
2. Navigate to Network | Interfaces page, click configure button of X0 interface.
3. Zone:  LAN.
4. Mode / IP Assignment: Layer 2 Bridge Mode (IP Route Option).
5. Bridged to: X2.
6. Enable Management & User Login if you want to manage it.
7. Click OK .
   
8. You may optionally enable the Block all non-IPv4 traffic setting to prevent the L2 bridge from passing non-IPv4 traffic. VLAN Filtering (on SonicWall NSA series appliances).
   
   
   • You may also optionally navigate to the VLAN Filtering tab to control VLAN traffic through the L2 bridge. By default, all VLANs are allowed:
   • Select Block listed VLANs (blacklist) from the drop-down list and add the VLANs you wish to block from the left pane to the right pane. All VLANs added to the right pane will be blocked, and all VLANs remaining in the left pane will be allowed.
   • Select Allow listed VLANs (whitelist) from the drop-down list and add the VLANs you wish to explicitly allow from the left pane to the right pane. All VLANs added to the right pane will be allowed, and all VLANs remaining in the left pane will be blocked.
     
9. The Network | Interfaces page displays the updated configuration: You may now apply security services to the appropriate zones, as desired. In this example, they should be applied to the LAN, WAN, or both zones.
   
   
   

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.

Configuring the Primary Bridge Interface

Choose an interface to act as the Primary Bridge Interface. In this example, we will use X1 (automatically assigned to the Primary WAN): Network | Interfaces 

1. Select the Network tab, Interfaces folder from the navigation panel. 
2. Click Configure icon in the right column of the X1 (WAN) interface.
3. Configure the interface with a Static IP address.
   

   EXAMPLE: 192.168.160.50
   
   
   NOTE: The Primary Bridge Interface must have a Static IP assignment.

4. Configure the default gateway. This is required for the security appliance itself to reach the Internet. (This applies only to WAN interfaces).
5. Configure the DNS server. (This applies only to WAN interfaces).
6. Configure management (HTTP, HTTPS, Ping, SNMP, SSH, User Logins, HTTP Redirects).
7. Click OK.

Configuring the Secondary Bridge Interface

Choose an interface to act as the Secondary Bridge Interface. In this example, we will use X0 (automatically assigned to the LAN): Network | Interfaces.

1. On the Network | Interfaces page, click Configure icon in the right column of the X0 (LAN) interface.
2. In the IP Assignment drop-down list, select Layer 2 Bridged Mode.
3. In the Bridged to drop-down list, select the X1 interface.
4. Configure management (HTTP, HTTPS, Ping, SNMP, SSH, User Logins, HTTP Redirects).
   
5. You may optionally enable the Block all non-IPv4 traffic setting to prevent the L2 bridge from passing non-IPv4 traffic. VLAN Filtering (on SonicWall NSA series appliances).
   
   
   • You may also optionally navigate to the VLAN Filtering tab to control VLAN traffic through the L2 bridge. By default, all VLANs are allowed:
   • Select Block listed VLANs (blacklist) from the drop-down list and add the VLANs you wish to block from the left pane to the right pane. All VLANs added to the right pane will be blocked, and all VLANs remaining in the left pane will be allowed.
   • Select Allow listed VLANs (whitelist) from the drop-down list and add the VLANs you wish to explicitly allow from the left pane to the right pane. All VLANs added to the right pane will be allowed, and all VLANs remaining in the left pane will be blocked.
     
     
6. Click OK.
   
   

   NOTE: The Network | Interfaces page displays the updated configuration: You may now apply security services to the appropriate zones, as desired. In this example, they should be applied to the LAN, WAN, or both zones.

Related Articles

• How to force an update of the Security Services Signatures from the Firewall GUI
• How to upload security services signatures manually on Closed Environments?
• How to Create Gen 7 Settings File by Using the Online Migration Tool

Categories

• Firewalls > NSa Series > Networking
• Firewalls > TZ Series > Networking