Number Of Subnets Supported; Wireless Zones: The Wlan Zone - SonicWALL SonicPoint Administrator's Manual

As part of the provisioning process, the security appliance will store the configuration for that
SonicPoint, and will push the configuration to the SonicPoint using SSPP (SonicWALL Simple
Provisioning Protocol). Upon receiving the configuration, the SonicPoint will update its configuration,
will reboot to affect the changes, and will enter an operational state. While still peered with the same
security appliance, changes to that SonicPoint's configuration will only be possible using the SonicOS
GUI, and must be performed at the unit (as opposed to the Profile) level.
While in Managed Mode, the SonicPoint will report its state to the security appliance using SDP
packets. A full description of SonicPoint state information can be found in the 'SonicPoint States'
section of this document. Also included in the SDP packets sent by operational SonicPoint devices is
a checksum value for its configuration. If the security appliance determines from the checksum that
there is a disagreement between its configuration checksum for that SonicPoint and that SonicPoint's
advertised checksum, it will engage an encrypted SSPP channel with that SonicPoint, and will send it
the proper configuration. The SonicPoint will then reboot to assume the corrected configuration.
It is important to note that changing a SonicPoint Profile on the security appliance will not update
operational SonicPoint units. This is by design, so as to allow Profiles to be added, deleted, and
modified with interrupting network operation. SonicPoint Profiles will only affect an unprovisioned
SonicPoint device, that is, a SonicPoint for which security appliance has no stored configuration.
Changing the configuration on an operational SonicPoint requires modification to that SonicPoint's
settings (under Wireless > SonicPoints > SonicPoint Settings). Alternatively, it is possible to delete
the SonicPoint peering from the SonicOS GUI, thus forcing a new auto-provisioning process using the
appropriate SonicPoint Profile.

Number of Subnets Supported

The following table indicates the size of a subnet allowed depending on the number of SonicPoint
devices available.
SonicPoints per
Interface
No SonicPoints
2 SonicPoints
4 SonicPoints
8 SonicPoints
16 SonicPoints
32 SonicPoints

Wireless Zones: The WLAN Zone

The Wireless Zone type has been added to existing Zone types (Trusted, Untrusted, Public,
Encrypted, Multicast) to provide support to SonicPoint Access Points. The default Wireless Zone
instance will be the "WLAN Zone."
Interfaces assigned to a Wireless Zone will have the following important and unique characteristics:
• SonicPoint Enforcement: As traffic passes from wireless clients through a SonicPoint, the
SonicPoint will tag the traffic so that it will be identifiable by a Wireless Zone interface. If the
Wireless Zone interface receives traffic that has not been appropriately tagged, it will discard the
traffic.
• Wireless Firewalling: The next-generation of the Inter-client Communications. The ability to apply
firewall Access Rules and Security Services to all wireless client traffic, even client-to-client traffic
through a single or multiple SonicPoints.
S WALL S P
ONIC ONIC OINT
Maximum Subnet Mask
30 bits - 255.255.255.252
29 bits - 255.255.255.248
29 bits - 255.255.255.248
28 bits - 255.255.255.240
27 bits - 255.255.255.224
26 bits - 255.255.255.192
A ' G
DMINISTRATOR S UIDE
SonicPoint Overview
Total Usable Available Client IP
IP Addresses Addresses
2 2
6 3
6 1
14 5
30 13
62 29
11