Koozali.org: home of the SME Server

openvpn, client unable to connect

valdis

openvpn, client unable to connect
« on: June 29, 2006, 05:52:57 AM »
Arvo to all, would appreciate help with openvpn.
I am all read out, it seems some follow the instrctions and no problems, others just problems, luck me, problems, but then a newie and trying to convince the powers linux & open source

esmith 6.5
swerts how-to on oenvpn

modem (bridged)-->esmith---->squid RH proxy--->network
210.xxx.xxx.xx       eth1
                              10.0.0.50   10.0.0.1
                                              192.168.xxx.xxx    192.168.xxx.xxx
config file

##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server.     #
#                                            #
# This configuration can be used by multiple #
# clients, however each client should have   #
# its own cert and key files.                #
#                                            #
# On Windows, you might want to rename this  #
# file so it has a .ovpn extension           #
##############################################

# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client

# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
dev tap
;dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one.  On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap


# Are we connecting to a TCP or
# UDP server?  Use the same setting as
# on the server.
;proto tcp
proto udp

# VK added
--log vkopen.log
 # vk added

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote 210.xx.xxx.xxx 1194
;remote my-server-2 1194

# Choose a random host from the remote
# list for load-balancing.  Otherwise
# try hosts in the order specified.
;remote-random

# Keep trying indefinitely to resolve the
# host name of the OpenVPN server.  Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite

# Most clients don't need to bind to
# a specific local port number.
nobind

# Downgrade privileges after initialization (non-Windows only)
;user nobody
;group nobody

# Try to preserve some state across restarts.
persist-key
persist-tun

# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here.  See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]
;http-proxy 192.168.177.1 3128

# Wireless networks often produce a lot
# of duplicate packets.  Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings

# SSL/TLS parms.
# See the server config file for more
# description.  It's best to use
# a separate .crt/.key file pair
# for each client.  A single ca
# file can be used for all clients.
ca ca.crt
cert client.crt
key client.key

# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server".  This is an
# important precaution to protect against
# a potential attack discussed here:
#  http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the nsCertType
# field set to "server".  The build-key-server
# script in the easy-rsa folder will do this.
ns-cert-type server

# If a tls-auth key is used on the server
# then every client must also have the key.
;tls-auth ta.key 1

# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
;cipher x

# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo

# Set log file verbosity.
verb 3

# Silence repeating messages
;mute 20



log from the client

Thu Jun 29 13:33:11 2006 OpenVPN 2.0.7 Win32-MinGW [SSL] [LZO] built on Apr 12 2006
Thu Jun 29 13:33:11 2006 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Thu Jun 29 13:33:11 2006 LZO compression initialized
Thu Jun 29 13:33:11 2006 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Thu Jun 29 13:33:11 2006 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Thu Jun 29 13:33:11 2006 Local Options hash (VER=V4): 'd79ca330'
Thu Jun 29 13:33:11 2006 Expected Remote Options hash (VER=V4): 'f7df56b8'
Thu Jun 29 13:33:11 2006 UDPv4 link local: [undef]
Thu Jun 29 13:33:11 2006 UDPv4 link remote: 210.23.137.192:1194
Thu Jun 29 13:33:11 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:14 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:16 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:19 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:21 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:24 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:26 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:28 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:29 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:31 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:33 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:36 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:38 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:41 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:43 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:46 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:47 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:49 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:52 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:54 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:56 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:33:58 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:34:00 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:34:02 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:34:05 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:34:06 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:34:08 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:34:11 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:34:12 2006 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Thu Jun 29 13:34:12 2006 TLS Error: TLS handshake failed
Thu Jun 29 13:34:12 2006 TCP/UDP: Closing socket
Thu Jun 29 13:34:12 2006 SIGUSR1[soft,tls-error] received, process restarting
Thu Jun 29 13:34:12 2006 Restart pause, 2 second(s)
Thu Jun 29 13:34:14 2006 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Thu Jun 29 13:34:14 2006 Re-using SSL/TLS context
Thu Jun 29 13:34:14 2006 LZO compression initialized
Thu Jun 29 13:34:14 2006 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Thu Jun 29 13:34:14 2006 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Thu Jun 29 13:34:14 2006 Local Options hash (VER=V4): 'd79ca330'
Thu Jun 29 13:34:14 2006 Expected Remote Options hash (VER=V4): 'f7df56b8'
Thu Jun 29 13:34:14 2006 UDPv4 link local: [undef]
Thu Jun 29 13:34:14 2006 UDPv4 link remote: 210.23.137.192:1194
Thu Jun 29 13:34:14 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:34:16 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:34:18 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:34:20 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Thu Jun 29 13:34:22 2006 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: openvpn, client unable to connect
« Reply #1 on: June 29, 2006, 08:16:11 PM »
Quote from: "valdis"
Arvo to all, would appreciate help with openvpn.


openvpn is not installed on a standard SME server install, so your post is off-topic for this forum.

valdis

Arvo to all, would appreciate help with openvpn.
« Reply #2 on: June 30, 2006, 12:30:28 AM »
Hi, must be my mistake.  There is in the standard how-to on the contrib site with links . I was told that to have a vpn connection through my sme server that is what I have to do.

Have also seen open vpn metioned previoulsy in other posts.  Must say I did inadvertently post to 7.x where it should have been 6.x.

Is this not the case, does the standard SME 6.5/7 server have vpn access, and all just works fine with no configuration issues with no certificates. I just installed 6.5 and immediately install openvpn ( as instructed )

Should I download and install version 7.

I am very happy with sme and the only issue I currently have is VPN.

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: Arvo to all, would appreciate help with openvpn.
« Reply #3 on: June 30, 2006, 12:40:54 AM »
Quote from: "valdis"

Must say I did inadvertently post to 7.x where it should have been 6.x.


No, it should have been 7.x Contribs or 6.x Contribs.

valdis

sme 7 & vpn access
« Reply #4 on: June 30, 2006, 01:50:32 AM »
Ok,  wrong forum, so I will make it relevant to my last mail.

I am now downloading sme 7.
I require VPN access into our network, most users use windows vpn client.

Is vpn access in sme 7 standard, with no issues. just say enter 2 in pptp clients and away you go?
Does one have to do "additional" tasks  to get vpn working? If so, a how-to. I am about to search sme serve 7.x (standard components) and reading doco.
Does it/can it use certificates with no/little issue?
Will now stop listening to superiors and check myself.  

Regards
VK