OpenVPN le client ne se connecte pasRésolu/Fermé

Question

Bonjour, 

Je viens de remonter un openVPN sur un serveur CentOS 6 64 bits.

J'ai installé l'application, généré mes clés et j'ai un problème.
Le PC client ne se connecte pas.

J'ai refait mon jeu de certificats plusieurs pensant que cela venait de là, mais finalement je ne crois pas.
J'ai plutôt l'impression que ça provient de l'application openvpn, mais je ne vois pas ce qui bloque.

Pour info, je donne l'adresse 200.100.100.50, mais forcément, elle est trop ronde pour être l'adresse réelle du serveur.

Coté serveur l'interface réseau iptunnel se monte correctement :

(extrait du résultat de ifconfig)
tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00          inet addr:10.8.0.1  P-t-P:10.8.0.2  Mask:255.255.255.255          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1          RX packets:0 errors:0 dropped:0 overruns:0 frame:0          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0          collisions:0 txqueuelen:100          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Voici ce que j'ai sur le serveur dans /var/log/messages

Feb 12 19:16:41 servername openvpn[5050]: I/O WAIT TR|Tw|SR|Sw [10/0]Feb 12 19:16:51 servername openvpn[5050]:  event_wait returned 0Feb 12 19:16:51 servername openvpn[5050]: I/O WAIT status=0x0020Feb 12 19:16:51 servername openvpn[5050]: MULTI: REAP range 176 -> 192Feb 12 19:16:51 servername openvpn[5050]: SCHEDULE: schedule_find_least NULLFeb 12 19:16:51 servername openvpn[5050]: PO_CTL rwflags=0x0001 ev=6 arg=0x0069c9e8Feb 12 19:16:51  servername openvpn[5050]: PO_CTL rwflags=0x0001 ev=7 arg=0x0069c8c8Feb 12 19:16:51  servername openvpn[5050]: I/O WAIT TR|Tw|SR|Sw [10/0]

Je pense que le problème se situe coté serveur, car avec un fichier client openvpn qui fonctionnait avec un ancien serveur, ça ne fonctionne pas mieux. (configuration cliente équivalente, j'ai pris soin de mettre la bonne addresse du serveur avant d'essayer).


Coté client le journal est un peu long, donc avant de le mettre je vais fournir les fichiers :

/etc/openvpn/server.conf
et
C:\program files\openvpn\config\client.ovpn

/etc/openvpn/server.conf
port 1194 #- portproto udp #- protocoldev tuntun-mtu 1500tun-mtu-extra 32mssfix 1450reneg-sec 0ca /etc/openvpn/easy-rsa/2.0/keys/ca.crtcert /etc/openvpn/easy-rsa/2.0/keys/server.crt#cert /etc/openvpn/easy-rsa/2.0/keys/ovpnsrv1.crtkey /etc/openvpn/easy-rsa/2.0/keys/server.key#key /etc/openvpn/easy-rsa/2.0/keys/ovpnsrv1.keydh /etc/openvpn/easy-rsa/2.0/keys/dh1024.pem#plugin /usr/share/openvpn/plugin/lib/openvpn-auth-pam.so /etc/pam.d/login #- Comment this line if you are using FreeRADIUSplugin /etc/openvpn/openvpn-auth-pam.so /etc/pam.d/login#plugin /usr/lib64/openvpn/plugin/lib/openvpn-auth-pam.so /etc/pam.d/login#plugin /etc/openvpn/radiusplugin.so /etc/openvpn/radiusplugin.cnf #- Uncomment this line if you are using FreeRADIUSclient-cert-not-requiredusername-as-common-nameserver 10.8.0.0 255.255.255.0push "redirect-gateway def1"push "dhcp-option DNS 8.8.8.8"push "dhcp-option DNS 8.8.4.4"keepalive 5 30comp-lzopersist-keypersist-tunstatus 1194.log#verb 3verb 9


c:\program files\openvpn\config\client.ovpn
############################################### 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 tapdev 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 tcpproto udp# The hostname/IP and port of the server.# You can have multiple remote entries# to load balance between the servers.remote 200.100.100.50 1194   #adresse fictive modifiée.;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-keypersist-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 ca.crt#cert client.crt #Fichier de la config de base.#key client.key #Fichier de la config de base.cert vpnhome.crtkey vpnhome.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:#  https://openvpn.net/community-resources/how-to/#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 9# Silence repeating messages;mute 20



Dans le journal coté client (Windows), j'ai beaucoup de lignes comme celles-ci :
Thu Feb 12 15:27:00 2015 us=150870  event_wait returned 1Thu Feb 12 15:27:01 2015 us=170768  event_wait returned 0
Mais comme j'ai mis le journal en mode "verbeux" je ne pense pas que ça ait un rapport.

Vers la fin de mon journal coté client (Windows), j'ai ça :

Thu Feb 12 15:32:02 2015 us=164596 WIN32 I/O: Socket Completion non-queued error: Invalid argument (WSAEINVAL) (errno=10022)Thu Feb 12 15:32:02 2015 us=164596 UDPv4 read returned -1Thu Feb 12 15:32:02 2015 us=164596 UDPv4 READ [0] from [undef]: DATA UNDEF len=-1Thu Feb 12 15:32:02 2015 us=164596  event_wait returned 1Thu Feb 12 15:32:02 2015 us=583596  event_wait returned 1Thu Feb 12 15:32:02 2015 us=583596 UDPv4 read returned 26Thu Feb 12 15:32:02 2015 us=583596 UDPv4 READ [26] from [AF_INET]200.100.100.50:1194: P_CONTROL_HARD_RESET_SERVER_V2 kid=0 sid=fcadd885 5a0b2941 [ 0 sid=f1a88f1e 5237851b ] pid=0 DATA Thu Feb 12 15:32:02 2015 us=583596 MANAGEMENT: >STATE:1423791122,AUTH,,,Thu Feb 12 15:32:02 2015 us=583596 TLS: Initial packet from [AF_INET]200.100.100.50:1194, sid=fcadd885 5a0b2941Thu Feb 12 15:32:02 2015 us=583596  event_wait returned 2Thu Feb 12 15:32:02 2015 us=583596 UDPv4 WRITE [22] to [AF_INET]200.100.00.50:1194: P_ACK_V1 kid=0 sid=f1a88f1e 5237851b [ 0 sid=fcadd885 5a0b2941 ]Thu Feb 12 15:32:02 2015 us=583596 UDPv4 write returned 22Thu Feb 12 15:32:02 2015 us=584596  event_wait returned 2Thu Feb 12 15:32:02 2015 us=584596 UDPv4 WRITE [114] to [AF_INET]200.100.00.50:1194: P_CONTROL_V1 kid=0 sid=f1a88f1e 5237851b [ ] pid=1 DATA 16030100 ce010000 ca030137 957a57c1 03fd70e3 ecce39a1 2e3f48cb 8a3031e[more...]Thu Feb 12 15:32:02 2015 us=584596 UDPv4 write returned 114Thu Feb 12 15:32:02 2015 us=584596  event_wait returned 2Thu Feb 12 15:32:02 2015 us=584596 UDPv4 WRITE [114] to [AF_INET]200.100.00.50:1194: P_CONTROL_V1 kid=0 sid=f1a88f1e 5237851b [ ] pid=2 DATA c0020005 0004c012 c0080016 0013c00d c003000a 00150012 00090014 0011000[more...]Thu Feb 12 15:32:02 2015 us=584596 UDPv4 write returned 114Thu Feb 12 15:32:02 2015 us=584596  event_wait returned 2Thu Feb 12 15:32:02 2015 us=584596 UDPv4 WRITE [25] to [AF_INET]200.100.00.50:1194: P_CONTROL_V1 kid=0 sid=f1a88f1e 5237851b [ ] pid=3 DATA 000f0010 0011000f 000101Thu Feb 12 15:32:02 2015 us=584596 UDPv4 write returned 25Thu Feb 12 15:32:02 2015 us=584596  event_wait returned 1Thu Feb 12 15:32:02 2015 us=642596  event_wait returned 1Thu Feb 12 15:32:02 2015 us=642596 PKCS#11: __pkcs11h_openssl_ex_data_free entered - parent=000000000033B020, ptr=0000000000000000, ad=000000000033B078, idx=0, argl=0, argp=00000000645D7DCFThu Feb 12 15:32:02 2015 us=642596 PKCS#11: __pkcs11h_openssl_ex_data_free entered - parent=00000000003A3100, ptr=0000000000000000, ad=00000000003A3158, idx=0, argl=0, argp=00000000645D7DCFThu Feb 12 15:32:02 2015 us=642596 TCP/UDP: Closing socketThu Feb 12 15:32:02 2015 us=643596 SIGTERM[hard,] received, process exitingThu Feb 12 15:32:02 2015 us=643596 MANAGEMENT: >STATE:1423791122,EXITING,SIGTERM,,Thu Feb 12 15:32:02 2015 us=643596 PKCS#11: pkcs11h_terminate entryThu Feb 12 15:32:02 2015 us=643596 PKCS#11: Terminating opensslThu Feb 12 15:32:02 2015 us=643596 PKCS#11: _pkcs11h_openssl_terminateThu Feb 12 15:32:02 2015 us=643596 PKCS#11: Removing providersThu Feb 12 15:32:02 2015 us=643596 PKCS#11: Releasing sessionsThu Feb 12 15:32:02 2015 us=643596 PKCS#11: Terminating sloteventThu Feb 12 15:32:02 2015 us=643596 PKCS#11: _pkcs11h_slotevent_terminate entryThu Feb 12 15:32:02 2015 us=643596 PKCS#11: _pkcs11h_slotevent_terminate returnThu Feb 12 15:32:02 2015 us=643596 PKCS#11: Marking as uninitialized



Je pense qu'il y a beaucoup de détails dans ce message, peut-être même un peu trop.
Il y a deux jours que je me bagarre avec cette config et j'ai du mal à m'en sortir.
J'ai déjà regardé sur le site "openvpn.net" et j'ai trouvé des messages décrivant le même problème, mais pas de solutions.

Merci par avance pour votre aide.

Configuration: GNU/Linux

Mykkel · Answer

bonjour, 
déjà, si tu indiques client-cert-not-required, alors les clés d'authenfication sur le client deviennent inutiles.

lignes à commenter pour le test:  
tun-mtu 1500
tun-mtu-extra 32
mssfix 1450
reneg-sec 0
plugin /etc/openvpn/openvpn-auth-pam.so /etc/pam.d/login
client-cert-not-required
username-as-common-name


et donnes l'affichage sur le serveur avant de lancer le client

à la fin, tu dois avoir ça:
   MULTI: TCP INIT maxclients=1024 maxevents=1028   Initialization Sequence Completed

jivef · Answer

Bonjour,
J'ai modifié un peu la config pour avoir un fichier log distinct au démarrage de l'application.
Et j'ai un fichier qui répertorie les machines connectées.

Le fichier 1194.log (Qui est sensé répertorier les machines connectées) ne voit rien passer.
[root@servername openvpn]# cat 1194.logOpenVPN CLIENT LISTUpdated,Thu Feb 19 19:29:07 2015Common Name,Real Address,Bytes Received,Bytes Sent,Connected SinceROUTING TABLEVirtual Address,Common Name,Real Address,Last RefGLOBAL STATSMax bcast/mcast queue length,0END[root@servername openvpn]#

Le fichier openvpn.log est le même que précédemment, sauf que j'ai réactivé l'authentification par jeu de clés.

Je ne pense pas que le problème provienne des clés, car il apparait même sans ça.
Mais je ne vois pas ou est l'erreur.
Je pense que je vais sauvegarder mon jeu de clés et tenter de réinstaller totalement OpenVPN.

Qu'en penses-tu ?


Ou bien, je peux essayer de l'installer sur une autre machine et m'en servir comme modèle.

jivef · Answer

En regardant les détails de OpenVPN voici ce que j'obtiens.

[root@servername etc]# openvpn --versionOpenVPN 2.3.6 x86_64-redhat-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Dec  2 2014library versions: OpenSSL 1.0.1e-fips 11 Feb 2013, LZO 2.03Originally developed by James YonanCopyright (C) 2002-2010 OpenVPN Technologies, Inc. <sales@openvpn.net>Compile time defines: enable_crypto=yes enable_crypto_ofb_cfb=yes enable_debug=yes enable_def_auth=yes enable_dlopen=unknown enable_dlopen_self=unknown enable_dlopen_self_static=unknown enable_fast_install=yes enable_fragment=yes enable_http_proxy=yes enable_iproute2=yes enable_libtool_lock=yes enable_lzo=yes enable_lzo_stub=no enable_management=yes enable_multi=yes enable_multihome=yes enable_pam_dlopen=no enable_password_save=yes enable_pedantic=no enable_pf=yes enable_pkcs11=yes enable_plugin_auth_pam=yes enable_plugin_down_root=yes enable_plugins=yes enable_port_share=yes enable_pthread=yes enable_selinux=no enable_server=yes enable_shared=yes enable_shared_with_static_runtimes=no enable_small=no enable_socks=yes enable_ssl=yes enable_static=yes enable_strict=no enable_strict_options=no enable_systemd=no enable_win32_dll=yes enable_x509_alt_username=yes with_crypto_library=openssl with_gnu_ld=yes with_iproute_path=/sbin/ip with_mem_check=no with_plugindir='$(libdir)/openvpn/plugins' with_sysroot=no[root@servername etc]#

jivef · Answer

Finalement, j'ai repris le fichier sample, puis en même temps, j'ai déplacé les certificats dans le dossier /etc/openvpn.
Et Ca a refonctionné.

Ouf !

Je n'ose pas encore mettre en résolu, on verra demain...

jivef · Answer

Après réfection complète du fichier /etc/openvpn/server.conf, openvpn refonctionne de nouveau correctement. Voici le nouveau fichier : Une des différences avec l'ancien est qu'il n'y est pas fait mention du plugin d'authentification : ################################################## Sample OpenVPN 2.0 config file for ## multi-client server. ## ## This file is for the server side ## of a many-clients <-> one-server ## OpenVPN configuration. ## ## OpenVPN also supports ## single-machine <-> single-machine ## configurations (See the Examples page ## on the web site for more info). ## ## This config should work on Windows ## or Linux/BSD systems. Remember on ## Windows to quote pathnames and use ## double backslashes, e.g.: ## "C:\Program Files\OpenVPN\config\foo.key" ## ## Comments are preceded with '#' or ';' ################################################### 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 tcpproto udp# "dev tun" will create a routed IP tunnel,# "dev tap" will create an ethernet tunnel.# Use "dev tap0" if you are ethernet bridging# and have precreated a tap0 virtual interface# and bridged it with your ethernet interface.# 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 tapdev tun# 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 ca.crtcert server.crtkey server.key # This file should be kept secret# Diffie hellman parameters.# Generate your own with:# openssl dhparam -out dh2048.pem 2048#dh dh2048.pemdh dh1024.pem# Network topology# Should be subnet (addressing via IP)# unless Windows clients v2.0.9 and lower have to# be supported (then net30, i.e. a /30 per client)# Defaults to net30 (not recommended);topology subnet# 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# Configure server mode for ethernet bridging# using a DHCP-proxy, where clients talk# to the OpenVPN server-side DHCP server# to receive their IP address allocation# and DNS server addresses. You must first use# your OS's bridging capability to bridge the TAP# interface with the ethernet NIC interface.# Note: this mode only works on clients (such as# Windows), where the client-side TAP adapter is# bound to a DHCP client.;server-bridge# 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"# 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# or bridge the TUN/TAP interface to the internet# in order for this to work properly).;push "redirect-gateway def1 bypass-dhcp"# Certain Windows-specific network settings# can be pushed to clients, such as DNS# or WINS server addresses. CAVEAT:# https://community.openvpn.net/openvpn/wiki/FAQ#dhcpcaveats# The addresses below refer to the public# DNS servers provided by opendns.com.;push "dhcp-option DNS 208.67.222.222";push "dhcp-option DNS 208.67.220.220"# 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# 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# 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-keypersist-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 verboseverb 9# Silence repeating messages. At most 20# sequential messages of the same message# category will be output to the log.;mute 2 Et voici l'ancien fichier qui ne permet pas l'authentification entre le client et le serveur. port 1194 #- portproto udp #- protocol#proto tcp #- protocoldev tun#tun-mtu 1500#tun-mtu-extra 32#mssfix 1450#reneg-sec 0ca /etc/openvpn/easy-rsa/2.0/keys/ca.crtcert /etc/openvpn/easy-rsa/2.0/keys/server.crt#cert /etc/openvpn/easy-rsa/2.0/keys/ovpnsrv1.crtkey /etc/openvpn/easy-rsa/2.0/keys/server.key#key /etc/openvpn/easy-rsa/2.0/keys/ovpnsrv1.keydh /etc/openvpn/easy-rsa/2.0/keys/dh1024.pem#plugin /usr/share/openvpn/plugin/lib/openvpn-auth-pam.so /etc/pam.d/login #- Comment this line if you are using FreeRADIUSplugin /etc/openvpn/openvpn-auth-pam.so /etc/pam.d/login#plugin /usr/lib64/openvpn/plugin/lib/openvpn-auth-pam.so /etc/pam.d/login#plugin /etc/openvpn/radiusplugin.so /etc/openvpn/radiusplugin.cnf #- Uncomment this line if you are using FreeRADIUS#client-cert-not-required#username-as-common-nameserver 10.8.0.0 255.255.255.0##push "redirect-gateway def1"push "redirect-gateway"push "dhcp-option DNS 8.8.8.8"push "dhcp-option DNS 8.8.4.4"keepalive 5 30comp-lzomax-clients 5 #Ajoute car il ne devrait pas y avoir plus de 5 connexions simultanees.persist-keypersist-tunstatus 1194.loglog openvpn.log #Ajoute pour avoir des informations a chaque redemarrage.#verb 3verb 9 Je passe le fil en résolu.

OpenVPN le client ne se connecte pas

5 réponses

Discussions similaires

Newsletters