[Résolu] Plus possible de jouer a wow via frozenway

janvier 2015 modifié dans Support technique
voila ca fait quelque semaine que je joue a wow via fozenway mais depuis hier j'ai une perte de co de frozenway apres le lancement de wow.

voici le journal:
FrozenWay version 1.6.5
----------------------------------
Server: premium-04-fr-03
Protocol: OpenVPN
----------------------------------
Sun Jan 11 09:20:31 2015 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013

Sun Jan 11 09:20:31 2015 Control Channel Authentication: using 'C:/Users/remy/Documents/FrozenWay 1.6.5/etc/keys/auth.key' as a OpenVPN static key file
Sun Jan 11 09:20:31 2015 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan 11 09:20:31 2015 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan 11 09:20:31 2015 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Jan 11 09:20:31 2015 Attempting to establish TCP connection with [AF_INET]212.129.3.4:443

Sun Jan 11 09:20:31 2015 TCP connection established with [AF_INET]212.129.3.4:443
Sun Jan 11 09:20:31 2015 TCPv4_CLIENT link local: [undef]
Sun Jan 11 09:20:31 2015 TCPv4_CLIENT link remote: [AF_INET]212.129.3.4:443
Sun Jan 11 09:20:31 2015 TLS: Initial packet from [AF_INET]212.129.3.4:443, sid=e489cdcc 30126353

Sun Jan 11 09:20:32 2015 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com
Sun Jan 11 09:20:32 2015 VERIFY OK: nsCertType=SERVER
Sun Jan 11 09:20:32 2015 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com

Sun Jan 11 09:20:32 2015 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sun Jan 11 09:20:32 2015 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan 11 09:20:32 2015 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sun Jan 11 09:20:32 2015 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan 11 09:20:32 2015 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Sun Jan 11 09:20:32 2015 [FrozenWay] Peer Connection Initiated with [AF_INET]212.129.3.4:443

Sun Jan 11 09:20:35 2015 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)

Sun Jan 11 09:20:35 2015 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.3.0.1,dhcp-option WINS 10.3.0.1,route 10.3.0.1,topology net30,socket-flags TCP_NODELAY,ifconfig 10.3.1.178 10.3.1.177'
Sun Jan 11 09:20:35 2015 OPTIONS IMPORT: --socket-flags option modified
Sun Jan 11 09:20:35 2015 OPTIONS IMPORT: --ifconfig/up options modified
Sun Jan 11 09:20:35 2015 OPTIONS IMPORT: route options modified
Sun Jan 11 09:20:35 2015 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sun Jan 11 09:20:35 2015 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Sun Jan 11 09:20:35 2015 open_tun, tt->ipv6=0
Sun Jan 11 09:20:35 2015 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{0CBFC4BA-EB06-4839-A880-4C9C9CE71000}.tap
Sun Jan 11 09:20:35 2015 TAP-Windows Driver Version 9.9
Sun Jan 11 09:20:35 2015 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.3.1.178/255.255.255.252 on interface {0CBFC4BA-EB06-4839-A880-4C9C9CE71000} [DHCP-serv: 10.3.1.177, lease-time: 31536000]
Sun Jan 11 09:20:35 2015 Successful ARP Flush on interface [19] {0CBFC4BA-EB06-4839-A880-4C9C9CE71000}

Sun Jan 11 09:20:40 2015 TEST ROUTES: 1/1 succeeded len=1 ret=1 a=0 u/d=up
Sun Jan 11 09:20:40 2015 C:\WINDOWS\system32\route.exe ADD 10.3.0.1 MASK 255.255.255.255 10.3.1.177
Sun Jan 11 09:20:40 2015 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sun Jan 11 09:20:40 2015 Route addition via IPAPI succeeded [adaptive]
Sun Jan 11 09:20:40 2015 Initialization Sequence Completed

IPv4 routing table :
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.76 50
0.0.0.0 128.0.0.0 10.3.1.177 10.3.1.178 30
10.3.0.1 255.255.255.255 10.3.1.177 10.3.1.178 30
10.3.1.176 255.255.255.252 10.3.1.178 10.3.1.178 286
10.3.1.178 255.255.255.255 10.3.1.178 10.3.1.178 286
10.3.1.179 255.255.255.255 10.3.1.178 10.3.1.178 286
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
128.0.0.0 128.0.0.0 10.3.1.177 10.3.1.178 30
192.168.2.0 255.255.255.0 192.168.2.76 192.168.2.76 296
192.168.2.76 255.255.255.255 192.168.2.76 192.168.2.76 296
192.168.2.255 255.255.255.255 192.168.2.76 192.168.2.76 296
212.129.3.4 255.255.255.255 192.168.2.1 192.168.2.76 40
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 192.168.2.76 192.168.2.76 296
224.0.0.0 240.0.0.0 10.3.1.178 10.3.1.178 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 192.168.2.76 192.168.2.76 296
255.255.255.255 255.255.255.255 10.3.1.178 10.3.1.178 286
Sun Jan 11 09:21:45 2015 [FrozenWay] Inactivity timeout (--ping-exit), exiting
Sun Jan 11 09:21:45 2015 C:\WINDOWS\system32\route.exe DELETE 10.3.0.1 MASK 255.255.255.255 10.3.1.177
Sun Jan 11 09:21:45 2015 Route deletion via IPAPI succeeded [adaptive]
Sun Jan 11 09:21:45 2015 Closing TUN/TAP interface
Sun Jan 11 09:21:45 2015 SIGTERM[soft,ping-exit] received, process exiting

Réponses

Connectez-vous ou Inscrivez-vous pour répondre.