[Résolu] Problème de connexion à league of legende (et autre)

piloulilou

Bonjour,
Je viens de souscrire un abonnement d'un mois suite à se que j'ai lus sur plusieurs discutions : "le serveur premium #4 fonctionne avec league of legende".
En me connectant sur ce serveur, je n'arrive pas à me connecter à LoL ni à Steam. J'ai besoins que quelques explications sur ce problème ! CF une copie du journal :
FrozenWay version 1.6.5
----------------------------------
Server: premium-04-fr-01
Protocol: OpenVPN
----------------------------------
Tue Apr 29 02:43:09 2014 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013

Tue Apr 29 02:43:10 2014 Control Channel Authentication: using 'D:/FrozenWay 1.6.5/etc/keys/auth.key' as a OpenVPN static key file
Tue Apr 29 02:43:10 2014 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Apr 29 02:43:10 2014 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Apr 29 02:43:10 2014 Socket Buffers: R=[65536->65536] S=[65536->65536]
Tue Apr 29 02:43:10 2014 Attempting to establish TCP connection with [AF_INET]88.190.203.60:443

Tue Apr 29 02:43:10 2014 TCP connection established with [AF_INET]88.190.203.60:443
Tue Apr 29 02:43:10 2014 TCPv4_CLIENT link local: [undef]
Tue Apr 29 02:43:10 2014 TCPv4_CLIENT link remote: [AF_INET]88.190.203.60:443
Tue Apr 29 02:43:10 2014 TLS: Initial packet from [AF_INET]88.190.203.60:443, sid=a4743b6f 7bed2c07

Tue Apr 29 02:43:10 2014 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com
Tue Apr 29 02:43:10 2014 VERIFY OK: nsCertType=SERVER
Tue Apr 29 02:43:10 2014 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com

Tue Apr 29 02:43:10 2014 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Apr 29 02:43:10 2014 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Apr 29 02:43:10 2014 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Apr 29 02:43:10 2014 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Apr 29 02:43:10 2014 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Tue Apr 29 02:43:10 2014 [FrozenWay] Peer Connection Initiated with [AF_INET]88.190.203.60:443

Tue Apr 29 02:43:12 2014 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)
Tue Apr 29 02:43:12 2014 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.13.58 10.1.13.57'
Tue Apr 29 02:43:12 2014 OPTIONS IMPORT: --socket-flags option modified
Tue Apr 29 02:43:12 2014 OPTIONS IMPORT: --ifconfig/up options modified
Tue Apr 29 02:43:12 2014 OPTIONS IMPORT: route options modified
Tue Apr 29 02:43:12 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Tue Apr 29 02:43:12 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Tue Apr 29 02:43:12 2014 open_tun, tt->ipv6=0
Tue Apr 29 02:43:12 2014 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{E38B7FB4-6632-436C-A763-EBD6FF081EE1}.tap
Tue Apr 29 02:43:12 2014 TAP-Windows Driver Version 9.9
Tue Apr 29 02:43:12 2014 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.1.13.58/255.255.255.252 on interface {E38B7FB4-6632-436C-A763-EBD6FF081EE1} [DHCP-serv: 10.1.13.57, lease-time: 31536000]
Tue Apr 29 02:43:12 2014 Successful ARP Flush on interface [8] {E38B7FB4-6632-436C-A763-EBD6FF081EE1}

Tue Apr 29 02:43:17 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:17 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:22 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:22 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:24 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:24 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:25 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:25 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:26 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:26 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:27 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:27 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:28 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:28 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:29 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:29 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:31 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:31 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:32 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:32 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:33 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:33 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:34 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:34 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:35 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:35 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:36 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:36 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:37 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:37 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:39 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:39 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:40 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:40 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:41 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:41 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:42 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:42 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:43 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:43 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:44 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:44 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:45 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:45 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:46 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:46 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Tue Apr 29 02:43:47 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Apr 29 02:43:47 2014 C:\Windows\system32\route.exe ADD 10.1.0.1 MASK 255.255.255.255 10.1.13.57
Tue Apr 29 02:43:47 2014 Warning: route gateway is not reachable on any active network adapters: 10.1.13.57
Tue Apr 29 02:43:47 2014 Route addition via IPAPI failed [adaptive]
Tue Apr 29 02:43:47 2014 Route addition fallback to route.exe
Tue Apr 29 02:43:47 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 172.17.0.5 p=0 i=3 t=4 pr=3 a=1155 h=0 m=25/0/0/0/0
10.1.0.1 255.255.255.255 10.1.13.57 p=0 i=3 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
10.6.33.72 255.255.255.252 10.6.33.74 p=0 i=8 t=3 pr=2 a=4737 h=0 m=286/0/0/0/0
10.6.33.74 255.255.255.255 10.6.33.74 p=0 i=8 t=3 pr=2 a=4737 h=0 m=286/0/0/0/0
10.6.33.75 255.255.255.255 10.6.33.74 p=0 i=8 t=3 pr=2 a=4737 h=0 m=286/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=31898 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=31898 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=31898 h=0 m=306/0/0/0/0
172.17.0.0 255.255.0.0 172.17.55.255 p=0 i=3 t=3 pr=2 a=1810 h=0 m=281/0/0/0/0
172.17.55.255 255.255.255.255 172.17.55.255 p=0 i=3 t=3 pr=2 a=1810 h=0 m=281/0/0/0/0
172.17.255.255 255.255.255.255 172.17.55.255 p=0 i=3 t=3 pr=2 a=1810 h=0 m=281/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=31898 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 172.17.55.255 p=0 i=3 t=3 pr=2 a=6361 h=0 m=281/0/0/0/0
224.0.0.0 240.0.0.0 10.6.33.74 p=0 i=8 t=3 pr=2 a=4770 h=0 m=286/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=31898 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 172.17.55.255 p=0 i=3 t=3 pr=2 a=6361 h=0 m=281/0/0/0/0
255.255.255.255 255.255.255.255 10.6.33.74 p=0 i=8 t=3 pr=2 a=4770 h=0 m=286/0/0/0/0
SYSTEM ADAPTER LIST
TAP-Windows Adapter V9 #3
Index = 28
GUID = {7EE1094F-08DD-4449-A389-9C0457A681D6}
IP = 0.0.0.0/0.0.0.0
MAC = 00:ff:7e:e1:09:4f
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Tue Apr 29 02:43:47 2014
DHCP LEASE EXPIRES = Tue Apr 29 02:43:47 2014
DNS SERV =
TAP-Windows Adapter V9 #2
Index = 9
GUID = {DE55AB66-E815-478F-9565-97095B329187}
IP = 0.0.0.0/0.0.0.0
MAC = 00:ff:de:55:ab:66
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Tue Apr 29 02:43:47 2014
DHCP LEASE EXPIRES = Tue Apr 29 02:43:47 2014
DNS SERV =
TAP-Windows Adapter V9
Index = 8
GUID = {E38B7FB4-6632-436C-A763-EBD6FF081EE1}
IP = 10.6.33.74/255.255.255.252
MAC = 00:ff:e3:8b:7f:b4
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV = 10.6.33.73/255.255.255.255
DHCP LEASE OBTAINED = Tue Apr 29 01:24:50 2014
DHCP LEASE EXPIRES = Wed Apr 29 01:24:50 2015
DNS SERV = 10.6.0.1/255.255.255.255
Microsoft Wi-Fi Direct Virtual Adapter
Index = 5
GUID = {3B6B2611-5F77-446D-B6F8-378054E29F11}
IP = 0.0.0.0/0.0.0.0
MAC = 16:27:1e:4c:6e:c8
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Tue Apr 29 02:43:47 2014
DHCP LEASE EXPIRES = Tue Apr 29 02:43:47 2014
DNS SERV =
Realtek PCIe GBE Family Controller
Index = 4
GUID = {2AEDF53F-C2A6-4CB6-B643-4D2117FBC41E}
IP = 0.0.0.0/0.0.0.0
MAC = 40:16:7e:16:bd:27
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Tue Apr 29 02:43:47 2014
DHCP LEASE EXPIRES = Tue Apr 29 02:43:47 2014
PRI WINS = 127.0.0.1/255.255.255.255
SEC WINS =
DNS SERV =
Qualcomm Atheros AR9485 Wireless Network Adapter
Index = 3
GUID = {1FE9D4BD-F884-4EE9-A32F-EA9D3B4A8EF8}
IP = 172.17.55.255/255.255.0.0
MAC = 54:27:1e:4c:6e:c8
GATEWAY = 172.17.0.5/255.255.255.255
DHCP SERV = 172.17.0.5/255.255.255.255
DHCP LEASE OBTAINED = Tue Apr 29 02:13:37 2014
DHCP LEASE EXPIRES = Wed Apr 30 02:13:37 2014
PRI WINS = 172.17.0.11/255.255.255.255
SEC WINS =
DNS SERV = 172.17.0.5/255.255.255.255
Tue Apr 29 02:43:47 2014 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

IPv4 routing table :
0.0.0.0 0.0.0.0 172.17.0.5 172.17.55.255 9999
0.0.0.0 0.0.0.0 10.1.13.57 10.6.33.74 30
10.1.0.1 255.255.255.255 10.1.13.57 172.17.55.255 26
10.6.33.72 255.255.255.252 10.6.33.74 10.6.33.74 286
10.6.33.74 255.255.255.255 10.6.33.74 10.6.33.74 286
10.6.33.75 255.255.255.255 10.6.33.74 10.6.33.74 286
88.190.203.60 255.255.255.255 172.17.0.5 172.17.55.255 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
172.17.0.0 255.255.0.0 172.17.55.255 172.17.55.255 281
172.17.55.255 255.255.255.255 172.17.55.255 172.17.55.255 281
172.17.255.255 255.255.255.255 172.17.55.255 172.17.55.255 281
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 172.17.55.255 172.17.55.255 281
224.0.0.0 240.0.0.0 10.6.33.74 10.6.33.74 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 172.17.55.255 172.17.55.255 281
255.255.255.255 255.255.255.255 10.6.33.74 10.6.33.74 286

J'aimerais bien savoir si mon investissement dans FrozenWay est un investissement utile ou inutile comme il l'est pour moi en ce moment. Merci
PS : Je suis dans une cité Univérsitaire à Montpellier dont le résaux ne me permet pas de jouer à LoL ni de me connecter à Steam

dax56

il ne faut pas qu il y ai Initialization Sequence Completed With Errors
au dessu de IPv4 routing table si non les donnée ne passe pas par frozenway

piloulilou

Haha merci de ta réponse mais ça m'avance pas trop sur d’éventuelles manip à faire =P

piloulilou

Apres un reformatage de mon ordi (pour de multiples raisons) et la mise à jour des pilotes j'arrive (enfin) à me connecter sur le serveur premium 4 et jouer sans encombre à LoL. Problèmes résolus (je ne sais pas trop comment haa les joies de l'informatique)