FrozenWay + HWR + Hotspot SFR: problème temps de reconnexion

defcon2 · janvier 2014

Bonjour, nouvel utilisateur d'un hotspot SFR, j'ai galéré un bon moment avant de trouver comment lancer Steam (etc).

J'ai donc trouvé FrozenWay, pris le forfait à 12€/3 mois après avoir testé la démo, configuré comme décrit ici et là, ça fonctionne très bien, je peux lancer Steam etc, et jouer.

Et ca se reconnecte automatiquement toutes les 2 heures mais...ça prend plus ou moins 2 minutes à se reconnecter et durant ce temps, je suis déconnecté du jeu. La plupart des jeux utilisant le moteur Source autorisent un certain délai avant de se déconnecter, par exemple quand je joue à Left 4 Dead 2 je suis déconnecté du serveur au bout de 30 secondes sans internet. Il faudrait donc que je réduise le temps de reconnexion de FrozenWay/HWR, en dessous de 30 secondes.

Je ne sais pas exactement ce qui est à l'origine de ce problème, je soupçonne FrozenWay de ne pas vérifier assez souvent s'il est connecté à internet. Il faudrait un réglage dans les Options, qui permette de décider à quelle fréquence FrozenWay doit vérifier la connexion internet.

Edit: Apparemment FrozenWay détecte quand la connexion internet est interrompue (une vingtaine de secondes après), mais il ne se Déconnecte pas immédiatement et je crois que c'est ça qui empêche HWR de se reconnecter immédiatement

Voici le Journal depuis le lancement de FrozenWay jusqu'a une déconnexion/reconnexion (celle-ci a été assez rapide, mais un peu moins d'une minute tout de même):

FrozenWay version 1.6.5
----------------------------------
Server: public-01-fr-05
Protocol: OpenVPN
----------------------------------
Wed Jan 08 02:53:42 2014 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013

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

Wed Jan 08 02:53:42 2014 TCP connection established with [AF_INET]176.31.219.84:443
Wed Jan 08 02:53:42 2014 TCPv4_CLIENT link local: [undef]
Wed Jan 08 02:53:42 2014 TCPv4_CLIENT link remote: [AF_INET]176.31.219.84:443

Wed Jan 08 02:53:42 2014 TLS: Initial packet from [AF_INET]176.31.219.84:443, sid=3abc8dad 56be5e19

Wed Jan 08 02:53:44 2014 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com
Wed Jan 08 02:53:44 2014 VERIFY OK: nsCertType=SERVER
Wed Jan 08 02:53:44 2014 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com

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

Wed Jan 08 02:53:47 2014 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)

Wed Jan 08 02:53:47 2014 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.7.0.1,dhcp-option WINS 10.7.0.1,route 10.7.0.1,topology net30,socket-flags TCP_NODELAY,ifconfig 10.7.29.110 10.7.29.109'
Wed Jan 08 02:53:47 2014 OPTIONS IMPORT: --socket-flags option modified
Wed Jan 08 02:53:47 2014 OPTIONS IMPORT: --ifconfig/up options modified
Wed Jan 08 02:53:47 2014 OPTIONS IMPORT: route options modified
Wed Jan 08 02:53:47 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Wed Jan 08 02:53:47 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Wed Jan 08 02:53:47 2014 open_tun, tt->ipv6=0
Wed Jan 08 02:53:47 2014 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{62679E8C-149F-4217-B87D-8D8DBF438E6E}.tap
Wed Jan 08 02:53:47 2014 TAP-Windows Driver Version 9.9 
Wed Jan 08 02:53:47 2014 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.7.29.110/255.255.255.252 on interface {62679E8C-149F-4217-B87D-8D8DBF438E6E} [DHCP-serv: 10.7.29.109, lease-time: 31536000]
Wed Jan 08 02:53:47 2014 Successful ARP Flush on interface [26] {62679E8C-149F-4217-B87D-8D8DBF438E6E}

Wed Jan 08 02:53:52 2014 TEST ROUTES: 1/1 succeeded len=1 ret=1 a=0 u/d=up
Wed Jan 08 02:53:52 2014 C:\Windows\system32\route.exe ADD 10.7.0.1 MASK 255.255.255.255 10.7.29.109
Wed Jan 08 02:53:52 2014 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Wed Jan 08 02:53:52 2014 Route addition via IPAPI succeeded [adaptive]
Wed Jan 08 02:53:52 2014 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.7.29.109 10.7.29.110 30
10.7.0.1 255.255.255.255 10.7.29.109 10.7.29.110 30
10.7.29.108 255.255.255.252 10.7.29.110 10.7.29.110 286
10.7.29.110 255.255.255.255 10.7.29.110 10.7.29.110 286
10.7.29.111 255.255.255.255 10.7.29.110 10.7.29.110 286
62.122.9.80 255.255.255.255 192.168.2.1 192.168.2.66 25
74.125.132.99 255.255.255.255 192.168.2.1 192.168.2.66 25
74.125.132.103 255.255.255.255 192.168.2.1 192.168.2.66 25
74.125.132.104 255.255.255.255 192.168.2.1 192.168.2.66 25
74.125.132.105 255.255.255.255 192.168.2.1 192.168.2.66 25
74.125.132.106 255.255.255.255 192.168.2.1 192.168.2.66 25
74.125.132.147 255.255.255.255 192.168.2.1 192.168.2.66 25
77.67.21.17 255.255.255.255 192.168.2.1 192.168.2.66 25
77.67.21.64 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
134.170.188.84 255.255.255.255 192.168.2.1 192.168.2.66 25
176.31.219.84 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
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.66 192.168.2.66 281
224.0.0.0 240.0.0.0 10.7.29.110 10.7.29.110 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.66 192.168.2.66 281
255.255.255.255 255.255.255.255 10.7.29.110 10.7.29.110 286
Wed Jan 08 04:13:43 2014 write TCPv4_CLIENT: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Jan 08 04:13:43 2014 read TCPv4_CLIENT: Connection timed out (WSAETIMEDOUT) (code=10060)
Wed Jan 08 04:13:43 2014 Connection reset, restarting [-1]
Wed Jan 08 04:13:43 2014 SIGUSR1[soft,connection-reset] received, process restarting
Wed Jan 08 04:13:43 2014 Restart pause, 1 second(s)

Wed Jan 08 04:13:44 2014 Socket Buffers: R=[8192->8192] S=[8192->8192]
Wed Jan 08 04:13:44 2014 Attempting to establish TCP connection with [AF_INET]176.31.219.84:443

Wed Jan 08 04:14:05 2014 TCP: connect to [AF_INET]176.31.219.84:443 failed, will try again in 1 seconds: Connection timed out (WSAETIMEDOUT)

Wed Jan 08 04:14:27 2014 TCP: connect to [AF_INET]176.31.219.84:443 failed, will try again in 1 seconds: Connection timed out (WSAETIMEDOUT)

Wed Jan 08 04:14:37 2014 TCP connection established with [AF_INET]176.31.219.84:443
Wed Jan 08 04:14:37 2014 TCPv4_CLIENT link local: [undef]
Wed Jan 08 04:14:37 2014 TCPv4_CLIENT link remote: [AF_INET]176.31.219.84:443
Wed Jan 08 04:14:37 2014 TLS: Initial packet from [AF_INET]176.31.219.84:443, sid=f38b0760 89f034d4

Wed Jan 08 04:14:38 2014 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com
Wed Jan 08 04:14:38 2014 VERIFY OK: nsCertType=SERVER
Wed Jan 08 04:14:38 2014 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com

Wed Jan 08 04:14:38 2014 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Jan 08 04:14:38 2014 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Jan 08 04:14:38 2014 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Jan 08 04:14:38 2014 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Jan 08 04:14:38 2014 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Wed Jan 08 04:14:38 2014 [FrozenWay] Peer Connection Initiated with [AF_INET]176.31.219.84:443

Wed Jan 08 04:14:40 2014 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)

Wed Jan 08 04:14:40 2014 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.7.0.1,dhcp-option WINS 10.7.0.1,route 10.7.0.1,topology net30,socket-flags TCP_NODELAY,ifconfig 10.7.29.110 10.7.29.109'
Wed Jan 08 04:14:40 2014 OPTIONS IMPORT: --socket-flags option modified
Wed Jan 08 04:14:40 2014 OPTIONS IMPORT: --ifconfig/up options modified
Wed Jan 08 04:14:40 2014 OPTIONS IMPORT: route options modified
Wed Jan 08 04:14:40 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Wed Jan 08 04:14:40 2014 Preserving previous TUN/TAP instance: FrozenWay
Wed Jan 08 04:14:40 2014 Initialization Sequence Completed

Y-a-t-il une solution à ce problème?