SonicPoint_wlanSonicVapView
SonicPoint > Virtual Access Point
This chapter describes the Virtual Access Point feature and includes the following sections:
SonicPoint VAP Overview
This section provides an introduction to the Virtual Access Point feature.
|
|
|
Virtual Access Points are supported when using SonicPoint wireless access points along with SonicWALL NSA appliances. For Virtual Access Point configuration using a TZ appliance, see the “Wireless > Virtual Access Point” section . |
This section contains the following subsections:
What Is a Virtual Access Point?
A Virtual Access Point is a multiplexed instantiation of a single physical Access Point (AP) so that it presents itself as multiple discrete Access Points. To wireless LAN clients, each Virtual AP appears to be an independent physical AP, when in actuality there is only a single physical AP. Before the evolution of the Virtual AP feature support, wireless networks were relegated to a One-to-One relationship between physical Access Points and wireless network security characteristics, such as authentication and encryption. In other words, an Access Point providing WPA-PSK security could not simultaneously offer Open or WPA-EAP connectivity to clients, and if the latter were required, they would had to have been provided by a separate, distinctly configured Access Points. This forced WLAN network administrators to find a solution to scale their existing wireless LAN infrastructure to provide differentiated levels of service. With the Virtual APs (VAP) feature, multiple VAPs can exist within a single physical AP in compliance with the IEEE 802.11 standard for the media access control (MAC) protocol layer that includes a unique Basic Service Set Identifier (BSSID) and Service Set Identified (SSID). This allows for segmenting wireless network services within a single radio frequency footprint of a single physical access point device.
VAPs allow the network administrator to control wireless user access and security settings by setting up multiple custom configurations on a single physical interface. Each of these custom configurations acts as a separate (virtual) access point, and can be grouped and enforced on single or multiple physical SonicPoint access points simultaneously.
For more information on SonicOS Secure Wireless features, refer to the SonicWALL Secure Wireless Integrated Solutions Guide .
What Is an SSID?
A Service Set IDentifier (SSID) is the name assigned to a wireless network. Wireless clients must use this same, case-sensitive SSID to communicate to the SonicPoint. The SSID consists of a text string up to 32 bytes long. Multiple SonicPoints on a network can use the same SSIDs. You can configure up to 8 unique SSIDs on SonicPoints and assign different configuration settings to each SSID.
SonicPoints broadcast a beacon (announcements of availability of a wireless network) for every SSID configured. By default, the SSID is included within the beacon so that wireless clients can see the wireless networks. The option to suppress the SSID within the beacon is provided on a per-SSID (e.g. per-VAP or per-AP) basis to help conceal the presence of a wireless network, while still allowing clients to connect by manually specifying the SSID.
The following settings can be assigned to each VAP:
|
|
|
VLAN |
Wireless Roaming with ESSID
An ESSID (Extended Service Set IDentifier) is a collection of Access Points (or Virtual Access Points) sharing the same SSID. A typical wireless network comprises more than one AP for the purpose of covering geographic areas larger than can be serviced by a single AP. As clients move through the wireless network, the strength of their wireless connection decreases as they move away from one Access Point (AP1) and increases as they move toward another (AP2). Providing AP1 and AP2 are on the same ESSID (for example, ‘sonicwall’) and that the (V)APs share the same SSID and security configurations, the client will be able to roam from one to the other. This roaming process is controlled by the wireless client hardware and driver, so roaming behavior can differ from one client to the next, but it is generally dependent upon the signal strength of each AP within an ESSID.
What Is a BSSID?
A BSSID (Basic Service Set IDentifier) is the wireless equivalent of a MAC (Media Access Control) address, or a unique hardware address of an AP or VAP for the purposes of identification. Continuing the example of the roaming wireless client from the ESSID section above, as the client on the ‘sonicwall’ ESSID moves away from AP1 and toward AP2, the strength of the signal from the former will decrease while the latter increases. The client’s wireless card and driver constantly monitors these levels, differentiating between the (V)APs by their BSSID. When the card/driver’s criteria for roaming are met, the client will detach from the BSSID of AP1 and attach to the BSSID or AP2, all the while remaining connected the ‘sonicwall’ ESSID.
Benefits of Using Virtual APs
This section includes a list of benefits in using the Virtual AP feature:
|
|
|
Radio Channel Conservation —Prevents building overlapped infrastructures by allowing a single Physical Access Point to be used for multiple purposes to avoid channel collision problem. Channel conservation. Multiple providers are becoming the norm within public spaces such as airports. Within an airport, it might be necessary to support an FAA network, one or more airline networks, and perhaps one or more Wireless ISPs. However, in the US and Europe, 802.11b networks can only support three usable (non-overlapping) channels, and in France and Japan only one channel is available. Once the channels are utilized by existing APs, additional APs will interfere with each other and reduce performance. By allowing a single network to be used for multiple purposes, Virtual APs conserve channels. |
|
|
|
Optimize SonicPoint LAN Infrastructur e—Share the same SonicPoint LAN infrastructure among multiple providers, rather than building an overlapping infrastructure, to lower down the capital expenditure for installation and maintenance of your WLANs. |
Benefits of Using Virtual APs with VLANs
Although the implementation of VAPs does not require the use of VLANs, VLAN use does provide practical traffic differentiation benefits. When not using VLANs, the traffic from each VAP is handled by a common interface on the SonicWALL security appliance. This means that all traffic from each VAP will belong to the same zone and same subnet (Footnote: a future version of SonicOS Enhanced will allow for traffic from different VAPs to exist on different subnets within the same zone, providing a measure of traffic differentiation even without VLAN tagging). By tagging the traffic from each VAP with a unique VLAN ID, and by creating the corresponding subinterfaces on the SonicWALL security appliance, it is possible to have each VAP occupy a unique subnet, and to assign each subinterface to its own zone.
This affords the following benefits:
|
|
|
Separate Guest Services or Lightweight Hotspot Messaging (LHM) configurations can be applied to each, facilitating the presentation of multiple guest service providers with a common set of SonicPoint hardware. |
Prerequisites
|
|
|
Each SonicWALL SonicPoint must be explicitly enabled for Virtual Access Point support by selecting the SonicPoint > SonicPoints > General Settings Tab : “Enable SonicPoint” checkbox in the SonicOS management interface and enabling either Radio A or G. |
|
|
|
SonicPoints must be linked to a WLAN zone on your SonicWALL UTM appliance in order for provisioning of APs to take place. |
|
|
|
When using VAPs with VLANs, you must ensure that the physical SonicPoint discovery and provisioning packets remain untagged (unless being terminated natively into a VLAN subinterface on the SonicWALL). You must also ensure that VAP packets that are VLAN tagged by the SonicPoint are delivered unaltered (neither un-encapsulated nor double-encapsulated) by any intermediate equipment, such as a VLAN capable switch, on the network. |
Deployment Restrictions
When configuring your VAP setup, be aware of the following deployment restrictions:
|
|
|
Maximum SonicPoint restrictions apply and differ based on your SonicWALL security appliance. Review these restrictions in the “Custom VLAN Settings” section . |
SonicPoint Virtual AP Configuration Task List
A SonicPoint VAP deployment requires several steps to configure. The following section provides first a brief overview of the steps involved, and then a more in-depth examination of the parts that make up a successful VAP deployment. This subsequent sections describe VAP deployment requirements and provides an administrator configuration task list:
SonicPoint VAP Configuration Overview
The following are required areas of configuration for VAP deployment:
|
|
Zone - The zone is the backbone of your VAP configuration. Each zone you create will have its own security and access control settings and you can create and apply multiple zones to a single physical interface by way of VLAN subinterfaces. |
|
|
Interface (or VLAN Subinterface) - The Interface (X2, X3, etc...) represents the physical connection between your SonicWALL UTM appliance and your SonicPoint(s). Your individual zone settings are applied to these interfaces and then forwarded to your SonicPoints. |
|
|
DHCP Server - 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. |
|
|
VAP Profile - The VAP Profile feature allows for creation of SonicPoint configuration profiles which can be easily applied to new SonicPoint Virtual Access Points as needed. |
|
|
VAP Objects - The VAP Objects feature allows for setup of general VAP settings. SSID and VLAN ID are configured through VAP Settings. |
|
|
VAP Groups - The VAP Group feature allows for grouping of multiple VAP objects to be simultaneously applied to your SonicPoint(s). |
|
|
Assign VAP Group to SonicPoint Provisioning Profile Radio - The Provisioning Profile allows a VAP Group to be applied to new SonicPoints as they are provisioned. |
|
|
Assign WEP Key (for WEP encryption only) - The Assign WEP Key allows for a WEP Encryption Key to be applied to new SonicPoints as they are provisioned. WEP keys are configured per-SonicPoint, meaning that any WEP-enabled VAPs assigned to a SonicPoint must use the same set of WEP keys. Up to 4 keys can be defined per-SonicPoint, and WEP-enabled VAPs can use these 4 keys independently. WEP keys are configured on individual SonicPoints or on SonicPoint Profiles from the SonicPoint > SonicPoints page. |
Network Zones
This section contains the following subsections:
A network security zone is a logical method of grouping one or more interfaces with friendly, user-configurable names, and applying security rules as traffic passes from one zone to another zone. With the zone-based security, the administrator can group similar interfaces and apply the same policies to them, instead of having to write the same policy for each interface. Network zones are configured from the Network > Zones page.
For detailed information on configuring zones, see Chapter 18, Network > Zones .
The Wireless Zone
The Wireless zone type, of which the “WLAN Zone” is the default instance, provides support to SonicWALL SonicPoints. When an interface or subinterface is assigned to a Wireless zone, the interface can discover and provision Layer 2 connected SonicPoints, and can also enforce security settings above the 802.11 layer, including WiFiSec Enforcement, SSL VPN redirection, Guest Services, Lightweight Hotspot Messaging and all licensed Deep Packet Inspection security services.
|
|
|
SonicPoints can only be managed using untagged, non-VLAN packets. When setting up your WLAN, ensure that packets sent to the SonicPoints are non VLAN tagged. |
Custom Wireless Zone Settings
Although SonicWALL provides the pre-configured Wireless zone, administrators also have the ability to create their own custom wireless zones. When using VAPs, several custom zones can be applied to a single, or multiple SonicPoint access points. The following three sections describe settings for custom wireless zones:
General
|
Select Wireless in order to enable and access wireless security options. |
|
|
Select this option to automatically create access rules to allow traffic to flow between the interfaces of a zone. This will effectively allow users on a wireless zone to communicate with each other. This option is often disabled when setting up Guest Services. |
|
|
SonicWALL Security Services |
Select the security services you wish to enforce on this zone. This allows you to extend your SonicWALL UTM security services to your SonicPoints. |
Wireless
|
Only allow traffic generated by a SonicPoint |
Restricts traffic on this zone to SonicPoint-generated traffic only. |
|
Redirects all traffic entering the Wireless zone to a defined SonicWALL SSL VPN appliance. This allows all wireless traffic to be authenticated and encrypted by the SSL VPN, using, for example, NetExtender to tunnel all traffic. Note: Wireless traffic that is tunneled through an SSL VPN will appear to originate from the SSL VPN rather than from the Wireless zone. SSL VPN Server - Select the Address Object representing the SSL VPN appliance to which you wish to redirect wireless traffic. |
|
|
Requires all traffic be either IPsec or WPA. With this option checked, all non-guest connections must be IPsec enforced. WiFiSec Exception Service - Select the service(s) you wish to be exempt from WiFiSec Enforcement. |
|
|
Require WiFiSec for Site-to- site VPN Tunnel Traversal |
For use with WiFiSec enforcement, requires WiFiSec security on all site-to-site VPN connections through this zone. |
|
Trust WPA/WPA2 traffic as WiFiSec |
|
|
SonicPoint Provisioning Profile |
Select a predefined SonicPoint Provisioning Profile to be applied to all current and future SonicPoints on this zone. |
Guest Services
The Enable Guest Services option allows the following guest services to be applied to a zone:
|
Enable inter-guest communication |
Allows guests connecting to SonicPoints in this Wireless zone to communicate directly and wirelessly with each other. |
|
Bypass AV Check for Guests |
|
|
Enable Dynamic Address Translation (DAT) |
Dynamic Address Translation (DAT) allows the SonicPoint to support any IP addressing scheme for Guest Services users. If this option is disabled (unchecked), wireless guest users must either have DHCP enabled, or an IP addressing scheme compatible with the SonicPoint’s network settings. |
|
Enable External Guest Authentication |
Requires guests connecting from the device or network you select to authenticate before gaining access. This feature, based on Lightweight Hotspot Messaging (LHM) is used for authenticating Hotspot users and providing them parametrically bound network access. |
|
Redirects users to a custom authentication page when they first connect to a SonicPoint in the Wireless zone. Click Configure to set up the custom authentication page. Enter either a URL to an authentication page or a custom challenge statement in the text field, and click OK. |
|
|
Directs users to the page you specify immediately after successful authentication. Enter a URL for the post-authentication page in the filed. |
|
|
Bypass Guest Authentication |
Allows a SonicPoint running Guest Services to integrate into environments already using some form of user-level authentication. This feature automates the Guest Services authentication process, allowing wireless users to reach Guest Services resources without requiring authentication. This feature should only be used when unrestricted Guest Services access is desired, or when another device upstream of the SonicPoint is enforcing authentication. |
|
Redirects SMTP traffic incoming on this zone to an SMTP server you specify. Select the address object to redirect traffic to. |
|
|
Blocks traffic from the networks you specify. Select the subnet, address group, or IP address to block traffic from. |
|
|
Automatically allows traffic through the Wireless zone from the networks you select. |
|
|
Specifies the maximum number of guest users allowed to connect to the Wireless zone. The default is 10. |
VLAN Subinterfaces
A Virtual Local Area Network (VLAN) allows you to split your physical network connections (X2, X3, etc...) into many virtual network connection, each carrying its own set of configurations. The VLAN solution allows each VAP to have its own separate subinterface on an actual physical interface.
VLAN subinterfaces have most of the capabilities and characteristics of a physical interface, including zone assignability, security services, WAN assignability (static addressing only), GroupVPN, DHCP server, IP Helper, routing, and full NAT policy and Access Rule controls. Features excluded from VLAN subinterfaces at this time are VPN policy binding, WAN dynamic client support, and multicast support.
VLAN subinterfaces are configured from the Network > Interfaces page.
Custom VLAN Settings
The table below lists configuration parameters and descriptions for VLAN subinterfaces:
|
Select a zone to inherit zone settings from a predefined or custom user-defined zone. |
|
|
Select a physical parent interface (X2, X3, etc...) for the VLAN. |
|
|
Create an IP address and Subnet Mask in accordance with your network configuration. |
|
|
Select the maximum number of SonicPoints to be used on this interface. Below are the maximum number of SonicPoints per interface based on your SonicWALL UTM hardware: |
|
|
Select the protocols you wish to use when managing this interface. |
|
|
Select the protocols you will make available to clients who access this subinterface. |
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/subinterface 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.
The table below shows maximum allowed DHCP leases for SonicWALL security appliances.
Virtual Access Points Profiles
A Virtual Access Point Profile allows the administrator to pre-configure and save access point settings in a profile. VAP Profiles allows settings to be easily applied to new Virtual Access Points. Virtual Access Point Profiles are configured from the SonicPoint > Virtual Access Point page.
Virtual Access Point Profile Settings
The table below lists configuration parameters and descriptions for Virtual Access Point Profile Settings:
|
Choose a friendly name for this VAP Profile. Choose something descriptive and easy to remember as you will later apply this profile to new VAPs. |
|||||||
|
Set to SonicPoint by default. Retain this default setting if using SonicPoints as VAPs (currently the only supported radio type) |
|||||||
|
Below is a list available authentication types with descriptive features and uses for each:
|
|||||||
|
The unicast cipher will be automatically chosen based on the authentication type. |
|||||||
|
The multicast cipher will be automatically chosen based on the authentication type. |
|||||||
|
Choose the maximum number of concurrent client connections permissible for this virtual access point. |
WPA-PSK / WPA2-PSK Encryption Settings
Pre-Shared Key (PSK) is available when using WPA or WPA2. This solution utilizes a shared key.
|
The shared passphrase users will enter when connecting with PSK- based authentication. |
|
|
The time period for which a Group Key is valid. The default value is 86400 seconds. Setting to low of a value can cause connection issues. |
WPA-EAP / WPA2-EAP Encryption Settings
Extensible Authentication Protocol (EAP) is available when using WPA or WPA2. This solution utilizes an external 802.1x/EAP capable RADIUS server for key generation.
|
RADIUS Server 1 Port |
The port on which your RADIUS authentication server communicates with clients and network devices. |
|
RADIUS Server 1 Secret |
|
|
The name/location of your backup RADIUS authentication server |
|
|
RADIUS Server 2 Port |
The port on which your backup RADIUS authentication server communicates with clients and network devices. |
|
RADIUS Server 2 Secret |
The secret passcode for your backup RADIUS authentication server |
|
The time period (in seconds) during which the WPA/WPA2 group key is enforced to be updated. |
Shared / Both (WEP) Encryption Settings
WEP is provided for use with legacy devices that do not support the newer WPA/WPA2 encryption methods. This solution utilizes a shared key.
|
Select the key to use for WEP connections to this VAP. WEP encryption keys are configured in the SonicPoint > SonicPoints page under SonicPoint Provisioning Profiles . |
Virtual Access Points
The VAP Settings feature allows for setup of general VAP settings. SSID and VLAN ID are configured through VAP Settings. Virtual Access Points are configured from the SonicPoint > Virtual Access Point page.
General VAP Settings
|
When using platforms that support VLAN, you may optionally select a VLAN ID to associate this VAP with. Settings for this VAP will be inherited from the VLAN you select. |
|
|
Enable Virtual Access Point |
|
|
Enable SSID Suppress |
Suppresses broadcasting of the SSID name and disables responses to
probe requests. Check this option if you do not wish for your SSID to be seen by |
Advanced VAP Settings
Advanced settings allows the administrator to configure authentication and encryption settings for this connection. Choose a Profile Name to inherit these settings from a user created profile. See “Virtual Access Points Profiles” section for complete authentication and encryption configuration information.
Virtual Access Point Groups
The Virtual Access Point Groups feature is available on SonicWALL NSA appliances. It allows for grouping of multiple VAP objects to be simultaneously applied to your SonicPoint(s). Virtual Access Point Groups are configured from the SonicPoint > Virtual Access Point page.
Sonic Point Provisioning Profiles
SonicPoint Provisioning Profiles provide a scalable and highly automated method of configuring and provisioning multiple SonicPoints across a Distributed Wireless Architecture. SonicPoint Profile definitions include all of the settings that can be configured on a SonicPoint, such as radio settings for the 2.4GHz and 5GHz radios, SSID’s, and channels of operation. For more information, see “SonicPoint Provisioning Profiles” .
Thinking Critically About VAPs
This section provides content to help determine what your VAP requirements are and how to apply these requirements to a useful VAP configuration. This section contains the following subsections:
Determining Your VAP Needs
When deciding how to configure your VAPs, begin by considering your communication needs, particularly:
|
|
|
Do my wireless client have the required hardware and drivers to support the chosen security settings? |
A Sample Network
The following is a sample VAP network configuration, describing four separate VAPs:
|
|
|
VAP #1, Corporate Wireless Users – A set of users who are commonly in the office, and to whom should be given full access to all network resources, providing that the connection is authenticated and secure. These users already belong to the network’s Directory Service, Microsoft Active Directory, which provides an EAP interface through IAS – Internet Authentication Services. |
|
|
|
VAP#2, Legacy Wireless Devices – A collection of older wireless devices, such as printers, PDAs and handheld devices, that are only capable of WEP encryption. |
|
|
|
VAP#3, Visiting Partners – Business partners, clients, and affiliated who frequently visit the office, and who need access to a limited set of trusted network resources, as well as the Internet. These users are not located in the company’s Directory Services. |
|
|
|
VAP# 4, Guest Users – Visiting clients to whom you wish to provide access only to untrusted (e.g. Internet) network resources. Some guest users will be provided a simple, temporary username and password for access. |
|
|
|
VAP#5, Frequent Guest Users – Same as Guest Users, however, these users will have more permanent guest accounts through a back-end database. |
Determining Security Configurations
Understanding these requirements, you can then define the zones (and interfaces) and VAPs that will provide wireless services to these users:
|
|
|
Corp Wireless – Highly trusted wireless zone. Employs WPA2-AUTO-EAP security. WiFiSec (WPA) Enforced. |
|
|
|
WEP & PSK – Moderate trust wireless zone. Comprises two virtual APs and subinterfaces, one for legacy WEP devices (e.g. wireless printers, older handheld devices) and one for visiting clients who will use WPA-PSK security. |
|
|
|
Guest Services – Using the internal Guest Services user database. |
|
|
|
LHM – Lightweight Hotspot Messaging enabled zone, configured to use external LHM authentication-back-end server. |
VAP Configuration Worksheet
The worksheet below provides some common VAP setup questions and solutions along with a space for you to record your own configurations.
|
How many different types of users will I need to support? |
Corporate wireless, guest access, visiting partners, wireless devices are all common user types, each requiring their own VAP |
Plan out the number of different VAPs needed. Configure a zone and VLAN for each VAP needed |
|
How many users will each VAP need to support? |
A corporate campus has 100 employees, all of whom have wireless capabilities |
The DHCP scope for the visitor zone is set to provide at least 100 addresses |
|
A corporate campus often has a few dozen wireless capable visitors |
The DHCP scope for the visitor zone is set to provide at least 25 addresses |
|
|
How do I want to secure different wireless users? |
A corporate user who has access to corporate LAN resources. |
|
|
A guest user who is restricted to only Internet access |
Enable Guest Services but configure no security settings |
|
|
Configure WEP and enable MAC address filtering |
||
|
What network resources do my users need to communicate with? |
A corporate user who needs access to the corporate LAN and all internal LAN resources, including other WLAN users. |
Enable Interface Trust on your
|
|
A wireless guest who needs to access InternetInternet and should not be allowed to communicate with other WLAN users. |
Disable Interface Trust on your
|
|
|
What security services to I wish to apply to my users? |
Corporate users who you want protected by the full SonicWALL security suite. |
Enable all SonicWALL security services. |
|
Guest users who you do not give a hoot about since they are not even on your LAN. |
Disable all SonicWALL security services. |
|
VAP Sample Configurations
This section provides configuration examples based on real-world wireless needs. This section contains the following subsections:
Configuring a VAP for Guest Access
You can use a Guest Access VAP for visiting clients to whom you wish to provide access only to untrusted (e.g. Internet) network resources. Guest users will be provided a simple, temporary username and password for access. More advanced configurations also offer more permanent guest accounts, verified through a back-end database.
This section contains the following subsection:
Configuring a Zone
In this section you will create and configure a new wireless zone with guest login capabilities.
|
|
In the left-hand menu, navigate to the Network > Zones page. |
|
|
Click the Add... button to add a new zone. |
General Settings Tab
|
|
In the General tab, enter a friendly name such as “VAP-Guest” in the Name field. |
|
|
Select Wireless from the Security Type drop-down menu. |
|
|
De-select the Allow Interface Trust checkbox to disallow communication between wireless guests. |
Wireless Settings Tab
|
|
In the Wireless tab, check the Only allow traffic generated by a SonicPoint checkbox. |
|
|
Select a provisioning profile from the SonicPoint Provisioning Profile drop-down menu (if applicable). |
Guest Services Tab
|
|
In the Guest Services tab, check the Enable Guest Services checkbox. |
|
|
|
In the following example, steps 2 through 7 are optional, they only represent a typical guest VAP configuration using guest services. Steps 2 and 7, however, are recommended. |
|
|
Check the Enable Dynamic Address Translation (DAT) checkbox to allow guest users full communication with addresses outside the local network. |
|
|
Check the Custom Authentication Page checkbox and click the Configure button to configure a custom header and footer for your guest login page. |
|
|
Click the OK button to save these changes. |
|
|
Check the Post Authentication Page checkbox and enter a URL to redirect wireless guests to after login. |
|
|
Check the Pass Networks checkbox to configure a website (such as your corporate site) that you wish to allow access to without logging in to guest services. |
|
|
Enter the maximum number of guests this VAP will support in the Max Guests field. |
|
|
Click the OK button to save these changes. |
Your new zone now appears at the bottom of the Network > Zones page, although you may notice it is not yet linked to a Member Interface. This is your next step.
Creating a Wireless LAN (WLAN) Interface
In this section you will configure one of your ports to act as a WLAN. If you already have a WLAN configured, skip to the “Creating a Wireless LAN (WLAN) Interface” section .
|
|
In the
Network > Interfaces
page, click the Configure
 icon corresponding to the interface you wish to use as a WLAN. The Interface Settings screen displays.
|
|
|
Select WLAN from the Zone drop-down list. |
|
|
Enter the desired IP Address for this interface. |
|
|
In the SonicPoint Limit drop-down menu, select a limit for the number of SonicPoints. This defines the total number of SonicPoints your WLAN interface will support. |
|
|
|
The maximum number of SonicPoints depends on your platform. Refer to the “Custom VLAN Settings” section to view the maximum number of SonicPoints for your platform. |
|
|
Click the OK button to save changes to this interface. |
Your WLAN interface now appears in the Interface Settings list.
Creating a VLAN Subinterface on the WLAN
In this section you will create and configure a new VLAN subinterface on your current WLAN. This VLAN will be linked to the zone you created in the “Configuring a Zone” section .
|
|
In the
Network > Interfaces
page, click the Add Interface
 button.
|
|
|
In the Zone drop-down menu, select the zone you created in “Configuring a Zone ” . In this case, we have chosen VAP-Guest . |
|
|
Enter a VLAN Tag for this interface. This number allows the SonicPoint(s) to identify which traffic belongs to the “VAP-Guest” VLAN. You should choose a number based on an organized scheme. In this case, we choose 200 as our tag for the VAP-Guest VLAN. |
|
|
In the Parent Interface drop-down menu, select the interface that your SonicPoint(s) are physically connected to. In this case, we are using X2 , which is our WLAN interface. |
|
|
Enter the desired IP Address for this subinterface. |
|
|
Select a limit for the number of SonicPoints from the SonicPoint Limit drop-down menu. This defines the total number of SonicPoints your VLAN will support. |
|
|
Optionally, you may add a comment about this subinterface in the Comment field. |
|
|
Click the OK button to add this subinterface. |
Your VLAN subinterface now appears in the Interface Settings list.
Configuring DHCP IP Ranges
Because the number of available DHCP leases vary based on your platform, the DHCP scope should be resized as each interface/subinterface is defined to ensure that adequate DHCP space remains for all subsequently defined interfaces. To view the maximum number of DHCP leases for your SonicWALL security appliance, refer to the “DHCP Server Scope” section .
|
|
In the left-hand menu, navigate to the Network > DHCP Server page. |
|
|
Locate the interface you just created, in our case this is the X2:V200 (virtual interface 200 on
the physical X2 interface) interface. Click the Configure
 icon corresponding to the desired interface.
|
|
|
|
If the interface you created does not appear on the Network > DHCP Server page, it is possible that you have already exceeded the number of allowed DHCP leases for your SonicWALL. For more information on DHCP lease exhaustion, refer to the “DHCP Server Scope” section . |
|
|
Edit the Range Start and Range End fields to meet your deployment needs |
|
|
Click the OK button to save these changes. |
Your new DHCP lease scope now appears in the DHCP Server Lease Scopes list.