Jeux ne se lancent plus

septembre 2013 modifié dans Support technique
Bonjour, j'avais posté un sujet similaire il y a quelques jours, je pensais le problème résolu mais en fait il est toujours là.
Tout fonctionne normalement, jusqu'au moment ou, même sous frozenway, aucune application ne fonctionne (, WoW, LoL...), comme si je n'étais pas connecté à Frozenway. En ce moment même je ne peux pas me servir de frozenway correctement, alors que j'ai payé un abonnement.
Si quelqu'un pourrait m'aiguiller pour ne plus rencontrer ce problème, je lui en serai extrèmement reconnaissant.

D'avance merci, je reste à disposition si il faut plus de renseignements.

Je précise que ce problème est survenu soudainement, à une heure près je n'avais encore aucun problème.
Chose curieuse également, Teamspeak (qui ne passe pas en hotspot sans FW) lui fonctionne. En revanche tout ce qui est jeux ne passe pas (wow, lol, pokerstars, etc)


Réponses

  • Personne n'a une idée d'ou peut venir mon problème ? Une histoire de port ou quelquechose comme ca ? (Je n'ai rien touché ma configuration est en "par défaut")

  • Salut,

    Donne le journal de connexion stp.
  • Salut et merci de vous pencher sur mon problème.
    Voici le journal :

    FrozenWay version 1.6.4
    ----------------------------------
    Server: premium-01-fr-04
    Protocol: OpenVPN
    ----------------------------------
    Fri Sep 27 01:25:47 2013 OpenVPN 2.3.2 i686-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013

    Fri Sep 27 01:25:48 2013 Control Channel Authentication: using 'C:/Users/Jocelyn/Desktop/FrozenWay 1.6.4/etc/keys/auth.key' as a OpenVPN static key file
    Fri Sep 27 01:25:48 2013 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Fri Sep 27 01:25:48 2013 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Fri Sep 27 01:25:48 2013 Socket Buffers: R=[8192->8192] S=[8192->8192]
    Fri Sep 27 01:25:48 2013 Attempting to establish TCP connection with [AF_INET]5.135.109.175:443

    Fri Sep 27 01:25:48 2013 TCP connection established with [AF_INET]5.135.109.175:443
    Fri Sep 27 01:25:48 2013 TCPv4_CLIENT link local: [undef]
    Fri Sep 27 01:25:48 2013 TCPv4_CLIENT link remote: [AF_INET]5.135.109.175:443
    Fri Sep 27 01:25:48 2013 TLS: Initial packet from [AF_INET]5.135.109.175:443, sid=8fb58f64 8519a418

    Fri Sep 27 01:25:48 2013 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com
    Fri Sep 27 01:25:48 2013 VERIFY OK: nsCertType=SERVER
    Fri Sep 27 01:25:48 2013 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com

    Fri Sep 27 01:25:48 2013 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Fri Sep 27 01:25:48 2013 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Fri Sep 27 01:25:48 2013 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Fri Sep 27 01:25:48 2013 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Fri Sep 27 01:25:48 2013 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
    Fri Sep 27 01:25:48 2013 [FrozenWay] Peer Connection Initiated with [AF_INET]5.135.109.175:443

    Fri Sep 27 01:25:51 2013 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)
    Fri Sep 27 01:25:51 2013 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.4.0.1,dhcp-option WINS 10.4.0.1,route 10.4.0.1,topology net30,socket-flags TCP_NODELAY,ifconfig 10.4.0.162 10.4.0.161'
    Fri Sep 27 01:25:51 2013 OPTIONS IMPORT: --socket-flags option modified
    Fri Sep 27 01:25:51 2013 OPTIONS IMPORT: --ifconfig/up options modified
    Fri Sep 27 01:25:51 2013 OPTIONS IMPORT: route options modified
    Fri Sep 27 01:25:51 2013 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
    Fri Sep 27 01:25:51 2013 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
    Fri Sep 27 01:25:51 2013 open_tun, tt->ipv6=0
    Fri Sep 27 01:25:51 2013 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{48C3E085-EDBD-459A-BA7D-855AEF57C3D5}.tap
    Fri Sep 27 01:25:51 2013 TAP-Windows Driver Version 9.9
    Fri Sep 27 01:25:51 2013 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.4.0.162/255.255.255.252 on interface {48C3E085-EDBD-459A-BA7D-855AEF57C3D5} [DHCP-serv: 10.4.0.161, lease-time: 31536000]
    Fri Sep 27 01:25:51 2013 Successful ARP Flush on interface [15] {48C3E085-EDBD-459A-BA7D-855AEF57C3D5}

    Fri Sep 27 01:25:56 2013 TEST ROUTES: 1/1 succeeded len=1 ret=1 a=0 u/d=up
    Fri Sep 27 01:25:56 2013 C:\Windows\system32\route.exe ADD 10.4.0.1 MASK 255.255.255.255 10.4.0.161
    Fri Sep 27 01:25:56 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
    Fri Sep 27 01:25:56 2013 Route addition via IPAPI succeeded [adaptive]
    Fri Sep 27 01:25:56 2013 Initialization Sequence Completed

    IPv4 routing table :
    0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.66 9999
    0.0.0.0 0.0.0.0 10.4.0.161 10.4.0.162 30
    5.135.109.175 255.255.255.255 192.168.2.1 192.168.2.66 25
    10.4.0.1 255.255.255.255 10.4.0.161 10.4.0.162 30
    10.4.0.160 255.255.255.252 10.4.0.162 10.4.0.162 286
    10.4.0.162 255.255.255.255 10.4.0.162 10.4.0.162 286
    10.4.0.163 255.255.255.255 10.4.0.162 10.4.0.162 286
    62.122.9.80 255.255.255.255 192.168.2.1 192.168.2.66 25
    65.55.57.27 255.255.255.255 192.168.2.1 192.168.2.66 25
    77.67.11.90 255.255.255.255 192.168.2.1 192.168.2.66 25
    77.67.11.131 255.255.255.255 192.168.2.1 192.168.2.66 25
    77.67.21.41 255.255.255.255 192.168.2.1 192.168.2.66 25
    77.67.21.48 255.255.255.255 192.168.2.1 192.168.2.66 25
    86.65.30.199 255.255.255.255 192.168.2.1 192.168.2.66 25
    109.0.66.10 255.255.255.255 192.168.2.1 192.168.2.66 25
    109.0.66.20 255.255.255.255 192.168.2.1 192.168.2.66 25
    109.0.74.75 255.255.255.255 192.168.2.1 192.168.2.66 25
    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
    173.194.78.99 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.78.103 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.78.104 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.78.105 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.78.106 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.78.147 255.255.255.255 192.168.2.1 192.168.2.66 25
    192.168.2.0 255.255.255.0 192.168.2.66 192.168.2.66 281
    192.168.2.66 255.255.255.255 192.168.2.66 192.168.2.66 281
    192.168.2.255 255.255.255.255 192.168.2.66 192.168.2.66 281
    193.27.194.177 255.255.255.255 192.168.2.1 127.0.0.1 25
    213.186.33.87 255.255.255.255 192.168.2.1 192.168.2.66 25
    217.109.56.160 255.255.255.255 192.168.2.1 192.168.2.66 25
    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.4.0.162 10.4.0.162 286
    224.0.0.0 240.0.0.0 192.168.2.66 192.168.2.66 281
    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.4.0.162 10.4.0.162 286
    255.255.255.255 255.255.255.255 192.168.2.66 192.168.2.66 281
  • Le journal est bon. Une fois connecté va sur http://www.monip.org et donne le résultat stp.

    Quel est l'erreur de WoW ?
  • Bonjour Atomik et mes excuses pour le délai de réponse. J'ai fait une pause avec tout ça parceque l'informatique reste une grande énigme pour moi... Tout marche bien et puis d'un coup ça plante, sans pour autant n'avoir rien touché... Bref.

    Voici le résultat de ma connexion sur http://www.monip.org/

    IP : 176.31.61.21
    premium-03-fr-02.fwpremium.com

    Pas de proxy détecté - No Proxy detected

    Mon souci avait donc disparu, en parcourant le forum j'ai tout essayé et finalement le décochage d'un paramètre Options Internet "Détecter automatiquement la connexion" avait réglé le problème...

    Aujourd'hui le souci recommence (rapport avec la nouvelle version de FW?) je suis connecté à internet (via hotspot sfr wifi fon) , je suis connecté à frozenway (premium3), je peux me connecter par exemple à Teamspeak, qui ne passe pas normalement sans FW, mais impossible de me connecter à Wow. Le launcher se lance donc normalement ça passe par FW, le jeu se lance je tape mon mot de passe, et aucune réponse cela reste bloqué sur "Connexion" .

    Je précise que je joue depuis longtemps de la sorte, qu'en temps normal tout fonctionne à merveille (60ms en raid)

    Mais là , je suis un peu dérouté ...
    En parlant de route, voici le journal de mes dernières tentatives... Merci d'avance pour ton aide.

    FrozenWay version 1.6.5
    ----------------------------------
    Server: premium-03-fr-02
    Protocol: OpenVPN
    ----------------------------------
    Tue Oct 01 21:07:22 2013 OpenVPN 2.3.2 i686-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013

    Tue Oct 01 21:07:23 2013 Control Channel Authentication: using 'C:/Users/Jocelyn/Desktop/FrozenWay 1.6.5/etc/keys/auth.key' as a OpenVPN static key file
    Tue Oct 01 21:07:23 2013 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Tue Oct 01 21:07:23 2013 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Tue Oct 01 21:07:23 2013 Socket Buffers: R=[8192->8192] S=[8192->8192]
    Tue Oct 01 21:07:23 2013 Attempting to establish TCP connection with [AF_INET]176.31.61.21:443

    Tue Oct 01 21:07:23 2013 TCP connection established with [AF_INET]176.31.61.21:443
    Tue Oct 01 21:07:23 2013 TCPv4_CLIENT link local: [undef]
    Tue Oct 01 21:07:23 2013 TCPv4_CLIENT link remote: [AF_INET]176.31.61.21:443
    Tue Oct 01 21:07:23 2013 TLS: Initial packet from [AF_INET]176.31.61.21:443, sid=55a8b73b 5e6ebdf9

    Tue Oct 01 21:07:23 2013 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com
    Tue Oct 01 21:07:23 2013 VERIFY OK: nsCertType=SERVER
    Tue Oct 01 21:07:23 2013 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com

    Tue Oct 01 21:07:23 2013 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Tue Oct 01 21:07:23 2013 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Tue Oct 01 21:07:23 2013 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Tue Oct 01 21:07:23 2013 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Tue Oct 01 21:07:23 2013 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
    Tue Oct 01 21:07:23 2013 [FrozenWay] Peer Connection Initiated with [AF_INET]176.31.61.21:443

    Tue Oct 01 21:07:25 2013 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)

    Tue Oct 01 21:07:25 2013 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.2.0.1,dhcp-option WINS 10.2.0.1,route 10.2.0.1,topology net30,socket-flags TCP_NODELAY,ifconfig 10.2.0.218 10.2.0.217'
    Tue Oct 01 21:07:25 2013 OPTIONS IMPORT: --socket-flags option modified
    Tue Oct 01 21:07:25 2013 OPTIONS IMPORT: --ifconfig/up options modified
    Tue Oct 01 21:07:25 2013 OPTIONS IMPORT: route options modified
    Tue Oct 01 21:07:25 2013 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
    Tue Oct 01 21:07:25 2013 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
    Tue Oct 01 21:07:25 2013 open_tun, tt->ipv6=0
    Tue Oct 01 21:07:25 2013 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{48C3E085-EDBD-459A-BA7D-855AEF57C3D5}.tap
    Tue Oct 01 21:07:25 2013 TAP-Windows Driver Version 9.9
    Tue Oct 01 21:07:25 2013 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.2.0.218/255.255.255.252 on interface {48C3E085-EDBD-459A-BA7D-855AEF57C3D5} [DHCP-serv: 10.2.0.217, lease-time: 31536000]
    Tue Oct 01 21:07:25 2013 Successful ARP Flush on interface [14] {48C3E085-EDBD-459A-BA7D-855AEF57C3D5}

    Tue Oct 01 21:07:31 2013 TEST ROUTES: 1/1 succeeded len=1 ret=1 a=0 u/d=up
    Tue Oct 01 21:07:31 2013 C:\Windows\system32\route.exe ADD 10.2.0.1 MASK 255.255.255.255 10.2.0.217
    Tue Oct 01 21:07:31 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
    Tue Oct 01 21:07:31 2013 Route addition via IPAPI succeeded [adaptive]
    Tue Oct 01 21:07:31 2013 Initialization Sequence Completed

    IPv4 routing table :
    0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.67 9999
    0.0.0.0 0.0.0.0 10.2.0.217 10.2.0.218 30
    10.2.0.1 255.255.255.255 10.2.0.217 10.2.0.218 30
    10.2.0.216 255.255.255.252 10.2.0.218 10.2.0.218 286
    10.2.0.218 255.255.255.255 10.2.0.218 10.2.0.218 286
    10.2.0.219 255.255.255.255 10.2.0.218 10.2.0.218 286
    23.14.93.71 255.255.255.255 192.168.2.1 192.168.2.67 25
    23.14.93.97 255.255.255.255 192.168.2.1 192.168.2.67 25
    62.122.9.80 255.255.255.255 192.168.2.1 192.168.2.67 25
    65.55.57.27 255.255.255.255 192.168.2.1 192.168.2.67 25
    86.65.30.199 255.255.255.255 192.168.2.1 192.168.2.67 25
    109.0.66.10 255.255.255.255 192.168.2.1 192.168.2.67 25
    109.0.66.20 255.255.255.255 192.168.2.1 192.168.2.67 25
    109.0.74.75 255.255.255.255 192.168.2.1 192.168.2.67 25
    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
    173.194.66.99 255.255.255.255 192.168.2.1 192.168.2.67 25
    173.194.66.103 255.255.255.255 192.168.2.1 192.168.2.67 25
    173.194.66.104 255.255.255.255 192.168.2.1 192.168.2.67 25
    173.194.66.105 255.255.255.255 192.168.2.1 192.168.2.67 25
    173.194.66.106 255.255.255.255 192.168.2.1 192.168.2.67 25
    173.194.66.147 255.255.255.255 192.168.2.1 192.168.2.67 25
    176.31.61.21 255.255.255.255 192.168.2.1 192.168.2.67 25
    192.168.2.0 255.255.255.0 192.168.2.67 192.168.2.67 281
    192.168.2.67 255.255.255.255 192.168.2.67 192.168.2.67 281
    192.168.2.255 255.255.255.255 192.168.2.67 192.168.2.67 281
    193.27.194.177 255.255.255.255 192.168.2.1 192.168.2.67 25
    195.10.8.154 255.255.255.255 192.168.2.1 192.168.2.67 25
    195.10.9.9 255.255.255.255 192.168.2.1 192.168.2.67 25
    213.186.33.87 255.255.255.255 192.168.2.1 192.168.2.67 25
    217.109.56.160 255.255.255.255 192.168.2.1 192.168.2.67 25
    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.2.0.218 10.2.0.218 286
    224.0.0.0 240.0.0.0 192.168.2.67 192.168.2.67 281
    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.2.0.218 10.2.0.218 286
    255.255.255.255 255.255.255.255 192.168.2.67 192.168.2.67 281
    Tue Oct 01 21:08:53 2013 [FrozenWay] Inactivity timeout (--ping-exit), exiting

    Tue Oct 01 21:08:53 2013 C:\Windows\system32\route.exe DELETE 10.2.0.1 MASK 255.255.255.255 10.2.0.217
    Tue Oct 01 21:08:53 2013 Route deletion via IPAPI succeeded [adaptive]
    Tue Oct 01 21:08:53 2013 Closing TUN/TAP interface
    Tue Oct 01 21:08:53 2013 SIGTERM[soft,ping-exit] received, process exiting

    FrozenWay version 1.6.5
    ----------------------------------
    Server: premium-03-fr-02
    Protocol: OpenVPN
    ----------------------------------
    Tue Oct 01 21:08:56 2013 OpenVPN 2.3.2 i686-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013

    Tue Oct 01 21:08:57 2013 Control Channel Authentication: using 'C:/Users/Jocelyn/Desktop/FrozenWay 1.6.5/etc/keys/auth.key' as a OpenVPN static key file
    Tue Oct 01 21:08:57 2013 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Tue Oct 01 21:08:57 2013 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Tue Oct 01 21:08:57 2013 Socket Buffers: R=[8192->8192] S=[8192->8192]
    Tue Oct 01 21:08:57 2013 Attempting to establish TCP connection with [AF_INET]176.31.61.21:443

    Tue Oct 01 21:08:57 2013 TCP connection established with [AF_INET]176.31.61.21:443
    Tue Oct 01 21:08:57 2013 TCPv4_CLIENT link local: [undef]
    Tue Oct 01 21:08:57 2013 TCPv4_CLIENT link remote: [AF_INET]176.31.61.21:443
    Tue Oct 01 21:08:57 2013 TLS: Initial packet from [AF_INET]176.31.61.21:443, sid=0923b833 e4471cf5

    Tue Oct 01 21:08:58 2013 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com
    Tue Oct 01 21:08:58 2013 VERIFY OK: nsCertType=SERVER
    Tue Oct 01 21:08:58 2013 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com

    Tue Oct 01 21:08:58 2013 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Tue Oct 01 21:08:58 2013 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Tue Oct 01 21:08:58 2013 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Tue Oct 01 21:08:58 2013 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Tue Oct 01 21:08:58 2013 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
    Tue Oct 01 21:08:58 2013 [FrozenWay] Peer Connection Initiated with [AF_INET]176.31.61.21:443

    Tue Oct 01 21:09:01 2013 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)
    Tue Oct 01 21:09:01 2013 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.2.0.1,dhcp-option WINS 10.2.0.1,route 10.2.0.1,topology net30,socket-flags TCP_NODELAY,ifconfig 10.2.0.218 10.2.0.217'
    Tue Oct 01 21:09:01 2013 OPTIONS IMPORT: --socket-flags option modified
    Tue Oct 01 21:09:01 2013 OPTIONS IMPORT: --ifconfig/up options modified
    Tue Oct 01 21:09:01 2013 OPTIONS IMPORT: route options modified
    Tue Oct 01 21:09:01 2013 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
    Tue Oct 01 21:09:01 2013 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
    Tue Oct 01 21:09:01 2013 open_tun, tt->ipv6=0
    Tue Oct 01 21:09:01 2013 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{48C3E085-EDBD-459A-BA7D-855AEF57C3D5}.tap

    Tue Oct 01 21:09:01 2013 TAP-Windows Driver Version 9.9
    Tue Oct 01 21:09:01 2013 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.2.0.218/255.255.255.252 on interface {48C3E085-EDBD-459A-BA7D-855AEF57C3D5} [DHCP-serv: 10.2.0.217, lease-time: 31536000]
    Tue Oct 01 21:09:01 2013 Successful ARP Flush on interface [14] {48C3E085-EDBD-459A-BA7D-855AEF57C3D5}

    Tue Oct 01 21:09:06 2013 TEST ROUTES: 1/1 succeeded len=1 ret=1 a=0 u/d=up
    Tue Oct 01 21:09:06 2013 C:\Windows\system32\route.exe ADD 10.2.0.1 MASK 255.255.255.255 10.2.0.217
    Tue Oct 01 21:09:06 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
    Tue Oct 01 21:09:06 2013 Route addition via IPAPI succeeded [adaptive]
    Tue Oct 01 21:09:06 2013 Initialization Sequence Completed

    IPv4 routing table :
    0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.67 9999
    0.0.0.0 0.0.0.0 10.2.0.217 10.2.0.218 30
    10.2.0.1 255.255.255.255 10.2.0.217 10.2.0.218 30
    10.2.0.216 255.255.255.252 10.2.0.218 10.2.0.218 286
    10.2.0.218 255.255.255.255 10.2.0.218 10.2.0.218 286
    10.2.0.219 255.255.255.255 10.2.0.218 10.2.0.218 286
    62.122.9.80 255.255.255.255 192.168.2.1 192.168.2.67 25
    64.4.11.42 255.255.255.255 192.168.2.1 192.168.2.67 25
    77.67.20.41 255.255.255.255 192.168.2.1 192.168.2.67 25
    77.67.20.42 255.255.255.255 192.168.2.1 192.168.2.67 25
    86.65.30.199 255.255.255.255 192.168.2.1 192.168.2.67 25
    92.123.72.134 255.255.255.255 192.168.2.1 192.168.2.67 25
    92.123.72.198 255.255.255.255 192.168.2.1 192.168.2.67 25
    109.0.66.10 255.255.255.255 192.168.2.1 192.168.2.67 25
    109.0.66.20 255.255.255.255 192.168.2.1 192.168.2.67 25
    109.0.74.75 255.255.255.255 192.168.2.1 192.168.2.67 25
    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
    173.194.78.99 255.255.255.255 192.168.2.1 192.168.2.67 25
    173.194.78.103 255.255.255.255 192.168.2.1 192.168.2.67 25
    173.194.78.104 255.255.255.255 192.168.2.1 192.168.2.67 25
    173.194.78.105 255.255.255.255 192.168.2.1 192.168.2.67 25
    173.194.78.106 255.255.255.255 192.168.2.1 192.168.2.67 25
    173.194.78.147 255.255.255.255 192.168.2.1 192.168.2.67 25
    176.31.61.21 255.255.255.255 192.168.2.1 192.168.2.67 25
    192.168.2.0 255.255.255.0 192.168.2.67 192.168.2.67 281
    192.168.2.67 255.255.255.255 192.168.2.67 192.168.2.67 281
    192.168.2.255 255.255.255.255 192.168.2.67 192.168.2.67 281
    193.27.194.177 255.255.255.255 192.168.2.1 192.168.2.67 25
    213.186.33.87 255.255.255.255 192.168.2.1 192.168.2.67 25
    217.109.56.160 255.255.255.255 192.168.2.1 192.168.2.67 25
    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.2.0.218 10.2.0.218 286
    224.0.0.0 240.0.0.0 192.168.2.67 192.168.2.67 281
    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.2.0.218 10.2.0.218 286
    255.255.255.255 255.255.255.255 192.168.2.67 192.168.2.67 281
  • C'est étrange... La qualité du signal Wifi est bonne ? Je vois que tu as eu une déconnexion dans le journal (au bout d'une minute de connexion).
  • octobre 2013 modifié
    Je n'ai habituellement que très peu de déconnexions.
    Je viens de re tester ce matin et je peux lancer league of legend, Teamspeak, pokerstars, mais pas WoW, qui reste toujours bloqué sur "Connexion"

    J'ai l'impression que ça pourrait venir de "Teredo" qui est rajouté automatiquement dans ma liste de ports, même si je le supprime de la liste. Qu'est ce que c'est exactement, est ce important ? Le souci pourrait venir de là, je fais bien de le supprimer ?


    Voici le journal de ce matin ;

    FrozenWay version 1.6.5
    ----------------------------------
    Server: premium-03-fr-02
    Protocol: OpenVPN
    ----------------------------------
    Wed Oct 02 07:08:54 2013 OpenVPN 2.3.2 i686-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013

    Wed Oct 02 07:08:55 2013 Control Channel Authentication: using 'C:/Users/Jocelyn/Desktop/FrozenWay 1.6.5/etc/keys/auth.key' as a OpenVPN static key file
    Wed Oct 02 07:08:55 2013 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Wed Oct 02 07:08:55 2013 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Wed Oct 02 07:08:55 2013 Socket Buffers: R=[8192->8192] S=[8192->8192]
    Wed Oct 02 07:08:55 2013 Attempting to establish TCP connection with [AF_INET]176.31.61.21:443

    Wed Oct 02 07:08:55 2013 TCP connection established with [AF_INET]176.31.61.21:443
    Wed Oct 02 07:08:55 2013 TCPv4_CLIENT link local: [undef]
    Wed Oct 02 07:08:55 2013 TCPv4_CLIENT link remote: [AF_INET]176.31.61.21:443
    Wed Oct 02 07:08:55 2013 TLS: Initial packet from [AF_INET]176.31.61.21:443, sid=124a1d39 42983e52

    Wed Oct 02 07:08:56 2013 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com
    Wed Oct 02 07:08:56 2013 VERIFY OK: nsCertType=SERVER
    Wed Oct 02 07:08:56 2013 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com

    Wed Oct 02 07:08:56 2013 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Wed Oct 02 07:08:56 2013 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Wed Oct 02 07:08:56 2013 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Wed Oct 02 07:08:56 2013 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Wed Oct 02 07:08:56 2013 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
    Wed Oct 02 07:08:56 2013 [FrozenWay] Peer Connection Initiated with [AF_INET]176.31.61.21:443

    Wed Oct 02 07:08:59 2013 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)
    Wed Oct 02 07:08:59 2013 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.2.0.1,dhcp-option WINS 10.2.0.1,route 10.2.0.1,topology net30,socket-flags TCP_NODELAY,ifconfig 10.2.0.18 10.2.0.17'
    Wed Oct 02 07:08:59 2013 OPTIONS IMPORT: --socket-flags option modified
    Wed Oct 02 07:08:59 2013 OPTIONS IMPORT: --ifconfig/up options modified
    Wed Oct 02 07:08:59 2013 OPTIONS IMPORT: route options modified
    Wed Oct 02 07:08:59 2013 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
    Wed Oct 02 07:08:59 2013 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
    Wed Oct 02 07:08:59 2013 open_tun, tt->ipv6=0
    Wed Oct 02 07:08:59 2013 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{48C3E085-EDBD-459A-BA7D-855AEF57C3D5}.tap
    Wed Oct 02 07:08:59 2013 TAP-Windows Driver Version 9.9
    Wed Oct 02 07:08:59 2013 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.2.0.18/255.255.255.252 on interface {48C3E085-EDBD-459A-BA7D-855AEF57C3D5} [DHCP-serv: 10.2.0.17, lease-time: 31536000]
    Wed Oct 02 07:08:59 2013 Successful ARP Flush on interface [14] {48C3E085-EDBD-459A-BA7D-855AEF57C3D5}

    Wed Oct 02 07:09:04 2013 TEST ROUTES: 1/1 succeeded len=1 ret=1 a=0 u/d=up
    Wed Oct 02 07:09:04 2013 C:\Windows\system32\route.exe ADD 10.2.0.1 MASK 255.255.255.255 10.2.0.17
    Wed Oct 02 07:09:04 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
    Wed Oct 02 07:09:04 2013 Route addition via IPAPI succeeded [adaptive]
    Wed Oct 02 07:09:04 2013 Initialization Sequence Completed

    IPv4 routing table :
    0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.66 9999
    0.0.0.0 0.0.0.0 10.2.0.17 10.2.0.18 30
    10.2.0.1 255.255.255.255 10.2.0.17 10.2.0.18 30
    10.2.0.16 255.255.255.252 10.2.0.18 10.2.0.18 286
    10.2.0.18 255.255.255.255 10.2.0.18 10.2.0.18 286
    10.2.0.19 255.255.255.255 10.2.0.18 10.2.0.18 286
    62.122.9.80 255.255.255.255 192.168.2.1 192.168.2.66 25
    64.4.11.42 255.255.255.255 192.168.2.1 192.168.2.66 25
    77.67.11.90 255.255.255.255 192.168.2.1 192.168.2.66 25
    77.67.11.131 255.255.255.255 192.168.2.1 192.168.2.66 25
    86.65.30.199 255.255.255.255 192.168.2.1 192.168.2.66 25
    109.0.66.10 255.255.255.255 192.168.2.1 192.168.2.66 25
    109.0.66.20 255.255.255.255 192.168.2.1 192.168.2.66 25
    109.0.74.75 255.255.255.255 192.168.2.1 192.168.2.66 25
    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
    173.194.66.99 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.66.103 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.66.104 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.66.105 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.66.106 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.66.147 255.255.255.255 192.168.2.1 192.168.2.66 25
    176.31.61.21 255.255.255.255 192.168.2.1 192.168.2.66 25
    192.168.2.0 255.255.255.0 192.168.2.66 192.168.2.66 281
    192.168.2.66 255.255.255.255 192.168.2.66 192.168.2.66 281
    192.168.2.255 255.255.255.255 192.168.2.66 192.168.2.66 281
    193.27.194.177 255.255.255.255 192.168.2.1 192.168.2.66 25
    213.186.33.87 255.255.255.255 192.168.2.1 192.168.2.66 25
    213.254.248.155 255.255.255.255 192.168.2.1 192.168.2.66 25
    213.254.248.187 255.255.255.255 192.168.2.1 192.168.2.66 25
    217.109.56.160 255.255.255.255 192.168.2.1 192.168.2.66 25
    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.2.0.18 10.2.0.18 286
    224.0.0.0 240.0.0.0 192.168.2.66 192.168.2.66 281
    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.2.0.18 10.2.0.18 286
    255.255.255.255 255.255.255.255 192.168.2.66 192.168.2.66 281

  • Ça n'a rien à voir avec Teredo, c'est un service Windows utilisé pour encapsuler l'IPv6 dans de l'IPv4 pour la transition. Il est rajouté par Windows automatiquement par UPnP d'où l'affichage dans la liste des ports. Tu peux le désactiver dans la liste des services Windows.

    J'ai essayé de me connecter au premium-03-fr-02, comme toi, et de lancer WoW et ça marche très bien : / Tu n'as pas installé récemment un logiciel qui touche au réseau ?
  • J'ai pu à nouveau jouer ce soir durant 3 voir 4h. Je me déconnecte de FW pour faire autre chose sur le net, je veux re tenter, et ça recommence, impossible de me connecter à wow ou à lol.... Je ne comprends vraiment pas et je crois que c'est ça qui m'énerve le plus...

    Pour te répondre non je n'ai pas installé de logiciel qui touche au réseau récemment.
    Je passe par un répeteur wifi, cela peut il venir de la ? Je ne pense pas car toujours utilisé mais sait on jamais. Je désespère un peu là.

    Je te donne les routes de mon dernier essai :

    FrozenWay version 1.6.5
    ----------------------------------
    Server: premium-03-fr-01
    Protocol: OpenVPN
    ----------------------------------
    Thu Oct 03 02:52:23 2013 OpenVPN 2.3.2 i686-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013

    Thu Oct 03 02:52:24 2013 Control Channel Authentication: using 'C:/Users/Jocelyn/Desktop/FrozenWay 1.6.5/etc/keys/auth.key' as a OpenVPN static key file
    Thu Oct 03 02:52:24 2013 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Thu Oct 03 02:52:24 2013 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Thu Oct 03 02:52:24 2013 Socket Buffers: R=[8192->8192] S=[8192->8192]
    Thu Oct 03 02:52:24 2013 Attempting to establish TCP connection with [AF_INET]176.31.61.20:443

    Thu Oct 03 02:52:24 2013 TCP connection established with [AF_INET]176.31.61.20:443
    Thu Oct 03 02:52:24 2013 TCPv4_CLIENT link local: [undef]
    Thu Oct 03 02:52:24 2013 TCPv4_CLIENT link remote: [AF_INET]176.31.61.20:443

    Thu Oct 03 02:52:24 2013 TLS: Initial packet from [AF_INET]176.31.61.20:443, sid=66a62fba 17d657f4

    Thu Oct 03 02:52:25 2013 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com
    Thu Oct 03 02:52:25 2013 VERIFY OK: nsCertType=SERVER
    Thu Oct 03 02:52:25 2013 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com

    Thu Oct 03 02:52:26 2013 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Thu Oct 03 02:52:26 2013 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Thu Oct 03 02:52:26 2013 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Thu Oct 03 02:52:26 2013 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Thu Oct 03 02:52:26 2013 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
    Thu Oct 03 02:52:26 2013 [FrozenWay] Peer Connection Initiated with [AF_INET]176.31.61.20:443

    Thu Oct 03 02:52:28 2013 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)

    Thu Oct 03 02:52:28 2013 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.1.0.1,dhcp-option WINS 10.1.0.1,route 10.1.0.1,topology net30,socket-flags TCP_NODELAY,ifconfig 10.1.0.18 10.1.0.17'
    Thu Oct 03 02:52:28 2013 OPTIONS IMPORT: --socket-flags option modified
    Thu Oct 03 02:52:28 2013 OPTIONS IMPORT: --ifconfig/up options modified
    Thu Oct 03 02:52:28 2013 OPTIONS IMPORT: route options modified
    Thu Oct 03 02:52:28 2013 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
    Thu Oct 03 02:52:28 2013 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
    Thu Oct 03 02:52:28 2013 open_tun, tt->ipv6=0
    Thu Oct 03 02:52:28 2013 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{48C3E085-EDBD-459A-BA7D-855AEF57C3D5}.tap
    Thu Oct 03 02:52:28 2013 TAP-Windows Driver Version 9.9
    Thu Oct 03 02:52:28 2013 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.1.0.18/255.255.255.252 on interface {48C3E085-EDBD-459A-BA7D-855AEF57C3D5} [DHCP-serv: 10.1.0.17, lease-time: 31536000]
    Thu Oct 03 02:52:28 2013 Successful ARP Flush on interface [14] {48C3E085-EDBD-459A-BA7D-855AEF57C3D5}

    Thu Oct 03 02:52:33 2013 TEST ROUTES: 1/1 succeeded len=1 ret=1 a=0 u/d=up
    Thu Oct 03 02:52:33 2013 C:\Windows\system32\route.exe ADD 10.1.0.1 MASK 255.255.255.255 10.1.0.17
    Thu Oct 03 02:52:33 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
    Thu Oct 03 02:52:33 2013 Route addition via IPAPI succeeded [adaptive]
    Thu Oct 03 02:52:33 2013 Initialization Sequence Completed

    IPv4 routing table :
    0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.66 9999
    0.0.0.0 0.0.0.0 10.1.0.17 10.1.0.18 30
    10.1.0.1 255.255.255.255 10.1.0.17 10.1.0.18 30
    10.1.0.16 255.255.255.252 10.1.0.18 10.1.0.18 286
    10.1.0.18 255.255.255.255 10.1.0.18 10.1.0.18 286
    10.1.0.19 255.255.255.255 10.1.0.18 10.1.0.18 286
    62.122.9.80 255.255.255.255 192.168.2.1 192.168.2.66 25
    65.55.57.27 255.255.255.255 192.168.2.1 192.168.2.66 25
    77.67.11.90 255.255.255.255 192.168.2.1 192.168.2.66 25
    77.67.11.131 255.255.255.255 192.168.2.1 192.168.2.66 25
    86.65.30.199 255.255.255.255 192.168.2.1 192.168.2.66 25
    109.0.66.10 255.255.255.255 192.168.2.1 192.168.2.66 25
    109.0.66.20 255.255.255.255 192.168.2.1 192.168.2.66 25
    109.0.74.75 255.255.255.255 192.168.2.1 192.168.2.66 25
    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
    173.194.66.99 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.66.103 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.66.104 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.66.105 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.66.106 255.255.255.255 192.168.2.1 192.168.2.66 25
    173.194.66.147 255.255.255.255 192.168.2.1 192.168.2.66 25
    176.31.61.20 255.255.255.255 192.168.2.1 192.168.2.66 25
    192.168.2.0 255.255.255.0 192.168.2.66 192.168.2.66 281
    192.168.2.66 255.255.255.255 192.168.2.66 192.168.2.66 281
    192.168.2.255 255.255.255.255 192.168.2.66 192.168.2.66 281
    193.27.194.177 255.255.255.255 192.168.2.1 192.168.2.66 25
    204.79.197.200 255.255.255.255 192.168.2.1 192.168.2.66 25
    213.186.33.87 255.255.255.255 192.168.2.1 192.168.2.66 25
    217.109.56.160 255.255.255.255 192.168.2.1 192.168.2.66 25
    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.1.0.18 10.1.0.18 286
    224.0.0.0 240.0.0.0 192.168.2.66 192.168.2.66 281
    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.1.0.18 10.1.0.18 286
    255.255.255.255 255.255.255.255 192.168.2.66 192.168.2.66 281



  • Si tu enlèves toutes les exceptions (redirections statiques) et que tu recoches "Utiliser FrozenWay comme serveur DNS", est-ce que ça change quelque chose ?
Connectez-vous ou Inscrivez-vous pour répondre.