Wireless > Virtual Access Point
360
SonicOS Enhanced 4.0 Administrator Guide
• Subnet Name: The name of the interface.
• IP Address: The first IP address in the subnet. Make sure that the IP address subnet does
not conflict with another address range.
• Subnet Mask: 255.255.255.0 is the default
• SonicPoint Limit: The maximum number of allowed SonicPoints is configured automatically.
• Comment: Optionally enter a comment about the subnet.
• Management: Select the appropriate protocols to allow remote management of the
SonicWALL security appliance from this subnet.
• User Login: Select HTTP and/or HTTPS to allow users with limited management rights to
log in to the SonicWALL security appliance.
• Add rule to enable redirect from HTTP to HTTPS: If you select HTTPS but do not select
HTTP for either Management or User Login, select this option to redirect HTTP users to
HTTPS.
• Create default DHCP Lease Scope: Select to create a DHCP lease scope for this subnet.
The DHCP lease scope consists of the IP addresses that are reserved for users who
connect to the VAP associated with this WLAN subnet. This option is enabled by default.
To configure additional options for the DHCP lease scope (such as the number of IP
addresses and the lease time), go to the Network > DHCP Server page, locate the lease
scope in the DHCP Server Lease Scope table, and click on the Configure icon. See
“Network > DHCP Server” section on page 277 for more information.
Step 4 Optionally, you can enable multicast reception on the subnet by clicking on the Advanced tab
and selecting the Enable multicast support checkbox.
Step 5 Clic k OK.
DHCP Server Scope
The DHCP server assigns leased IP addresses to users within specified ranges, known as
“Scopes”. The default ranges for DHCP scopes are often excessive for the needs of most
SonicPoint deployments, for instance, a scope of 200 addresses for an interface that will only
use 30. Because of this, DHCP ranges must be set carefully in order to ensure the available
lease scope is not exhausted.
The DHCP scope should be resized as each interface/sub-interface is defined to ensure that
adequate DHCP space remains for all subsequently defined interfaces. Failure to do so may
cause the auto-creation of subsequent DHCP scopes to fail, requiring manual creation after
performing the requisite scope resizing. DHCP Server Scope is set from the Network > DHCP
Server page.