SonicOSX 7 System
- SonicOSX 7
- 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 SonicOSX 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
- 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
One Arm Mode and Single Interface Support
One Arm Mode is when only one firewall interface is used, and all traffic comes into and out from the same interface. It is possible to apply security rules and Deep Packet Inspection (DPI) scans on data traffic from the One Arm interface. Data received from this interface is scanned by SonicOSX security services and then sent out on this interface.
One example usage scenario is shown below for SonicWall Cloud Edge. Cloud Edge works well when using a single interface on the firewall where traffic comes into and goes out from the same interface.
For One Arm Mode, you need to configure the interface:
- Interface must have a valid IP address (IPv4 or IPv6) configured. This can be a static IP address or a DHCP address.
- Must have One Arm Peer (next hop IP address) configured.
- Only LAN or WAN zone interfaces allow One Arm Mode in SonicOSX 7.0.1.
When you complete the One Arm Mode interface configuration, SonicOSX automatically updates the system configuration to support One Arm Mode.
If the One Arm Mode interface is in the LAN zone, options on the NETWORK | Firewall > Advanced page are enabled or disabled. These are under ACCESS RULE OPTIONS:
- Enable Apply firewall rules for intra-LAN traffic to/from the same interface - enable LAN-to-LAN security scanning
-
Disable Enable ICMP Redirect on LAN zone - disable ICMP redirect if One Arm Mode interface is in LAN zone
An address object for the One Arm Peer is automatically created.
A security policy to allow traffic from One Arm Mode interface to One Arm Mode interface is automatically created so traffic will always be allowed.
A routing policy is automatically added with the One Arm Peer as the gateway to allow other traffic to apply One Arm routing, if needed.
For using a single interface on the firewall, the minimum number of NIC is changed to 1. To use only X0, you need to shut down X1 to make all traffic go out from X0. When you shut down X1, the priority of the One Arm routing policy becomes higher than the default route priority and traffic will use the X0 One Arm routing policy.
For configuration of a One Arm Mode interface, see Configuring One Arm Mode.
Was This Article Helpful?
Help us to improve our support portal