Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 902
  • Last Modified:

A problem to properly connect openSWAN to Sonicwall VPN server

The question is related to this one.

Our office has the SonicWall TZ 170 hardware firewall/VPN server.
My home machine is Debian GNU/Linux v7. I use the OpenSWAN package to connect to the VPN.

The problem is as follows:
I have to switch the VPN policy "Allow connection to" on the VPN server to "All Secured Gateways" in order to make my Linux box get connected. But that's not good, because all other Windows-based clients VPN claim they have access only to the office network, the internet connection is forbidden for them during their VPN session (The "Allow connection to" should be "Split Tunnels" to let them access the internet during a VPN session).
If I connect when the "Split Tunnels" is set then no error is given, but no office's node is reachable.

I tried also to check the "Set Default Route as this Gateway" and specified the address in the "Default LAN Gateway" (on the advanced tab of the TZ170's VPN policy page) to at least make the internet access via the VPN tunnel, but in this case I can not connect at all.

Attached is the screenshot of the VPN policy editor, ipsec.conf file, the log what I see on a successful connection, and the log on "Split Tunnels" (no differences though)

This how I establish the connection:
ipsec setup --start
sleep 8
ipsec whack --listen
sleep 8
ipsec whack --name sonicwall --initiate

Open in new window


This is a help page for the server's VPN policy:
http://help.mysonicwall.com/sw/eng/705/ui2/23100/VPN/VPN_Policy_GroupVPN_IKE_Preshared_Secret.htm
vpn1.png
ipsec.conf.txt
good.log
bad.log
0
zc2
Asked:
zc2
1 Solution
 
zc2Author Commented:
Found a good guide:
http://www.golinuxhub.com/2012/10/openswan-configuration-on-red-hat-5-for.html

Following the guide made the VPN work.

The key changes:
1) /proc/sys/net/ipv4/ip_forward has to contain 1  (configured in the /etc/sysctl.conf)
2) regenerated the site private key by executing
ipsec newhostkey --output /etc/ipsec.secrets --bits 2048 --verbose
(with restoring the @GroupVPN @xxxxxxxxxxx : PSK "Pre Shared Key" string)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Building an Effective Phishing Protection Program

Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now