[Résolu] Petit problème avec Frozenspot

AzarmahAzarmah
mars 2015 modifié dans Support technique
Bonjour

Je fais ce topic parce que j'ai en ce moment un petit problème qui survient pour la première fois.

Hier soir je n'avais aucun soucis à créer mon hotspot avec Frozenway, cependant aujourd'hui chaque fois que je le fais je perd systématiquement ma connexion internet et ceci s'affiche dans le journal de Frozenway :

Wed Mar 04 10:38:45 2015 write TCPv4_CLIENT: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 10:38:45 2015 write TCPv4_CLIENT: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 10:38:45 2015 read TCPv4_CLIENT: Connection timed out (WSAETIMEDOUT) (code=10060)
Wed Mar 04 10:38:45 2015 Connection reset, restarting [-1]
Wed Mar 04 10:38:45 2015 SIGUSR1[soft,connection-reset] received, process restarting
Wed Mar 04 10:38:45 2015 Restart pause, 1 second(s)

Wed Mar 04 10:38:46 2015 Socket Buffers: R=[65536->65536] S=[65536->65536]
Wed Mar 04 10:38:46 2015 Attempting to establish TCP connection with [AF_INET]176.31.61.23:443

Wed Mar 04 10:39:07 2015 TCP: connect to [AF_INET]176.31.61.23:443 failed, will try again in 1 seconds: Connection timed out (WSAETIMEDOUT)

Wed Mar 04 10:39:29 2015 TCP: connect to [AF_INET]176.31.61.23:443 failed, will try again in 1 seconds: Connection timed out (WSAETIMEDOUT)

Wed Mar 04 10:39:51 2015 TCP: connect to [AF_INET]176.31.61.23:443 failed, will try again in 1 seconds: Connection timed out (WSAETIMEDOUT)

Wed Mar 04 10:40:13 2015 TCP: connect to [AF_INET]176.31.61.23:443 failed, will try again in 1 seconds: Connection timed out (WSAETIMEDOUT)

Merci d'avance pour l'aide.

Réponses

  • 4t0m1k4t0m1k
    Salut,

    As-tu essayé de redémarrer ton PC ?

    Peux-tu donner le journal de connexion complet stp ?
  • AzarmahAzarmah
    Journal complet :

    FrozenWay version 1.6.5
    ----------------------------------
    Server: premium-01-ch-03
    Protocol: OpenVPN
    ----------------------------------
    Wed Mar 04 10:49:40 2015 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013

    Wed Mar 04 10:49:41 2015 Control Channel Authentication: using 'C:/Users/Azarmah/Downloads/FrozenWay 1.6.5/etc/keys/auth.key' as a OpenVPN static key file
    Wed Mar 04 10:49:41 2015 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Wed Mar 04 10:49:41 2015 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Wed Mar 04 10:49:41 2015 Socket Buffers: R=[65536->65536] S=[65536->65536]
    Wed Mar 04 10:49:41 2015 Attempting to establish TCP connection with [AF_INET]5.135.109.190:443
    Wed Mar 04 10:49:41 2015 TCP connection established with [AF_INET]5.135.109.190:443
    Wed Mar 04 10:49:41 2015 TCPv4_CLIENT link local: [undef]
    Wed Mar 04 10:49:41 2015 TCPv4_CLIENT link remote: [AF_INET]5.135.109.190:443

    Wed Mar 04 10:49:41 2015 TLS: Initial packet from [AF_INET]5.135.109.190:443, sid=502bb43f c04b400d

    Wed Mar 04 10:49:42 2015 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com
    Wed Mar 04 10:49:42 2015 VERIFY OK: nsCertType=SERVER
    Wed Mar 04 10:49:42 2015 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com

    Wed Mar 04 10:49:42 2015 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Wed Mar 04 10:49:42 2015 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Wed Mar 04 10:49:42 2015 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Wed Mar 04 10:49:42 2015 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Wed Mar 04 10:49:42 2015 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
    Wed Mar 04 10:49:42 2015 [FrozenWay] Peer Connection Initiated with [AF_INET]5.135.109.190:443

    Wed Mar 04 10:49:44 2015 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)
    Wed Mar 04 10:49:44 2015 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.19.0.1,dhcp-option WINS 10.19.0.1,route 10.19.0.1,topology net30,socket-flags TCP_NODELAY,ifconfig 10.19.0.10 10.19.0.9'
    Wed Mar 04 10:49:44 2015 OPTIONS IMPORT: --socket-flags option modified
    Wed Mar 04 10:49:44 2015 OPTIONS IMPORT: --ifconfig/up options modified
    Wed Mar 04 10:49:44 2015 OPTIONS IMPORT: route options modified
    Wed Mar 04 10:49:44 2015 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
    Wed Mar 04 10:49:44 2015 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
    Wed Mar 04 10:49:44 2015 open_tun, tt->ipv6=0
    Wed Mar 04 10:49:44 2015 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{64480F9C-1AA2-4C17-B337-16ED22094DA1}.tap
    Wed Mar 04 10:49:44 2015 TAP-Windows Driver Version 9.9
    Wed Mar 04 10:49:44 2015 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.19.0.10/255.255.255.252 on interface {64480F9C-1AA2-4C17-B337-16ED22094DA1} [DHCP-serv: 10.19.0.9, lease-time: 31536000]
    Wed Mar 04 10:49:44 2015 Successful ARP Flush on interface [8] {64480F9C-1AA2-4C17-B337-16ED22094DA1}

    Wed Mar 04 10:49:49 2015 TEST ROUTES: 1/1 succeeded len=1 ret=1 a=0 u/d=up
    Wed Mar 04 10:49:49 2015 C:\WINDOWS\system32\route.exe ADD 10.19.0.1 MASK 255.255.255.255 10.19.0.9
    Wed Mar 04 10:49:49 2015 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
    Wed Mar 04 10:49:49 2015 Route addition via IPAPI succeeded [adaptive]
    Wed Mar 04 10:49:49 2015 Initialization Sequence Completed

    IPv4 routing table :
    0.0.0.0 0.0.0.0 10.42.0.1 10.42.24.26 25
    0.0.0.0 128.0.0.0 10.17.1.205 10.19.0.10 30
    0.0.0.0 128.0.0.0 10.19.0.9 10.19.0.10 30
    5.135.109.188 255.255.255.255 10.42.0.1 10.42.24.26 25
    10.4.0.1 255.255.255.255 10.4.0.113 10.19.0.10 30
    10.17.0.1 255.255.255.255 10.17.1.205 10.19.0.10 30
    10.19.0.1 255.255.255.255 10.19.0.9 10.19.0.10 30
    10.19.0.8 255.255.255.252 10.19.0.10 10.19.0.10 286
    10.19.0.10 255.255.255.255 10.19.0.10 10.19.0.10 286
    10.19.0.11 255.255.255.255 10.19.0.10 10.19.0.10 286
    10.42.0.0 255.255.0.0 10.42.24.26 10.42.24.26 281
    10.42.24.26 255.255.255.255 10.42.24.26 10.42.24.26 281
    10.42.255.255 255.255.255.255 10.42.24.26 10.42.24.26 281
    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.17.1.205 10.19.0.10 30
    128.0.0.0 128.0.0.0 10.19.0.9 10.19.0.10 30
    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.19.0.10 10.19.0.10 286
    224.0.0.0 240.0.0.0 10.42.24.26 10.42.24.26 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.19.0.10 10.19.0.10 286
    255.255.255.255 255.255.255.255 10.42.24.26 10.42.24.26 281
    Wed Mar 04 10:50:37 2015 write TCPv4_CLIENT: Connection reset by peer (WSAECONNRESET) (code=10054)
    Wed Mar 04 10:50:37 2015 write TCPv4_CLIENT: Connection reset by peer (WSAECONNRESET) (code=10054)
    Wed Mar 04 10:50:37 2015 write TCPv4_CLIENT: Connection reset by peer (WSAECONNRESET) (code=10054)
    Wed Mar 04 10:50:37 2015 write TCPv4_CLIENT: Connection reset by peer (WSAECONNRESET) (code=10054)
    Wed Mar 04 10:50:37 2015 read TCPv4_CLIENT: Connection timed out (WSAETIMEDOUT) (code=10060)
    Wed Mar 04 10:50:37 2015 Connection reset, restarting [-1]
    Wed Mar 04 10:50:37 2015 SIGUSR1[soft,connection-reset] received, process restarting
    Wed Mar 04 10:50:37 2015 Restart pause, 1 second(s)

    Wed Mar 04 10:50:38 2015 Socket Buffers: R=[65536->65536] S=[65536->65536]
    Wed Mar 04 10:50:38 2015 Attempting to establish TCP connection with [AF_INET]5.135.109.190:443

    Wed Mar 04 10:50:59 2015 TCP: connect to [AF_INET]5.135.109.190:443 failed, will try again in 1 seconds: Connection timed out (WSAETIMEDOUT)

    C'est un différent vu que j'ai recommencé sur un autre serveur mais il se passe la même chose.

    Je redémarre mon PC et je réessaye.
  • AzarmahAzarmah
    Après redémarrage ça semble fonctionner, je ne sais pas vraiment pourquoi, en tout cas problème réglé merci.
  • 4t0m1k4t0m1k
    Salut,

    Ça venait d'un problème dans ta table de routage (un bug venant de FrozenWay).
Cette discussion a été fermée.