• SonicOS 7
• Zones
  • How Zones Work
  • Predefined Zones
  • Security Types
  • Allow Interface Trust
  • Enabling SonicWall Security Services on Zones
  • Effect of Wireless and Non-Wireless Controller Modes
    • Effects of Enabling Non-Wireless Controller Mode
    • Effects of Enabling Wireless Controller Mode
  • Match Objects > Zones
    • The Zone Settings Table
    • Adding a New Zone
    • Configuring a Zone for Guest Access
    • Configuring a Zone for Open Authentication and Social Login
    • Configuring a Zone for Captive Portal Authentication with RADIUS
    • Configuring a Zone for Customized Policy Message
    • Configuring a Zone for Customized Login Page
    • Configuring the WLAN Zone
    • Configuring the RADIUS Server
    • Configuring DPI-SSL Granular Control per Zone
    • Enabling Automatic Redirection to the User-Policy Page
    • Deleting a Zone
• Addresses
  • Types of Address Objects
  • About Address Groups
  • About UUIDs for Address Objects and Groups
  • Addresses Page
    • Common Features
      • Common Functions
      • Common Column Headings
    • Sorting the Entries
  • Default Address Objects and Groups
  • Default Pref64 Address Object
  • Default Rogue Address Groups
  • Adding an Address Object
  • Editing Address Objects
  • Deleting Custom Address Objects
  • Purging MAC or FQDN Address Objects
  • Creating Address Groups
  • Editing Address Groups
  • Deleting Address Groups
  • Working with Dynamic Address Objects
    • Key Features of Dynamic Address Objects
    • Enforcing the Use of Sanctioned Servers on the Network
    • Using MAC and FQDN Dynamic Address Objects
      • Blocking All Protocol Access to a Domain using FQDN DAOs
      • Using an Internal DNS Server for FQDN-based Access Rules
      • Controlling a Dynamic Host’s Network Access by MAC Address
      • Bandwidth Managing Access to an Entire Domain
• Services
  • About Default Service Objects and Groups
  • Predefined IP Protocols for Custom Service Objects
  • Adding Service Objects using Predefined Protocols
  • Adding Custom IP Type Services
    • Configuration Example
  • Editing Custom Service Objects
  • Deleting Custom Service Objects
  • Adding Custom Service Groups
  • Editing Custom Service Groups
  • Deleting Custom Service Groups
• URI Lists
  • About URIs and the URI List
  • About URI List Groups
  • About Keywords and the Keyword List
  • Matching URI List Objects
  • Using URI List Objects
  • Managing URI List Objects
    • About the URI List Objects Table
    • Configuring URI List Objects
    • Exporting a URI List Object
    • Editing a URI List Object
    • Deleting URI List Objects
  • Managing URI List Groups
    • About the URI List Groups Table
    • Adding URI List Groups
    • Editing a URI List Group
    • Deleting URI List Groups
• Match Objects
  • About Match Objects
    • About Regular Expressions
      • Regular Expression Syntax
    • About Negative Matching
  • About Application List Objects
    • About Application Filters
    • About Category Filters
  • Configuring a Match Object
  • Configuring Application List Objects
• Schedules
  • Adding a Custom Schedule
  • Modifying Schedules
  • Deleting Custom Schedules
• Dynamic Group
  • About the Dynamic External Address Group File
  • DEAG and DEAO Maximums
  • High Availability Requirements
  • Adding a Dynamic External Object
  • Editing Dynamic External Objects
  • Deleting Dynamic External Objects
• Email Addresses
  • Configuring Email Address Objects
• SonicWall Support
  • About This Document

Configuration Example

Assume an administrator needs to allow RSVP (Resource Reservation Protocol - IP Type 46) and SRP (Spectralink™ Radio Protocol – IP type 119) from all clients on the WLAN zone (WLAN Subnets) to a server on the LAN zone (for example, 10.50.165.26). You can define custom IP type service objects to handle these two services.

To define a custom IP type service and related configuration:

1. Navigate to Object > Match Objects > Services > Service Objects page.

2. Click the Add button. The Service Objects dialog displays.

   

3. Enter a descriptive name for the service object in the Name field.

4. Select Custom IP type from the Protocol drop-down menu.

   

5. In the field to the right of the Protocol drop-down list, type in the protocol number for the Custom IP Type.

   The Port Range and Sub Type fields are not definable or applicable to a Custom IP Type.

   Attempts to define a custom protocol type service object for a predefined IP type is not permitted and results in an error message.

6. Click Save.
7. Repeat Step 3 through Step 6 for each custom service to be defined.
8. Navigate to Object > Match Objects > Services > Service Groups page.

9. Click the Add button. The Service Groups dialog displays.

   

10. Enter a descriptive name for the service group in the Name field, such as myServices.

11. Select the custom service objects you just created from the list on the left, and then click the Right Arrow button to move them into the list on the right.

    Press Ctrl or Shift to select multiple service objects, and then click the Right Arrow button to move them all at one time.

12. Click Save.
13. Navigate to Object > Match Objects > Services > Service Objects page.
14. Click the Add button. The Service Objects dialog displays.
15. Create an address object for the host that the WLAN Subnets can access using myServices.

16. Select the custom service objects you just created from the list on the left, and then click the Right Arrow button to move them into the list on the right.

    Press Ctrl or Shift to select multiple service objects, and then click the Right Arrow button to move them all at one time.

17. Click Save.
18. Navigate to Policy > Rules and Policies > Access Rules page to create a WLAN > LAN rule.

19. Define an access rule allowing myServices from WLAN Subnets to the 10.50.165.26 address object.

    It may be necessary to create an access rule for bidirectional traffic; for example, an additional access rule from the LAN > WLAN allowing myServices from 10.50.165.26 to WLAN Subnets.

20. Click Save.

    IP protocol 46 and 119 traffic will now be recognized and allowed to pass from WLAN Subnets to the host at 10.50.165.26.