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
Add DHCP Dynamic Scope
To add a dynamic scope
- From the General view, to enable this scope, ensure Enable this DHCP Scope is selected. This option is selected by default.
-
To populate the Range Start, Range End, Default Gateway, and Subnet Mask fields:
-
With default values for a certain interface:
- Select Interface Pre-Populate near the bottom of the dialog. The selections become available. This option is not selected by default.
- Select the interface. The populated IP addresses are in the same private subnet as the selected interface.
To select an interface from Interface Pre-Populate, the interface must first be fully configured and it must be either:
- Of the zone type LAN, WLAN, or DMZ.
- A VLAN subinterface
- Go to Step 3.
-
Manually:
- Type in your own IP address range.
- Enter the number of minutes an IP address is leased by the scope before it is issued another IP address in the Lease Time (minutes) field. The minimum is 0, the maximum is 71582789, and 1440 minutes (24 hours) is the default.
- Enter the IP address of the gateway into the Default Gateway field.
- Enter the gateway subnet mask into the Subnet Mask field.
-
- Optionally, enter a comment in the Comment field.
-
The Interface Pre-Populate option populates the DHCP scope configuration with information from the selected interface. After the scope has been added, you might notice that the Interface reads “N/A.”
-
Select Allow BOOTP Clients to use Range if you have BOOTP Clients on your network. This option is not selected by default.
BOOTP stands for bootstrap protocol, which is a TCP/IP protocol and service that allows disables workstations to obtain their IP address, other TCP/IP configuration information, and their boot image file from a BOOTP server.
- Click DNS/WINS to continue configuring the DHCP Server feature.
Was This Article Helpful?
Help us to improve our support portal