SonicOS 7.1 System
- SonicOS 7.1
- About SonicOS
- Interfaces
- About Interfaces
- Interface Settings IPv4
- Adding Virtual Interfaces
- Configuring Routed Mode
- Enabling Bandwidth Management on an Interface
- Configuring Interfaces in Transparent IP Mode (Splice L3 Subnet)
- Configuring Wireless Interfaces
- Configuring WAN Interfaces
- Configuring Tunnel Interfaces
- Configuring VPN Tunnel Interfaces
- Configuring Link Aggregation and Port Redundancy
- Configuring One Arm Mode
- Configuring an IPS Sniffer Mode Appliance
- Configuring Security Services (Unified Threat Management)
- Configuring Wire and Tap Mode
- Layer 2 Bridged Mode
- Key Features of SonicOS Layer 2 Bridged Mode
- Key Concepts to Configuring L2 Bridged Mode and Transparent Mode
- Comparing L2 Bridged Mode to Transparent Mode
- Comparison of L2 Bridged Mode to Transparent Mode
- Benefits of Transparent Mode over L2 Bridged Mode
- ARP in Transparent Mode
- VLAN Support in Transparent Mode
- Multiple Subnets in Transparent Mode
- Non-IPv4 Traffic in Transparent Mode
- ARP in L2 Bridged Mode
- VLAN Support in L2 Bridged Mode
- L2 Bridge IP Packet Path
- Multiple Subnets in L2 Bridged Mode
- Non-IPv4 Traffic in L2 Bridged Mode
- L2 Bridge Path Determination
- L2 Bridge Interface Zone Selection
- Sample Topologies
- Configuring Network Interfaces and Activating L2B Mode
- Configuring Layer 2 Bridged Mode
- Asymmetric Routing
- Configuring Interfaces for IPv6
- 31-Bit Network Settings
- PPPoE Unnumbered Interface Support
- Failover & LB
- Neighbor Discovery
- ARP
- MAC IP Anti-Spoof
- Web Proxy
- PortShield Groups
- SonicOS Support of X-Series Switches
- About the X-Series Solution
- Performance Requirements
- Key Features Supported with X-Series Switches
- PortShield Functionality and X-Series Switches
- PoE/PoE+ and SFP/SFP+ Support
- X-Series Solution and SonicPoints
- Managing Extended Switches using GMS
- Extended Switch Global Parameters
- About Links
- Logging and Syslog Support
- Supported Topologies
- Port Graphics
- Port Configuration
- External Switch Configuration
- External Switch Diagnostics
- Configuring PortShield Groups
- SonicOS Support of X-Series Switches
- PoE Settings
- VLAN Translation
- IP Helper
- Dynamic Routing
- DHCP Server
- Configuring a DHCP Server
- Configuring Advanced Options
- Configuring DHCP Option Objects
- Configuring DHCP Option Groups
- Configuring a Trusted DHCP Relay Agent Address Group (IPv4 Only)
- Enabling Trusted DHCP Relay Agents
- Configuring IPv4 DHCP Servers for Dynamic Ranges
- Configuring IPv6 DHCP Servers for Dynamic Ranges
- Configuring IPv4 DHCP Static Ranges
- Configuring IPv6 DHCP Static Ranges
- Configuring DHCP Generic Options for DHCP Lease Scopes
- DHCP and IPv6
- Multicast
- Network Monitor
- AWS Configuration
- SonicWall Support
Configuring the Primary Bridge Interface
To configure the primary bridge interface
- Navigate to NETWORK | System > Interfaces.
- Click the Configure icon in the right column of interface X2. The Edit Interface dialog displays.
-
Select LAN from the Zone drop-down menu. More options display.
You do not need to configure settings on the Advanced or VLAN Filtering tabs.
- For Mode / IP Assignment, select Static IP Mode.
-
Configure the interface with a static IP Address (for example,
10.1.2.3
). The IP address you choose should not collide with any of the networks that are seen by the switch.The Primary Bridge Interface must have a static Mode / IP Assignment.
- In the Subnet Mask field, enter the subnet mask. The default is
255.255.255.0
. -
A gateway is optional for DMZ and LAN zone interfaces. If desired, type the IP address of the gateway device into the Default Gateway field. The gateway device provides access between this interface and the external network, whether it is the Internet or a private network.
A default gateway IP is required on a WAN interface if any destination is required to be reached through the WAN interface that is not part of the WAN subnet IP address space, regardless whether we receive a default route dynamically from a routing protocol of a peer device on the WAN subnet.
- Type in a descriptive Comment.
-
The Domain Name field is used to bound an accurate domain name with all web services provided by this interface. The value can be one of the following:
-
An FQDN address (
*.company.com / www.company.com
) -
An IPv4 or IPv6 address string (
a.a.a.a / b:b:b:b:b:b:b:b
)When configured, all web access, along with SSL VPN service, should be accessed by only the Domain Name. No other attempts are allowed.
Access through an exact IP address is implicitly trusted, whether this field is set or not.
To enable this feature, make sure the Enforce HTTP Host Header Check option located on the Administrator page, is enabled as well.
-
- Choose Management option(s) for the interface: HTTPS, Ping, SNMP, SSH.
- Choose User Login options: HTTP, HTTPS.
- To enable redirect to HTTPS from HTTP, select Add rule to enable redirect from HTTP to HTTPS. For more information about this option, see HTTP/HTTPS Redirection.
- Click OK.
Was This Article Helpful?
Help us to improve our support portal