Connecté.. mais en faite non.

juin 2014 modifié dans Support technique
Bonsoir,

J'utilise actuellement hotspost SFR WIFI FON.

Quand je lance la connexion à un serveur (n'importe lequel) la barre de connexion reste fixée au milieu une vingtaine de secondes, puis le bouton "Deconnexion" apparaît, ce qui devrait me confirmer que je suis bien connecté, cependant rien n'as réellement changé, ma connexion est plus lente, mais mon IP est toujours la même et je peux voir sur des logiciels comme Mumble par exemple que je ne reçois aucun ping.

Cela fait plusieurs mis que j'ai ce problème, mais je n'étais pas venu le poster sur le forum, j'ai tenté d'utiliser un abonnement mais cela n'a rien changé.

Voici le journal de connexion si cela peut être utile avant qu'on me le demande ^^

Merci d'avance

FrozenWay version 1.6.5 ---------------------------------- Server: public-02-fr-08 Protocol: HTTPS ---------------------------------- Sat Jun 07 23:39:58 2014 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013 Sat Jun 07 23:39:59 2014 Control Channel Authentication: using 'C:/Users/Administrateur/Downloads/FrozenWay 1.6.5/FrozenWay 1.6.5/etc/keys/auth.key' as a OpenVPN static key file Sat Jun 07 23:39:59 2014 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Sat Jun 07 23:39:59 2014 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Sat Jun 07 23:39:59 2014 Socket Buffers: R=[8192->8192] S=[8192->8192] Sat Jun 07 23:39:59 2014 Attempting to establish TCP connection with [AF_INET]127.0.0.1:55519 Sat Jun 07 23:39:59 2014 TCP connection established with [AF_INET]127.0.0.1:55519 Sat Jun 07 23:39:59 2014 TCPv4_CLIENT link local: [undef] Sat Jun 07 23:39:59 2014 TCPv4_CLIENT link remote: [AF_INET]127.0.0.1:55519 Sat Jun 07 23:39:59 2014 TLS: Initial packet from [AF_INET]127.0.0.1:55519, sid=8cb7e850 7b6caf4c Sat Jun 07 23:40:00 2014 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com Sat Jun 07 23:40:00 2014 VERIFY OK: nsCertType=SERVER Sat Jun 07 23:40:00 2014 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com Sat Jun 07 23:40:01 2014 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key Sat Jun 07 23:40:01 2014 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Sat Jun 07 23:40:01 2014 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key Sat Jun 07 23:40:01 2014 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Sat Jun 07 23:40:01 2014 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA Sat Jun 07 23:40:01 2014 [FrozenWay] Peer Connection Initiated with [AF_INET]127.0.0.1:55519 Sat Jun 07 23:40:03 2014 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1) Sat Jun 07 23:40:03 2014 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.8.0.1,dhcp-option WINS 10.8.0.1,route 10.8.0.1,topology net30,socket-flags TCP_NODELAY,ifconfig 10.8.8.226 10.8.8.225' Sat Jun 07 23:40:03 2014 OPTIONS IMPORT: --socket-flags option modified Sat Jun 07 23:40:03 2014 OPTIONS IMPORT: --ifconfig/up options modified Sat Jun 07 23:40:03 2014 OPTIONS IMPORT: route options modified Sat Jun 07 23:40:03 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Sat Jun 07 23:40:03 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 Sat Jun 07 23:40:03 2014 open_tun, tt->ipv6=0 Sat Jun 07 23:40:03 2014 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{AAFD5150-F1FC-4B9A-8D40-8C7D549E3A2F}.tap Sat Jun 07 23:40:03 2014 TAP-Windows Driver Version 9.9 Sat Jun 07 23:40:03 2014 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.8.226/255.255.255.252 on interface {AAFD5150-F1FC-4B9A-8D40-8C7D549E3A2F} [DHCP-serv: 10.8.8.225, lease-time: 31536000] Sat Jun 07 23:40:03 2014 Successful ARP Flush on interface [27] {AAFD5150-F1FC-4B9A-8D40-8C7D549E3A2F} Sat Jun 07 23:40:08 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:08 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:13 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:13 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:14 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:14 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:15 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:15 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:16 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:16 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:18 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:18 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:19 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:19 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:20 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:20 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:21 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:21 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:23 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:23 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:24 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:24 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:25 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:25 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:26 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:26 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:27 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:27 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:29 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:29 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:30 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:30 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:31 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:31 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:32 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:32 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:33 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:33 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:34 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:34 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:35 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:35 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:36 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:36 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:37 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:37 2014 Route: Waiting for TUN/TAP interface to come up... Waking up the interface... Sat Jun 07 23:40:38 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down Sat Jun 07 23:40:38 2014 C:\Windows\system32\route.exe ADD 10.8.0.1 MASK 255.255.255.255 10.8.8.225 Sat Jun 07 23:40:38 2014 Warning: route gateway is not reachable on any active network adapters: 10.8.8.225 Sat Jun 07 23:40:38 2014 Route addition via IPAPI failed [adaptive] Sat Jun 07 23:40:38 2014 Route addition fallback to route.exe Sat Jun 07 23:40:38 2014 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem SYSTEM ROUTING TABLE 0.0.0.0 0.0.0.0 192.168.2.1 p=0 i=12 t=4 pr=3 a=326 h=0 m=50/0/0/0/0 10.5.18.148 255.255.255.252 10.5.18.150 p=0 i=27 t=3 pr=3 a=611104 h=0 m=286/0/0/0/0 10.5.18.150 255.255.255.255 10.5.18.150 p=0 i=27 t=3 pr=3 a=611104 h=0 m=286/0/0/0/0 10.5.18.151 255.255.255.255 10.5.18.150 p=0 i=27 t=3 pr=3 a=611104 h=0 m=286/0/0/0/0 10.8.0.1 255.255.255.255 10.8.8.225 p=0 i=12 t=4 pr=3 a=0 h=0 m=41/0/0/0/0 127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=694518 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=3 a=694518 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=3 a=694518 h=0 m=306/0/0/0/0 192.168.2.0 255.255.255.0 192.168.2.75 p=0 i=12 t=3 pr=3 a=694336 h=0 m=296/0/0/0/0 192.168.2.75 255.255.255.255 192.168.2.75 p=0 i=12 t=3 pr=3 a=694336 h=0 m=296/0/0/0/0 192.168.2.255 255.255.255.255 192.168.2.75 p=0 i=12 t=3 pr=3 a=694336 h=0 m=296/0/0/0/0 224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=694518 h=0 m=306/0/0/0/0 224.0.0.0 240.0.0.0 10.5.18.150 p=0 i=27 t=3 pr=3 a=694501 h=0 m=286/0/0/0/0 224.0.0.0 240.0.0.0 192.168.2.75 p=0 i=12 t=3 pr=3 a=694483 h=0 m=296/0/0/0/0 255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=694518 h=0 m=306/0/0/0/0 255.255.255.255 255.255.255.255 10.5.18.150 p=0 i=27 t=3 pr=3 a=694501 h=0 m=286/0/0/0/0 255.255.255.255 255.255.255.255 192.168.2.75 p=0 i=12 t=3 pr=3 a=694483 h=0 m=296/0/0/0/0 SYSTEM ADAPTER LIST Microsoft Virtual WiFi Miniport Adapter Index = 28 GUID = {14CB49D7-E132-4AB7-B0B2-FC68CD82BA80} IP = 0.0.0.0/0.0.0.0 MAC = c0:cb:38:97:b0:9a GATEWAY = 0.0.0.0/255.255.255.255 DHCP SERV = DHCP LEASE OBTAINED = Sat Jun 07 23:40:38 2014 DHCP LEASE EXPIRES = Sat Jun 07 23:40:38 2014 DNS SERV = TAP-Windows Adapter V9 Index = 27 GUID = {AAFD5150-F1FC-4B9A-8D40-8C7D549E3A2F} IP = 10.5.18.150/255.255.255.252 MAC = 00:ff:aa:fd:51:50 GATEWAY = 0.0.0.0/255.255.255.255 DHCP SERV = 10.5.18.149/255.255.255.255 DHCP LEASE OBTAINED = Sat May 31 21:55:34 2014 DHCP LEASE EXPIRES = Sun May 31 21:55:34 2015 DNS SERV = 10.5.0.1/255.255.255.255 Intel(R) 82577LC Gigabit Network Connection Index = 13 GUID = {D49F981A-D820-4746-ABC0-DBBBCD1AB1C5} IP = 0.0.0.0/0.0.0.0 MAC = 84:2b:2b:84:18:6c GATEWAY = 0.0.0.0/255.255.255.255 DHCP SERV = DHCP LEASE OBTAINED = Sat Jun 07 23:40:38 2014 DHCP LEASE EXPIRES = Sat Jun 07 23:40:38 2014 DNS SERV = Carte r�seau Broadcom 802.11n Index = 12 GUID = {D2349A56-6501-4FD2-A79B-DF5B9763CBC6} IP = 192.168.2.75/255.255.255.0 MAC = c0:cb:38:97:b0:9a GATEWAY = 192.168.2.1/255.255.255.255 DHCP SERV = 192.168.2.1/255.255.255.255 DHCP LEASE OBTAINED = Sat Jun 07 23:35:58 2014 DHCP LEASE EXPIRES = Sat Jun 07 23:55:58 2014 DNS SERV = 109.0.66.20/255.255.255.255 109.0.66.10/255.255.255.255 Sat Jun 07 23:40:38 2014 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv ) IPv4 routing table : 0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.75 9989 0.0.0.0 0.0.0.0 10.8.8.225 10.5.18.150 30 10.5.18.148 255.255.255.252 10.5.18.150 10.5.18.150 286 10.5.18.150 255.255.255.255 10.5.18.150 10.5.18.150 286 10.5.18.151 255.255.255.255 10.5.18.150 10.5.18.150 286 10.8.0.1 255.255.255.255 10.8.8.225 192.168.2.75 31 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 306 127.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 306 127.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306 176.31.132.91 255.255.255.255 192.168.2.1 192.168.2.75 30 192.168.2.0 255.255.255.0 192.168.2.75 192.168.2.75 286 192.168.2.75 255.255.255.255 192.168.2.75 192.168.2.75 286 192.168.2.255 255.255.255.255 192.168.2.75 192.168.2.75 286 224.0.0.0 240.0.0.0 127.0.0.1 127.0.0.1 306 224.0.0.0 240.0.0.0 10.5.18.150 10.5.18.150 286 224.0.0.0 240.0.0.0 192.168.2.75 192.168.2.75 286 255.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306 255.255.255.255 255.255.255.255 10.5.18.150 10.5.18.150 286 255.255.255.255 255.255.255.255 192.168.2.75 192.168.2.75 286

Réponses

  • J'ai le même problème, avec un journal similaire ( avec beaucoup trop de "Waking up the interface..")
    J'ai essayé, en OpenVPN, sur plusieurs serveur différent les 2 public et les 4 premium, mais rien ne change.
  • ça me le fait aussi, et j'ai trouvé comment résoudre ce souci : Essayez d'aller dans panneau de configuration => réseau et internet => connexions réseau, désactivez la connexion frozenway, puis réactivez la. Ensuite, connectez vous, ça devrait résoudre ce problème ;)
  • J'avais déjà essayé de désactivé la carte réseau virtuel, je l'avais même réinstallé.

    Je viens de réessayer au cas où, mais toujours au même point :/
  • Merci Dethane, je n'avais pas pensé à faire ça, ça a marché pour moi
  • Ok , any one speack english? i have a problem since 2 days ago , i`m connecting via SFR.FON and i have a huge ping near 900ms , i have the abonnament : Play-more, any one have the same problem whit the ping?
  • Maybe the problem is SFR FON.
    Can you make a speed test without FrozenWay and share us your result ? (http://www.speedtest.net/)
  • This problem is not about ping nor particular network/hotspot, it's a locally one.

    Avez-vous essayé de changer la méthode d'attribution de l'adresse IP dans les options réseau de FrozenWay ?
  • juin 2014 modifié
    http://www.speedtest.net/my-result/3557266374
    Yes the the hotspot is the problem ..... any one els got that in the past and got normal after?
    I think it start to get crowed the hot spot i use. :(
  • Rien ne change essayant toutes les méthodes d’attribution d'ip.

    De toutes façons j'ai ma box qui arrive demain, donc je n'aurais plus besoin d'utiliser Frozenway pour le moment ^^
Connectez-vous ou Inscrivez-vous pour répondre.