Wireless: SonicPoint Layer 3 Management using GRE Tunnel with DHCP addressing method

03/26/2020 29 People found this article helpful 485,943 Views

Description

This article covers how to configure SonicPoint-N Layer 3 management using GRE tunneling with DHCP addressing method.

Resolution

Applies to:

Firmware/Software Version: 5.9 and above
Services: SonicPoint Layer 3 Management

Overview:

- With SonicOS 5.9 firmware the SonicWall UTM appliances are capable of discovering and managing SonicPoint-N devices which are behind a layer 3 network device.
- SonicPoint-Ns will use the DHCP option 138 (Access controller option) for discovery.
- GRE / DTLS (phase II) tunnel is established between the SonicWall UTM appliance and the SonicPoint-N device(s) to carry management and data traffic.

Scenario:

Discovering and managing SonicPoint-Ns using the GRE Tunneling with DHCP addressing method.
Note:
The configuration illustrated below is based on the above network diagram. You must modify the settings to match with your deployment in your environment

Deployment Steps:

Part 1: Configuration on the SonicWall UTM appliance

Step 1: Create WLAN Tunnel Interface
Step 2: Create DHCP Scope with DHCP Option 138 (Sonic WALL CAPWAP)
Step 3: Route Policy to access SonicPoint-Ns behind L3 network device (30.30.30.x)

Part 2: configuration on the Intermediate Router to perform DHCP Relay/IPHelper
Part3: Configuration on the SonicPointNs

Step 1: Downloading the SonicOS 5.9 compatible firmware for SonicPont-Ns
Step 2: Accessing the SonicPoint-N Management Interface in Standalone Mode
Step 3: Uploading the SonicOS 5.9 compatible firmware for SonicPont-Ns
Step 4: Configuring the L3 Management Settings - Manually (optional Step)

Detailed configuration steps:

Part 1: Configuration on the SonicWall UTM appliance

Step 1: Configuration – WLAN Tunnel Interface

Login to the SonicWall Management Interface and go to Network > Interfaces page
Select WLAN tunnel interface in the Add Interface drop down menu and configure as per your setup

Zone: WLAN
Tunnel ID: 0 (zero)
Tunnel Source Interface: X4 (AC Interface) (This is the interface through the routed network where the SonicPoint is reached)
Mode / IP Assignment: Static
IP Address: 172.16.35.1
Subnet Mask: 255.255.255.0

Please Note: A DHCP scope (172.17.35.1/24) will be automatically created in the Network | DHCP Server page for the wireless clients.
(Sonicpoint and its clients would be leased an ip from this virtual subnet within the GRE tunnel)
Step 2: Create DHCP Scope with DHCP Option 138 (Sonic WALL CAPWAP)

Go to Network | DHCP Server page, ensure that the “Enable DHCPv4 Server” option is checked/enabled.
Click on the Advanced button

In the Option Objects tab, click on Add Options button; enter the details as per your setup.

Option Name: Enter a Name of your choice
Option Number: Select “138 (CAPWAP AC IPv4 Address List)
Option Type: IP Address (will be greyed out)
Option Value: Enter “10.10.10.1” [This is the IP of the interface to which the WT0 interface is bound to (X4 interface ip) ]
Click OK when Done

The DHCP scope for the routed physical network (30.30.30.0/24) can be configured either on the UTM (or) on the intermediate router . If SonicWall is configured as the DHCP server for the routed network , you may configure the router to Forward DHCP Protocol (DHCP Relay/IP Helper) from the SonicPoint-Ns to the SonicWall UTM Appliance.

The below configuration assumes that the UTM is the DHCP server for the routed network (network behind the router)

On the DHCP Server page, click on the Add Dynamic button to Create a DHCP Scope for the SonicPoint-N devices, binding with the new DHCP AC option to the scope.

Range Start: 30.30.30.100
Range End: 30.30.30.200
Default Gateway: 30.30.30.1
Subnet Mask: 255.255.255.0

Step 3: Route Policy to access SonicPoint-Ns behind network device (30.30.30.x)

Please Note: If you have already created a similar Route Policy you may skip this section

Go to Network | Routing page and click on Add button, configure as follows:
When the Sonicpoint gets an IP leased out from the above scope , it will establish a GRE tunnel to the AC IP address (which it gets from the DHCP option 138 as part of the lease)

Part 2: Configuration the Intermediate Router to perform DHCP Relay/IPHelper

Method 1: You may configure the router to Forward DHCP Protocol (DHCP Relay/IP Helper) from the SonicPoint-Ns to the SonicWall UTM Appliance. The DHCP Relay policy should forward the DHCP Protocol (DORA Process) from 30.30.30.0 Network to the SonicWall's X4 Interface IP 10.10.10.1.

Protocol: DHCP
From: 30.30.30.0/24
To: 10.10.10.1

Method 2: If the Router does not have the DHCP Relay option or if you do not have access to it, you may setup your SoincPoint-N in SafeMode and configure the settings manually.

In the Part 3 section below - please follow the Steps 1,2,3 and Step 4 (Configuring the L3 Management Settings Manually (Optional Step))

Part 3: Configuration on the SonicPointNs

Step 1: Downloading the SonicOS 5.9 compatible firmware for SoincPont-Ns

Method 1: Connecting SonicPoint-Ns to SonicWall UTM appliance running SonicOS 5.9 and above

When the SonicPoint-Ns are connected to a SonicWall UTM appliance’s WLAN interface/Zone running SonicOS 5.9 and above, the SonicPoint-Ns will be automatically updated with the latest firmware.

Method 2: Manually updating the SonicPoint-Ns firmware

Download the TSR from a SonicWall UTM appliance running 5.9 or above

Open the TSR in a Text reader/editor and find the SonicPoint-Ns download URL

Copy-Paste the Download URL in a Web Browser and download the appropriate SonicPoint-N Image

Step 2: Accessing the SonicPoint-N Management Interface in Standalone Mode:

The default management interface of the SonicPoint is 192.168.1.20

If you are connecting to the LAN port on the SonicPoint directly from a PC or through only the PoE injector, you need to configure the Local Area Connection on the PC to be in the same subnet as the SonicPoint.

IP address: 192.168.1.100.
Netmask: 255.255.255.0.

Connect directly to the LAN port of the SonicPoint with a crossover cable or regular cat. 5 Ethernet cable.

Connect to the LAN port of the SonicPoint through the PoE injector with a regular cat. 5 Ethernet cable.

Start your Web browser and direct it to the default management IP address for the SonicPoint, 192.168.1.20

Troubleshooting Tip:If you are unable to access the SonicPoint-N you may press the Reset Button on the SonicPoint-Ns to access it in SafeMode and then follow the above steps again:
Step 3: Uploading the SonicOS 5.9 compatible firmware for SonicPont-Ns
Please Note: During the reboot the SonicPoint-N will initiate the DHCP Process (DORA) and the Router should perform DHCP Relay to SonicWall Appliance for SonicPoint-N to successfully get the DHCP IP with DHCP Option 138. Then SonicPoint-N will initiate CAPWAP and GRE/DTLS process to IP received via DHCP option 138 to complete the SonicPoint provisioning.

Caution: If you have already configured the Router to perform DHCP Relay please skipthis section.

Step 4: Configuring the L3 Management Settings - Manually (optional Step)

If you do not have access to the Router to perform the DHCP Relay you may following the below steps to configure the L3 management settings manually on the SonicPoint-N device.

Navigate to SonicPoint-Ns Network | Interfaces page
Under L3 Management settings, enable the option/check “Enable AC IP configuration”.
Enter the AC IP as: 10.10.10.1 (X4 Interface IP of SonicWall UTM Appliance)
Enable the Disable local DHCP Client option.

Enter Local IP address: 30.30.30.100
Subnet Mask: 255.255.255.0
Default Gateway: 30.30.30.1 (Router's IP address)

Click on Accept button on top.
You will get a prompt at the bottom to Restart the SonicPoint-N, click on the link and restart the SonicPoint-N appliance.

Please Note:After the reboot the SonicPoint-N will try to establish GRE/DTLS tunnel with CAPWAP settings to the IP address mentioned in the AC IP field to complete the SonicPoint provisioning.