OpenVPN

Résolu
Dash226 Messages postés 19 Statut Membre -  
mamiemando Messages postés 33228 Date d'inscription   Statut Modérateur Dernière intervention   -
Bonjour,
j'essaie de mettre en place mon réseau VPN en utilisant comme serveur ma machine virtuelle Ubuntu 14.04 LTS sous VirtualBox et comme client ma machine Windows 8.1 profesionnal N .
j'ai edité mon fichier de configuration server.conf comme ceci

port : 8000
dev tun
proto tcp
ca ca.crt
cert server.crt
key server.key
dh dh2048.pem
server 10.9.1.0 255.255.255.0
ifconfig-pool-persist ipp.txt
keepalive 10 120
push "redirect-gateway def1 bypass dhcp"
push "dhcp-option DNS 208.67.222.222"
push "dhcp-option DNS 208.67.220.220"

Cependant quand je demarre la server par la commande sudo openvpn server.conf
j'ai l'erreur

TCP/UDP: Socket bind failed on local address [undef]: address already in use

1 réponse

  1.
    mamiemando Messages postés 33228 Date d'inscription   Statut Modérateur Dernière intervention   7 940
     
    Cela signifie qu'un sicket est déjà ouvert sur ce port (soit par ton serveur openvpn, déjà lancé, soit par un autre serveur, configuré pour utiliser le même port).

    Chose étrange, tu sembles vouloir configurer un serveur openvpn qui écoute sur le port 8000, or ce n'est pas le port standard...
    https://openvpn.net/vpn-server-resources/

    Bonne chance
    1
    1. Dash226 Messages postés 19 Statut Membre
       
      oui je sais j'ai changé parce que je pensais que l'erreur etait du au port mais en utilisant un
      ps -A
      j'ai pu trouver le processus que j'ai tué avec un kill et le serveur démarre normallement le client aussi démarre normallement sur ma machine virtuelle ubuntu mais quand j'essaie de me connecter sur Window avec NMDVPN il me disent dans les logs :
      tls error tls key negotiation failed to occur within 60 seconds
      une idée ?
      0
    3. Dash226 Messages postés 19 Statut Membre
       
      Désolé pour le manque de ponctuation :( . J'ai suivi les instructions j'ai remplacé la valeur remote dans le fichier client.conf et j'ai mis l'adresse public du serveur. Maintenant l'initialisation se complète mais avec des erreurs. Voici le log :

      Fri Sep 05 11:39:01 2014 NMDVPN 2.1.4 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Apr 25 2011
      Fri Sep 05 11:39:01 2014 NOTE: NMDVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
      Fri Sep 05 11:39:01 2014 LZO compression initialized
      Fri Sep 05 11:39:01 2014 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
      Fri Sep 05 11:39:01 2014 Socket Buffers: R=[65536->65536] S=[65536->65536]
      Fri Sep 05 11:39:01 2014 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
      Fri Sep 05 11:39:01 2014 Local Options hash (VER=V4): '41690919'
      Fri Sep 05 11:39:01 2014 Expected Remote Options hash (VER=V4): '530fdded'
      Fri Sep 05 11:39:01 2014 UDPv4 link local: [undef]
      Fri Sep 05 11:39:01 2014 UDPv4 link remote: 172.25.4.167:2608
      Fri Sep 05 11:39:01 2014 TLS: Initial packet from 172.25.4.167:2608, sid=6c865214 8f9bcab4
      Fri Sep 05 11:39:01 2014 VERIFY OK: depth=1, /C=BF/ST=Kadiogo/L=Ouagadougou/O=Airtel/OU=MyOrganizationalUnit/CN=server/name=EasyRSA/emailAddress=me@myhost.mydomain
      Fri Sep 05 11:39:01 2014 VERIFY OK: nsCertType=SERVER
      Fri Sep 05 11:39:01 2014 VERIFY OK: depth=0, /C=BF/ST=Kadiogo/L=Ouagadougou/O=Airtel/OU=MyOrganizationalUnit/CN=server/name=EasyRSA/emailAddress=me@myhost.mydomain
      Fri Sep 05 11:39:01 2014 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
      Fri Sep 05 11:39:01 2014 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
      Fri Sep 05 11:39:01 2014 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
      Fri Sep 05 11:39:01 2014 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
      Fri Sep 05 11:39:01 2014 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA
      Fri Sep 05 11:39:01 2014 [server] Peer Connection Initiated with 172.25.4.167:2608
      Fri Sep 05 11:39:03 2014 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
      Fri Sep 05 11:39:03 2014 PUSH: Received control message: 'PUSH_REPLY,route 172.25.4.17 255.255.254.0,route 192.168.20.0 255.255.255.0,redirect-gateway def1 bypass dhcp,dhcp-option DNS 208.67.222.222,dhcp-option DNS 208.67.220.220,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5'
      Fri Sep 05 11:39:03 2014 Options error: unknown --redirect-gateway flag: bypass
      Fri Sep 05 11:39:03 2014 OPTIONS IMPORT: timers and/or timeouts modified
      Fri Sep 05 11:39:03 2014 OPTIONS IMPORT: --ifconfig/up options modified
      Fri Sep 05 11:39:03 2014 OPTIONS IMPORT: route options modified
      Fri Sep 05 11:39:03 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
      Fri Sep 05 11:39:03 2014 ROUTE default_gateway=172.25.4.254
      Fri Sep 05 11:39:06 2014 RESOLVE: Cannot resolve host address: delay: [HOST_NOT_FOUND] The specified host is unknown.
      Fri Sep 05 11:39:06 2014 NMDVPN ROUTE: failed to parse/resolve route for host/network: delay
      Fri Sep 05 11:39:06 2014 TAP-WIN32 device [Ethernet 2] opened: \\.\Global\{2E5605B3-DE28-4777-B9FC-2705B2CD25FE}.tap
      Fri Sep 05 11:39:06 2014 TAP-Win32 Driver Version 9.21
      Fri Sep 05 11:39:06 2014 TAP-Win32 MTU=1500
      Fri Sep 05 11:39:06 2014 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {2E5605B3-DE28-4777-B9FC-2705B2CD25FE} [DHCP-serv: 10.8.0.5, lease-time: 31536000]
      Fri Sep 05 11:39:06 2014 NOTE: FlushIpNetTable failed on interface [102] {2E5605B3-DE28-4777-B9FC-2705B2CD25FE} (status=1168) : Élément introuvable.
      Fri Sep 05 11:39:11 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:11 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:16 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:16 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:17 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:17 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:18 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:18 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:20 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:20 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:21 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:21 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:22 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:22 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:23 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:23 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:24 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:24 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:26 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:26 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:27 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:27 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:28 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:28 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:29 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:29 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:31 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:31 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:32 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:32 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:33 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:33 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:34 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:34 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:35 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:35 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:37 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:37 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:38 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:38 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:39 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:39 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:40 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:40 2014 Route: Waiting for TUN/TAP interface to come up...
      Fri Sep 05 11:39:41 2014 TEST ROUTES: 0/3 succeeded len=3 ret=0 a=0 u/d=up
      Fri Sep 05 11:39:41 2014 WARNING: potential route subnet conflict between local LAN [172.25.4.0/255.255.254.0] and remote VPN [172.25.4.0/255.255.254.0]
      Fri Sep 05 11:39:41 2014 C:\WINDOWS\system32\route.exe ADD 172.25.4.17 MASK 255.255.254.0 10.8.0.5
      L'ajout de l'itin'raire a 'chou'ÿ: ParamStre incorrect.
      Fri Sep 05 11:39:42 2014 C:\WINDOWS\system32\route.exe ADD 192.168.20.0 MASK 255.255.255.0 10.8.0.5
      L'ajout de l'itin'raire a 'chou'ÿ: L'objet existe d'j....
      Fri Sep 05 11:39:42 2014 C:\WINDOWS\system32\route.exe ADD 10.8.0.1 MASK 255.255.255.255 10.8.0.5
      L'ajout de l'itin'raire a 'chou'ÿ: L'objet existe d'j....
      SYSTEM ROUTING TABLE
      0.0.0.0 0.0.0.0 172.25.4.254 p=0 i=4 t=4 pr=3 a=2959 h=0 m=25/0/0/0/0
      10.8.0.1 255.255.255.255 10.8.0.5 p=0 i=4 t=4 pr=3 a=1400 h=0 m=26/0/0/0/0
      10.16.0.0 255.255.0.0 172.25.4.253 p=0 i=4 t=4 pr=3 a=2959 h=0 m=26/0/0/0/0
      127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=157848 h=0 m=306/0/0/0/0
      127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=157848 h=0 m=306/0/0/0/0
      127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=157848 h=0 m=306/0/0/0/0
      172.17.0.0 255.255.0.0 172.25.4.253 p=0 i=4 t=4 pr=3 a=2959 h=0 m=26/0/0/0/0
      172.25.4.0 255.255.254.0 172.25.4.154 p=0 i=4 t=3 pr=2 a=2959 h=0 m=281/0/0/0/0
      172.25.4.154 255.255.255.255 172.25.4.154 p=0 i=4 t=3 pr=2 a=2959 h=0 m=281/0/0/0/0
      172.25.5.255 255.255.255.255 172.25.4.154 p=0 i=4 t=3 pr=2 a=2959 h=0 m=281/0/0/0/0
      172.25.26.0 255.255.255.0 172.25.4.253 p=0 i=4 t=4 pr=3 a=2959 h=0 m=26/0/0/0/0
      192.168.20.0 255.255.255.0 10.8.0.5 p=0 i=4 t=4 pr=3 a=1400 h=0 m=26/0/0/0/0
      192.168.56.0 255.255.255.0 192.168.56.1 p=0 i=88 t=3 pr=2 a=2974 h=0 m=276/0/0/0/0
      192.168.56.1 255.255.255.255 192.168.56.1 p=0 i=88 t=3 pr=2 a=2974 h=0 m=276/0/0/0/0
      192.168.56.255 255.255.255.255 192.168.56.1 p=0 i=88 t=3 pr=2 a=2974 h=0 m=276/0/0/0/0
      192.168.248.0 255.255.254.0 172.25.4.253 p=0 i=4 t=4 pr=3 a=2959 h=0 m=26/0/0/0/0
      224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=157848 h=0 m=306/0/0/0/0
      224.0.0.0 240.0.0.0 192.168.56.1 p=0 i=88 t=3 pr=2 a=2978 h=0 m=276/0/0/0/0
      224.0.0.0 240.0.0.0 172.25.4.154 p=0 i=4 t=3 pr=2 a=2977 h=0 m=281/0/0/0/0
      255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=157848 h=0 m=306/0/0/0/0
      255.255.255.255 255.255.255.255 192.168.56.1 p=0 i=88 t=3 pr=2 a=2978 h=0 m=276/0/0/0/0
      255.255.255.255 255.255.255.255 172.25.4.154 p=0 i=4 t=3 pr=2 a=2977 h=0 m=281/0/0/0/0
      SYSTEM ADAPTER LIST
      Bluetooth Device (Personal Area Network)
      Index = 9
      GUID = {62B2DFEE-72F3-4B0B-A401-CA84D2AD4014}
      IP = 0.0.0.0/0.0.0.0
      MAC = e0:ca:94:e7:3f:56
      GATEWAY = 0.0.0.0/255.255.255.255
      DHCP SERV =
      DHCP LEASE OBTAINED = Fri Sep 05 11:39:42 2014
      DHCP LEASE EXPIRES = Fri Sep 05 11:39:42 2014
      DNS SERV =
      Microsoft Wi-Fi Direct Virtual Adapter
      Index = 5
      GUID = {F30C1AE1-B28B-47FD-8518-B0D7A9A558F4}
      IP = 0.0.0.0/0.0.0.0
      MAC = e0:ca:94:e6:ef:42
      GATEWAY = 0.0.0.0/255.255.255.255
      DHCP SERV =
      DHCP LEASE OBTAINED = Fri Sep 05 11:39:42 2014
      DHCP LEASE EXPIRES = Fri Sep 05 11:39:42 2014
      DNS SERV =
      Realtek RTL8723AE Wireless LAN 802.11n PCI-E NIC
      Index = 4
      GUID = {A0F85C93-FE9D-4567-8C9F-F27EAD808268}
      IP = 172.25.4.154/255.255.254.0
      MAC = e0:ca:94:e6:ef:42
      GATEWAY = 172.25.4.254/255.255.255.255
      DHCP SERV = 172.25.1.209/255.255.255.255
      DHCP LEASE OBTAINED = Fri Sep 05 10:50:23 2014
      DHCP LEASE EXPIRES = Fri Sep 05 22:50:23 2014
      PRI WINS = 172.25.1.208/255.255.255.255
      SEC WINS = 172.25.1.209/255.255.255.255
      DNS SERV = 172.25.1.208/255.255.255.255 172.25.1.209/255.255.255.255
      Realtek PCIe FE Family Controller
      Index = 3
      GUID = {FD769B69-A2F8-485F-81DB-2C3F28D4EEF8}
      IP = 0.0.0.0/0.0.0.0
      MAC = e8:40:f2:99:be:f9
      GATEWAY = 0.0.0.0/255.255.255.255
      DHCP SERV =
      DHCP LEASE OBTAINED = Fri Sep 05 11:39:42 2014
      DHCP LEASE EXPIRES = Fri Sep 05 11:39:42 2014
      PRI WINS = 172.25.1.208/255.255.255.255
      SEC WINS = 172.25.1.209/255.255.255.255
      DNS SERV =
      VirtualBox Host-Only Ethernet Adapter
      Index = 88
      GUID = {7852A50A-CD33-4958-8EA0-0C4431A24142}
      IP = 192.168.56.1/255.255.255.0
      MAC = 08:00:27:00:f0:99
      GATEWAY = 0.0.0.0/255.255.255.255
      DNS SERV =
      Fri Sep 05 11:39:42 2014 Initialization Sequence Completed With Errors ( see https://community.openvpn.net/openvpn/wiki/FAQ#dhcpclientserv )
      0
    4. mamiemando Messages postés 33228 Date d'inscription   Statut Modérateur Dernière intervention   7 940
       
      Apparemment le problème est côté client :
      https://community.openvpn.net/openvpn/wiki/259-tap-win32-adapter-is-not-coming-up-qinitialization-sequence-completed-with-errorsq
      0
    5. Dash226 Messages postés 19 Statut Membre
       
      bref j'ai tout essayé j'ai toujours le s mêmes souci sur mon Windows 8.1. J'ai monter une machine virtuelle Windows XP sous VirtualBox installer NMDVPN avec les fichiers clients et les mêmes config et tout fonctionne normalement. Sans doute un problème de compatibilité de Windows 8. En tout cas merci beaucoup pour ton aide :D
      0

Discussions similaires

Enlever ou désactiver le mode sécurisé Freebox
Cycy -
bazfile -

18 réponses
Tap Windows c'est quoi ?
Bijouxx -
Coucou -

8 réponses
Problème de VPN avec TAP-Windows sous Windows 10
Pouillout -
Vikki24 -

1 réponse
Leboncoin mode vacances : mettre en pause toutes ses annonce
Munk87 -
lebon -

4 réponses
TAP Windows Asapter V9
RibelluGaming -
brupala -

2 réponses