Global VPN Client IP Assignment Using The Sonicwall Appliance

AID: 4160
  • Status: Published

10150 points

  • Bydigitap
  • TypeTutorial
  • Posted on2010-11-25 at 11:00:14
Awards
  • Community Pick
  • Experts Exchange Approved
This article will step through configuring a SonicWALL appliance to utilize an internal DHCP server for Global VPN Client (GVC) hosts.  There are times when using an external (external to the SonicWALL) DHCP server, such as Windows Servers, isn’t practical for one reason or another.

This article assumes the WAN GlobalVPN VPN policy has already been configured and is functioning.  Additionally, this article is in two parts:

Part One will use an already configured WLAN zone for assigning IP addresses to GVC hosts.
Part Two will walk through setting up the WLAN zone if not already configured.


Part One – Setup DHCP for GVC Hosts Utilizing The WLAN Zone


NOTE: It is assumed that WLAN already has access to LAN and LAN to WLAN.

What you’ll need to know:
- The IP address assigned to the interface the WLAN zone is assigned to.

1. Login to the SonicWALL appliance and go to VPN > DHCP over VPN.

2. Confirm Central Gateway is selected in the drop down and click Configure (See Image 1 Below).



3. Check the following boxes:
    - Use Internal DHCP Server
    - For Global VPN Client

4. In the Relay IP Address text box, type the IP address assigned to the interface the WLAN zone is assigned to.  See Image 2 below for the final settings.  Once the settings are completed, click OK.



5. Once completed, establish a VPN connection and confirm the IP address is assigned from the DHCP scope assigned to the WLAN zone.


Part Two: Setting Up DHCP For GVC Hosts When WLAN Hasn’t Been Configured

What you’ll need:
- Identify a IP subnet that isn’t currently being utilized on the internal network.
- An available interface on the SonicWALL

1. Click Network > Interface and edit an available Interface that isn’t being utilized for another purpose.  For this article, I have selected the X3 interface.

2. Select the WLAN zone in the Zone drop down (See Image 3 Below).



3. Give the interface an IP address.  For this article, I have chosen 10.10.10.20 (See Image 4 Below).



4. Click OK.  You’ll get a prompt regarding the management interface.  Disregard this message as the management interface is configured on the LAN interface.

5. Click Network > DHCP Server.  Once the WLAN zone settings are saved to the Interface, the SonicWALL appliance automatically created a new DHCP scope specifically for hosts connected to the X3 interface (or, whichever Interface was chosen).

6. Edit the new DHCP scope and modify the Start and End IP range if the default is not acceptable.

7. Click the DNS/WINS tab.  If you desire your GVC hosts to resolve hosts on the LAN network, you’ll need to enter the Active Directory domain (if utilized) and internal DNS servers.  Also, if you have any WINS servers, you’ll need to enter those here too.

8. Once configured, click OK.

9. Click VPN > VPN Over DHCP.

10. Confirm Central Gateway is selected in the drop down and click Configure (See Image 1 Below).



11. Check the following boxes:

    - Use Internal DHCP Server
    - For Global VPN Client

12. In the Relay IP Address text box, type the IP address assigned to the interface the WLAN zone is assigned to.  See  Image 2 below for the final settings.  Once the settings are completed, click OK.



13. Now, we need to confirm Firewall Access between the WLAN <-> LAN zones.  Click Firewall > Access Rules (See Image 5 Below).



14. The default View Style is Matrix.  Click the WLAN > LAN matrix intersection to see the rules affecting this traffic.

15. See the screen shot below to see the default rule.  The rule in my screen shot is Allow, but the default MAY be Deny.  Click Edit to bring up the particulars of the Access Rule.  In the Action section, click the Allow radio button and click OK (See Image 6 Below).



16. Click the LAN > WLAN matrix intersection to confirm the default rule is configured to allow traffic.  Use the procedure in Step 15 to change this to allow.  Otherwise, proceed to the next step.

17. Now, establish a VPN connection and confirm the IP address is assigned from the DHCP scope assigned to the WLAN zone.
Asked On
2010-11-25 at 11:00:14ID4160
Tags

sonicwall

,

gvc

,

DHCP

,

WLAN

Topic

Networking Hardware

Views
5586

Comments

Expert Comment

by: IT-Monkey-Dave on 2012-02-02 at 11:46:36ID: 41626

This article is exactly what I'm trying to do.  The Global VPN Client test system establishes a VPN link successfully.  It gets to "Acquiring IP Address" and then nothing.  The firewall shows that the link is up, and an IP has been assigned from the correct DHCP scope (I happen to be using Interface X5 for WLAN).  But the client never receives the IP address.  I've been messing with this all morning and can't figure it out.

Anyone have any ideas why the allocated IP isn't reaching the VPN client?

Author Comment

by: digitap on 2012-02-02 at 12:01:51ID: 41629

What does the log of the GVC say?

Expert Comment

by: IT-Monkey-Dave on 2012-02-02 at 12:06:41ID: 41630

Everything in the GVC client log looks good up to the point "Renewing IP address for the virtual interface [MAC address]".  It sits there and eventually times out with "Failed to renew the IP address for the virtual interface".  While that timeout is going on, the firewall shows the VPN link is up and traffic is moving in both directions.  An IP has been allocated from the correct scope for the WLAN interface.  But the client never seems to receive it.

Author Comment

by: digitap on 2012-02-02 at 12:23:21ID: 41633

Hmmm. I'd probably want to see some screen shots of the configuration as you have it, but that's hard to do here and should be in a question.

Are the subnets between the two different? Is the local subnet different than the subnet being assigned by the X5 DHCP scope on the Sonicwall?

Expert Comment

by: IT-Monkey-Dave on 2012-02-02 at 12:33:22ID: 41635

The LAN subnet is good old 192.168.0.0/24.  I can honestly blame a previous admin for that.

The fabricated X5 subnet is 10.0.69.0/24.  The X5 Interface is 10.0.69.1.  DHCP Scope for that is 10.0.69.10 thru .99.

If I change the "DHCP over VPN" properties so the client obtains an IP from our LAN DHCP server, everything is fine.  But the whole point of this exercise is to get the VPN clients off the pesky 192.168.0.0 subnet.

Perhaps interestingly, I have a different DHCP scope for L2TP Pool.  If the client connects from some standard L2TP VPN client, it works fine.

I may have to post this as a new question...  It seems like I'm very close to getting this to work but some small detail isn't right yet.

Author Comment

by: digitap on 2012-02-02 at 13:32:42ID: 41638

Let me know if you do. I've been on a EE vacation as I've had some life changes, new baby, that has left me too busy for EE. I don't get updates on new questions at the moment.

Add your Comment

Please Sign up or Log in to comment on this article.

Join Experts Exchange Today

Gain Access to all our Tech Resources

Get personalized answers

Ask unlimited questions

Access Proven Solutions

Search 3.2 million solutions

Read In-Depth How-To Guides

1000+ articles, demos, & tips

Watch Step by Step Tutorials

Learn direct from top tech pros

And Much More!

Your complete tech resource

See Plans and Pricing

30-day free trial. Register in 60 seconds.

Loading Advertisement...

Top Networking Hardware Experts

  1. Darr247

    48,114

    1,500 points yesterday

    Profile
    Rank: Genius
  2. craigbeck

    34,951

    0 points yesterday

    Profile
    Rank: Sage
  3. TimotiSt

    33,498

    0 points yesterday

    Profile
    Rank: Master
  4. giltjr

    31,195

    0 points yesterday

    Profile
    Rank: Genius
  5. mat1458

    25,731

    0 points yesterday

    Profile
    Rank: Master
  6. nazsky

    24,298

    0 points yesterday

    Profile
    Rank: Wizard
  7. erniebeek

    23,582

    0 points yesterday

    Profile
    Rank: Genius
  8. Mysidia

    23,136

    0 points yesterday

    Profile
    Rank: Sage
  9. donjohnston

    22,743

    400 points yesterday

    Profile
    Rank: Genius
  10. hanccocka

    18,468

    0 points yesterday

    Profile
    Rank: Genius
  11. ikalmar

    17,948

    0 points yesterday

    Profile
    Rank: Genius
  12. Netty

    17,574

    0 points yesterday

    Profile
    Rank: Guru
  13. rigan123

    15,527

    0 points yesterday

    Profile
    Rank: Guru
  14. eeRoot

    15,448

    0 points yesterday

    Profile
    Rank: Wizard
  15. andyalder

    15,320

    0 points yesterday

    Profile
    Rank: Genius
  16. dpk_wal

    15,100

    0 points yesterday

    Profile
    Rank: Genius
  17. lrmoore

    13,688

    0 points yesterday

    Profile
    Rank: Savant
  18. Soulja

    13,404

    0 points yesterday

    Profile
    Rank: Genius
  19. thinkpads_user

    12,572

    0 points yesterday

    Profile
    Rank: Genius
  20. harbor235

    12,348

    0 points yesterday

    Profile
    Rank: Genius
  21. fmarshall

    11,851

    0 points yesterday

    Profile
    Rank: Wizard
  22. Rick_O_Shay

    11,764

    0 points yesterday

    Profile
    Rank: Sage
  23. kevinhsieh

    11,100

    0 points yesterday

    Profile
    Rank: Genius
  24. digitap

    10,000

    0 points yesterday

    Profile
    Rank: Genius
  25. danieldias

    9,900

    1,500 points yesterday

    Profile
    Rank: Master

Hall Of Fame