Bonjour
suivre a la configuration ,et apres la verefication j'arrive a :
mon fechier client.conf:
##############################################
# 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
# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load bance between the servers.
remote 192.168.13.159 443
;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 192.168.10.1 8080
# 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 BF-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
si je tappe #openvpn client.conf:
Wed Apr 28 10:59:24 2010 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Wed Apr 28 10:59:24 2010 Re-using SSL/TLS context
Wed Apr 28 10:59:24 2010 LZO compression initialized
Wed Apr 28 10:59:24 2010 Control Channel MTU parms [ L:1544 D:140 EF:40 EB:0 ET:0 EL:0 ]
Wed Apr 28 10:59:24 2010 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Wed Apr 28 10:59:24 2010 Local Options hash (VER=V4): '69109d17'
Wed Apr 28 10:59:24 2010 Expected Remote Options hash (VER=V4): 'c0103fa8'
Wed Apr 28 10:59:24 2010 Attempting to establish TCP connection with 192.168.10.1:8080 [nonblock]
Wed Apr 28 10:59:25 2010 TCP connection established with 192.168.10.1:8080
Wed Apr 28 10:59:25 2010 Send to HTTP proxy: 'CONNECT 192.168.13.159:443 HTTP/1.0'
Wed Apr 28 10:59:26 2010 HTTP proxy returned: 'HTTP/1.0 200 Connection established'
Wed Apr 28 10:59:28 2010 Socket Buffers: R=[87380->131072] S=[16384->131072]
Wed Apr 28 10:59:28 2010 TCPv4_CLIENT link local: [undef]
Wed Apr 28 10:59:28 2010 TCPv4_CLIENT link remote: 192.168.10.1:8080
Wed Apr 28 10:59:28 2010 TLS: Initial packet from 192.168.10.1:8080, sid=24ec3838 a67a0aa1
Wed Apr 28 10:59:28 2010 VERIFY OK: depth=1, /C=TN/ST=CA/L=sousee/O=isitcom/CN=isitcom_CA/emailAddress=taieb.8599@yahoo.fr
Wed Apr 28 10:59:28 2010 VERIFY OK: nsCertType=SERVER
Wed Apr 28 10:59:28 2010 VERIFY OK: depth=0, /C=TN/ST=CA/L=sousee/O=isitcom/CN=server/emailAddress=taieb.8599@yahoo.fr
Wed Apr 28 10:59:28 2010 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Apr 28 10:59:28 2010 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Apr 28 10:59:28 2010 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Apr 28 10:59:28 2010 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Apr 28 10:59:28 2010 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Wed Apr 28 10:59:28 2010 [server] Peer Connection Initiated with 192.168.10.1:8080
Wed Apr 28 10:59:31 2010 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Apr 28 10:59:31 2010 PUSH: Received control message: 'PUSH_REPLY,route 192.168.1.159 255.255.255.0,route 192.168.10.1 255.255.255.0,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5'
Wed Apr 28 10:59:31 2010 OPTIONS IMPORT: timers and/or timeouts modified
Wed Apr 28 10:59:31 2010 OPTIONS IMPORT: --ifconfig/up options modified
Wed Apr 28 10:59:31 2010 OPTIONS IMPORT: route options modified
Wed Apr 28 10:59:31 2010 Preserving previous TUN/TAP instance: tun1
Wed Apr 28 10:59:31 2010 Initialization Sequence Completed
Wed Apr 28 10:59:38 2010 Connection reset, restarting [0]
Wed Apr 28 10:59:38 2010 TCP/UDP: Closing socket
Wed Apr 28 10:59:38 2010 SIGUSR1[soft,connection-reset] received, process restarting
et j 'arrive a pinger l'adresse 10.8.0.1
ping 10.8.0.1
PING 10.8.0.1 (10.8.0.1) 56(84) bytes of data.
64 bytes from 10.8.0.1: icmp_seq=1 ttl=64 time=1.37 ms
64 bytes from 10.8.0.1: icmp_seq=2 ttl=64 time=1.07 ms
64 bytes from 10.8.0.1: icmp_seq=3 ttl=64 time=1.73 ms
64 bytes from 10.8.0.1: icmp_seq=4 ttl=64 time=1.63 ms
^C
donc normalement la configuration se fonctionne
mais comment connecter au serveur par authentification de client
merci d'avance
