It is currently 02.10.2014 00:21


All times are UTC




Post new topic This topic is locked, you cannot edit posts or make further replies.  [ 4 posts ] 
Author Message
 Post subject: OVPN - keine Verbindung zum Server möglich
PostPosted: 19.12.2005 19:37 
Tripple-DES
Tripple-DES

Joined: 19.12.2005 19:09
Posts: 34
Hi,

ich habe heut mal versucht, das besagte OpenVPN aufzusetzen. Und zwar soll das hier auf einem FreeBSD 5.4 (Server) laufen. Optimaler Weise im Bridging Mode. Im Moment wäre ich aber froh, wenn ich überhaupt eine Verbindung hinbekommen könnte.

Beim Installieren und Einrichten bin ich nach [url]http://www.pronix.de/pronix-935.html[/url]
vorgegangen. Davon abgesehen, dass ich die 1024'rer Schlüssellängen auf 2048 gesetzt habe war mein Vorgehen identisch.

Der Server scheint auch zu laufen. Zumindest startet er ohne Fehlermeldung. Ich habe hier die folgende Server.conf:

[code]# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d

# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one. You will need to
# open up this port on your firewall.
port 1194

# TCP or UDP server?
;proto tcp
proto udp

# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap" if you are ethernet bridging.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# 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
tun-mtu 1492
fragment 1300
mssfix

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one. On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap

# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key). Each client
# and the server must have their own cert and
# key file. The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys. Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca /usr/local/etc/openvpn/vpn-ca.pem
cert /usr/local/etc/openvpn/servercert.pem
key /usr/local/etc/openvpn/serverkey.pem

# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys.
dh /usr/local/etc/openvpn/dh2048.pem

# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.8.0.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file. If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt

# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface. Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0. Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients. Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

# Push routes to the client to allow it
# to reach other private subnets behind
# the server. Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"
push "route 10.0.0.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
# iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN. This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
# ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients. There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
# group, and firewall the TUN/TAP interface
# for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
# modify the firewall in response to access
# from different clients. See man
# page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# the TUN/TAP interface to the internet in
# order for this to work properly).
# CAVEAT: May break client's network config if
# client's local DHCP server packets get routed
# through the tunnel. Solution: make sure
# client's local DHCP server is reachable via
# a more specific route than the default route
# of 0.0.0.0/0.0.0.0.
;push "redirect-gateway"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
;push "dhcp-option DNS 10.8.0.1"
;push "dhcp-option WINS 10.8.0.1"

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
;client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.

#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn

# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120

# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
# openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
;tls-auth ta.key 0 # This file is secret
auth SHA1

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC # Blowfish (default)
;cipher AES-128-CBC # AES
;cipher DES-EDE3-CBC # Triple-DES
cipher AES-256-CBC

# Enable compression on the VPN link.
# If you enable it here, you must also
# enable it in the client config file.
comp-lzo

# The maximum number of concurrently connected
# clients we want to allow.
max-clients 100

# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
user nobody
group nobody

# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it. Use one
# or the other (but not both).
;log openvpn.log
;log-append openvpn.log

# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3

# Silence repeating messages. At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20
[/code]


nichts besonderes also.

die Client.ovpn sieht so aus:

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

# 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
tun-mtu 1492
fragment 1300
mssfix

# 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
dev-node Priv-VPN

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

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
;remote my-server-1 1194
;remote my-server-2 1194
remote 10.0.0.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 #]

# 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 "C:\\Programme\\OpenVPN\\config\\vpn-ca.pem"
cert "C:\\Programme\\OpenVPN\\config\\jadecert.pem"
key "C:\\Programme\\OpenVPN\\config\\jadekey.pem"

# 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

#Server muss sich beim Client authentifizieren
tls-remote Server

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

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

# 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[/code]

auch nichts besonderes - denke ich. Als dev-node habe ich den Namen der Lan-Verbindung, der in der Netzwerkumgebung angezeigt wird eingetragen. Was mich irritiert, ist dass die Client.ovpn nirgendwo so wirklich die 10.8.0.x enthält ... so wird mir die entsprechende Nic auch immer als "Kabel abgezogen" angezeigt. :-/

Ich denke auch, hier wird das Problem liegen. Zum besseren Verständnis poste ich hier noch mal die Ausgabe des Clients beim Start:

[code]Mon Dec 19 20:25:54 2005 OpenVPN 2.0.5 Win32-MinGW [SSL] [LZO] built on Nov 2 2
005
Mon Dec 19 20:25:54 2005 IMPORTANT: OpenVPN's default port number is now 1194, b
ased on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earl
ier used 5000 as the default port.
Mon Dec 19 20:25:54 2005 LZO compression initialized
Mon Dec 19 20:25:54 2005 WARNING: normally if you use --mssfix and/or --fragment
, you should also set --tun-mtu 1500 (currently it is 1492)
Mon Dec 19 20:25:54 2005 Control Channel MTU parms [ L:1554 D:138 EF:38 EB:0 ET:
0 EL:0 ]
Mon Dec 19 20:25:54 2005 Data Channel MTU parms [ L:1554 D:1300 EF:62 EB:135 ET:
0 EL:0 AF:3/1 ]
Mon Dec 19 20:25:54 2005 Fragmentation MTU parms [ L:1554 D:1300 EF:61 EB:135 ET
:1 EL:0 AF:3/1 ]
Mon Dec 19 20:25:54 2005 Local Options hash (VER=V4): 'a9557fc3'
Mon Dec 19 20:25:54 2005 Expected Remote Options hash (VER=V4): '3e1c4603'
Mon Dec 19 20:25:54 2005 UDPv4 link local: [undef]
Mon Dec 19 20:25:54 2005 UDPv4 link remote: 10.0.0.2:1194
Mon Dec 19 20:25:54 2005 TLS: Initial packet from 10.0.0.2:1194, sid=7832705d 04
7efc6e
Mon Dec 19 20:25:54 2005 VERIFY ERROR: depth=0, error=self signed certificate: /
C=DE/ST=land/L=ort/O=private/CN=name/emailAddress=meine.e@mail.adresse
Mon Dec 19 20:25:54 2005 TLS_ERROR: BIO read tls_read_plaintext error: error:140
90086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Mon Dec 19 20:25:54 2005 TLS Error: TLS object -> incoming plaintext read error
Mon Dec 19 20:25:54 2005 TLS Error: TLS handshake failed
Mon Dec 19 20:25:54 2005 TCP/UDP: Closing socket
Mon Dec 19 20:25:54 2005 SIGUSR1[soft,tls-error] received, process restarting
Mon Dec 19 20:25:54 2005 Restart pause, 2 second(s)
Mon Dec 19 20:25:56 2005 IMPORTANT: OpenVPN's default port number is now 1194, b
ased on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earl
ier used 5000 as the default port.
Mon Dec 19 20:25:56 2005 Re-using SSL/TLS context
Mon Dec 19 20:25:56 2005 LZO compression initialized
Mon Dec 19 20:25:56 2005 WARNING: normally if you use --mssfix and/or --fragment
, you should also set --tun-mtu 1500 (currently it is 1492)
Mon Dec 19 20:25:56 2005 Control Channel MTU parms [ L:1554 D:138 EF:38 EB:0 ET:
0 EL:0 ]
Mon Dec 19 20:25:56 2005 Data Channel MTU parms [ L:1554 D:1300 EF:62 EB:135 ET:
0 EL:0 AF:3/1 ]
Mon Dec 19 20:25:56 2005 Fragmentation MTU parms [ L:1554 D:1300 EF:61 EB:135 ET
:1 EL:0 AF:3/1 ]
Mon Dec 19 20:25:56 2005 Local Options hash (VER=V4): 'a9557fc3'
Mon Dec 19 20:25:56 2005 Expected Remote Options hash (VER=V4): '3e1c4603'
Mon Dec 19 20:25:56 2005 UDPv4 link local: [undef]
Mon Dec 19 20:25:56 2005 UDPv4 link remote: 10.0.0.2:1194
Mon Dec 19 20:25:56 2005 TCP/UDP: Closing socket
Mon Dec 19 20:25:56 2005 SIGTERM[hard,] received, process exiting
Press any key to continue...[/code]

Wenn es weiterhilft, kann ich auch gern noch die Ausgabend es Servers posten ...

die Win Firewall hab ich für diese Nic abgeschalten, werd die aber gleich mal ganz deaktivieren .. vielleicht hilfts ja ...

Ansonsten weiß ich hier grad nicht mehr so wirklich weiter ...

In diesem Sinne bin ich auch über jeden Hinweis dankbar ...

Im Voraus schon mal danke ...

Steffen


Top
Offline Profile  
 
 Post subject:
PostPosted: 20.12.2005 10:50 
Top-Supporter
Top-Supporter
User avatar

Joined: 13.09.2004 08:51
Posts: 1465
Location: Schwobaländle
Sieht wohl so aus als ob deine Zertifikate nicht funktionieren

Mon Dec 19 20:25:54 2005 VERIFY ERROR: depth=0, error=self signed certificate: /
C=DE/ST=land/L=ort/O=private/CN=name/emailAddress=meine.e@mail.adresse
Mon Dec 19 20:25:54 2005 TLS_ERROR: BIO read tls_read_plaintext error: error:140
90086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Mon Dec 19 20:25:54 2005 TLS Error: TLS object -> incoming plaintext read error
Mon Dec 19 20:25:54 2005 TLS Error: TLS handshake failed


Top
Offline Profile  
 
 Post subject:
PostPosted: 20.12.2005 12:11 
Tripple-DES
Tripple-DES

Joined: 19.12.2005 19:09
Posts: 34
Hi,

wie eben schon bemerkt ... kann das an der Zeit liegen, die auf beiden Systemen unterschiedlich ist?

Die Anleitung sah ansonsten recht ordentlich aus ... und auch das was ich in der Zwischenzeit auf verschiedenen Anderen Seiten nachgelesen habe (z.B. [url]http://www.openbsd.de/files/openbsd-ipsec.pdf[/url]
[url]http://www.dfn-pca.de/certify/ssl/handbuch/ossl095/ossl095-7.html[/url]

usw. deckt sich damit ...

Wenn du noch Ideen hast ...

... ansonsten Danke erst einmal ... und ich melde mich, wenn es klappt - oder auch nicht klappt ...

Steffen


Top
Offline Profile  
 
 Post subject:
PostPosted: 20.12.2005 12:19 
Top-Supporter
Top-Supporter
User avatar

Joined: 13.09.2004 08:51
Posts: 1465
Location: Schwobaländle
Ich schliese den Topic erstmal. Ich hab irgendwie das Gefühl von einem Murmeltiertag wenn ich deinen beiden Threats hin und her springe :roll:

hier geht es weiter


Top
Offline Profile  
 
Display posts from previous:  Sort by  
Post new topic This topic is locked, you cannot edit posts or make further replies.  [ 4 posts ]  Moderator: Moderators

All times are UTC


Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
Theme created StylerBB.net