killokr.blogg.se

1. #SONICWALL SSL VPN CLIENT SETUP USING 2ND PUBLIC IP HOW TO#
2. #SONICWALL SSL VPN CLIENT SETUP USING 2ND PUBLIC IP DOWNLOAD#

Later on as we configure users, you can specify specific routes for individual users.įinally, in SonicOS 5.9.0.0 you need to go to the Client Settings tab to setup your WINS, DNS, etc… for the client to use. Note that these routes are the superset of the routes that you want people to be able to connect to. In the example to the right, you see that I have added a list of routes for the clients to use through the NetExtender client when they connect. In SonicOS 5.8.1.13, this is defined in SSL VPN / Client Routes. On the Client routes tab you need to choose from the address objects defined in Network / Address Objects which ones you want to allow the clients to connect to. This is different than the 5.8.1.13 SonicOS and therefore, give you more flexibility as it doesn’t have to draw addresses from a current network that you have assigned to an interface. To the right is how I defined my SSLVPN DHCP pool Network Object on my 5.9 SonicOS. In SonicOS 5.8.1.13, one configures the whole DHCP setup completely in this area by setting the interface where the addresses are routed that you want to use–like X0 for example, Then setup the range using the start ip and end ip and then all of the other network stuff that you would normally expect such as WINS if needed, DNS, etc… You would then to to SSL VPN / Client Routes to set that up like we will describe later for 5.9.Ĭreate Your SSLVPN DHCP POOL Address Object This is where things are a bit different between 5.8 and 5.9. Next, we go into SSL VPN / Client Settings. This has been good for me because sometimes there are specific versions of the NetExtender client that I want my clients using due to bugs or other.

#SONICWALL SSL VPN CLIENT SETUP USING 2ND PUBLIC IP DOWNLOAD#

Setup the Radius settings if you use Radius.The Inactivity Timeout will disconnect clients if they are inactive longer than this time period.If you need to manage this SonicWall over this VPN directly you will want to Enable Web Management and likewise if you use SSH for SonicWall management, turn that on too.The only thing that this matches to is the domain name that they will need to enter on the NetExtender client side. Tell it the domain that you want to use.If you need to use a signed certificate go to system / certificates and manage that there.I also turn on LAN so that I can test it internally.

No reason to have a VPN setup if you can’t connect to it from the WAN. Be certain that the WAN interface is clicked so that it is green.Login and browse to the SSL VPN / Server Settings page. Create your users and give them proper access to the right devices on your network.There are 3 basic tasks to create a SonicWall SSLVPN. You will see just between these two releases (5.8.1.13 and 5.9.0.0) there are a few differences. And since verions 5.8.1.13 is recent in my memory, I have notes for that version here too. So, while they are all similar, this tutorial was done using a SonicWall NSA 3500 running SonicOS Enhanced 5.9.0.0-91o. Each one is somewhat different as the SonicOS changes and the steps and location of items changes from release to release.

#SONICWALL SSL VPN CLIENT SETUP USING 2ND PUBLIC IP HOW TO#

There are several great tutorials out there on how to setup a SonicWall SSLVPN.