[Résolu] Frozenway se connecte mais rien ne change en réalité (ip inchangée, ports bloqués)

HorusLupercalHorusLupercal
septembre 2016 modifié dans Support technique
Salut, je suis sur un co de type crous avec identification par navigateur. Frozenway fonctionnait encore hier sans soucis (battle.net, steam, p2p) avec abo illimité.
Aujourd'hui il se connecte mais l'ip reste celle du crous quand je check sur http://www.ip-adress.eu/ ou un autre site du meme type. aucune de mes apps ne fonctionne car les ports semblent bloqués comme si frozenway ne faisait rien en réalité.
Journal :
FrozenWay version 1.6.6
----------------------------------
Server: premium-02-fr-01
Protocol: OpenVPN
----------------------------------
Wed Sep 07 15:46:10 2016 OpenVPN 2.3.8 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Aug 27 2015
Wed Sep 07 15:46:10 2016 library versions: OpenSSL 1.0.1p 9 Jul 2015, LZO 2.08

Wed Sep 07 15:46:10 2016 Control Channel Authentication: using 'C:/Users/Horus/Desktop/FrozenWay 1.6.6/etc/keys/auth.key' as a OpenVPN static key file
Wed Sep 07 15:46:10 2016 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Sep 07 15:46:10 2016 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Sep 07 15:46:10 2016 Socket Buffers: R=[65536->65536] S=[65536->65536]
Wed Sep 07 15:46:10 2016 Attempting to establish TCP connection with [AF_INET]178.33.86.20:443 [nonblock]

Wed Sep 07 15:46:11 2016 TCP connection established with [AF_INET]178.33.86.20:443
Wed Sep 07 15:46:11 2016 TCPv4_CLIENT link local: [undef]
Wed Sep 07 15:46:11 2016 TCPv4_CLIENT link remote: [AF_INET]178.33.86.20:443
Wed Sep 07 15:46:11 2016 TLS: Initial packet from [AF_INET]178.33.86.20:443, sid=ac27df4e 8f29174f

Wed Sep 07 15:46:11 2016 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com
Wed Sep 07 15:46:11 2016 VERIFY OK: nsCertType=SERVER
Wed Sep 07 15:46:11 2016 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com

Wed Sep 07 15:46:11 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Sep 07 15:46:11 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Sep 07 15:46:11 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Sep 07 15:46:11 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Sep 07 15:46:11 2016 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 1024 bit RSA
Wed Sep 07 15:46:11 2016 [FrozenWay] Peer Connection Initiated with [AF_INET]178.33.86.20:443

Wed Sep 07 15:46:13 2016 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)
Wed Sep 07 15:46:13 2016 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.90 10.1.0.89'
Wed Sep 07 15:46:13 2016 OPTIONS IMPORT: --socket-flags option modified
Wed Sep 07 15:46:13 2016 OPTIONS IMPORT: --ifconfig/up options modified
Wed Sep 07 15:46:13 2016 OPTIONS IMPORT: route options modified
Wed Sep 07 15:46:13 2016 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Wed Sep 07 15:46:13 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Wed Sep 07 15:46:13 2016 open_tun, tt->ipv6=0
Wed Sep 07 15:46:13 2016 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{C4E1B874-386D-488C-A439-26002C012394}.tap
Wed Sep 07 15:46:13 2016 TAP-Windows Driver Version 9.21
Wed Sep 07 15:46:13 2016 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.1.0.90/255.255.255.252 on interface {C4E1B874-386D-488C-A439-26002C012394} [DHCP-serv: 10.1.0.89, lease-time: 31536000]
Wed Sep 07 15:46:13 2016 Successful ARP Flush on interface [10] {C4E1B874-386D-488C-A439-26002C012394}

Wed Sep 07 15:46:18 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:18 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:23 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:23 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:24 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:24 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:25 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:25 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:26 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:26 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:27 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:27 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:28 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:28 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:29 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:29 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:30 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:30 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:32 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:32 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:33 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:33 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:34 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:34 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:36 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:36 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:37 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:37 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:38 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:38 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:39 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:39 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:40 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:40 2016 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Wed Sep 07 15:46:42 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Sep 07 15:46:42 2016 Route: Waiting for TUN/TAP interface to come up...

Réponses

  • HorusLupercalHorusLupercal
    suite du journal :
    Waking up the interface...
    Wed Sep 07 15:46:43 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
    Wed Sep 07 15:46:43 2016 Route: Waiting for TUN/TAP interface to come up...

    Waking up the interface...
    Wed Sep 07 15:46:44 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
    Wed Sep 07 15:46:44 2016 Route: Waiting for TUN/TAP interface to come up...

    Waking up the interface...
    Wed Sep 07 15:46:45 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
    Wed Sep 07 15:46:45 2016 Route: Waiting for TUN/TAP interface to come up...

    Waking up the interface...
    Wed Sep 07 15:46:46 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
    Wed Sep 07 15:46:46 2016 Route: Waiting for TUN/TAP interface to come up...

    Waking up the interface...
    Wed Sep 07 15:46:47 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
    Wed Sep 07 15:46:47 2016 Route: Waiting for TUN/TAP interface to come up...

    Waking up the interface...
    Wed Sep 07 15:46:49 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
    Wed Sep 07 15:46:49 2016 C:\Windows\system32\route.exe ADD 10.1.0.1 MASK 255.255.255.255 10.1.0.89
    Wed Sep 07 15:46:49 2016 Warning: route gateway is not reachable on any active network adapters: 10.1.0.89
    Wed Sep 07 15:46:49 2016 Route addition via IPAPI failed [adaptive]
    Wed Sep 07 15:46:49 2016 Route addition fallback to route.exe
    Wed Sep 07 15:46:49 2016 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
    SYSTEM ROUTING TABLE
    0.0.0.0 0.0.0.0 192.168.71.254 p=0 i=12 t=4 pr=3 a=1392 h=0 m=20/0/0/0/0
    10.1.0.1 255.255.255.255 10.1.0.13 p=0 i=12 t=4 pr=3 a=37150 h=0 m=21/0/0/0/0
    10.1.0.1 255.255.255.255 10.1.0.89 p=0 i=12 t=4 pr=3 a=0 h=0 m=21/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=2907203 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=2907203 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=2907203 h=0 m=306/0/0/0/0
    169.254.0.0 255.255.0.0 169.254.177.216 p=0 i=10 t=3 pr=2 a=696 h=0 m=276/0/0/0/0
    169.254.177.216 255.255.255.255 169.254.177.216 p=0 i=10 t=3 pr=2 a=696 h=0 m=276/0/0/0/0
    169.254.255.255 255.255.255.255 169.254.177.216 p=0 i=10 t=3 pr=2 a=696 h=0 m=276/0/0/0/0
    192.168.71.0 255.255.255.0 192.168.71.48 p=0 i=12 t=3 pr=2 a=1392 h=0 m=276/0/0/0/0
    192.168.71.48 255.255.255.255 192.168.71.48 p=0 i=12 t=3 pr=2 a=1392 h=0 m=276/0/0/0/0
    192.168.71.255 255.255.255.255 192.168.71.48 p=0 i=12 t=3 pr=2 a=1392 h=0 m=276/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=2907203 h=0 m=306/0/0/0/0
    224.0.0.0 240.0.0.0 192.168.71.48 p=0 i=12 t=3 pr=2 a=2907203 h=0 m=276/0/0/0/0
    224.0.0.0 240.0.0.0 169.254.177.216 p=0 i=10 t=3 pr=2 a=715 h=0 m=276/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=2907203 h=0 m=306/0/0/0/0
    255.255.255.255 255.255.255.255 192.168.71.48 p=0 i=12 t=3 pr=2 a=2907203 h=0 m=276/0/0/0/0
    255.255.255.255 255.255.255.255 169.254.177.216 p=0 i=10 t=3 pr=2 a=715 h=0 m=276/0/0/0/0
    SYSTEM ADAPTER LIST
    Killer E2200 Gigabit Ethernet Controller
    Index = 12
    GUID = {FBBB6A62-11FB-4AD2-94C5-5F96E6D6A8D7}
    IP = 192.168.71.48/255.255.255.0
    MAC = d8:cb:8a:7f:62:b5
    GATEWAY = 192.168.71.254/255.255.255.255
    DHCP SERV = 10.3.0.31/255.255.255.255
    DHCP LEASE OBTAINED = Wed Sep 07 15:38:37 2016
    DHCP LEASE EXPIRES = Wed Sep 07 16:08:37 2016
    DNS SERV = 193.50.27.67/255.255.255.255 193.50.27.66/255.255.255.255
    Killer Wireless-n/a/ac 1525 Wireless Network Adapter
    Index = 11
    GUID = {CD795CC9-FBA0-4813-B2E6-A22357089993}
    IP = 0.0.0.0/0.0.0.0
    MAC = ac:d1:b8:8c:c6:47
    GATEWAY = 10.10.111.254/255.255.255.255
    DHCP SERV =
    DHCP LEASE OBTAINED = Wed Sep 07 15:46:49 2016
    DHCP LEASE EXPIRES = Wed Sep 07 15:46:49 2016
    DNS SERV =
    Microsoft Wi-Fi Direct Virtual Adapter
    Index = 5
    GUID = {52F5F677-0205-4C6A-9055-9B592AA4F8DA}
    IP = 0.0.0.0/0.0.0.0
    MAC = ae:d1:b8:8c:c6:47
    GATEWAY = 0.0.0.0/255.255.255.255
    DHCP SERV =
    DHCP LEASE OBTAINED = Wed Sep 07 15:46:49 2016
    DHCP LEASE EXPIRES = Wed Sep 07 15:46:49 2016
    DNS SERV =
    FrozenWay Adapter
    Index = 10
    GUID = {C4E1B874-386D-488C-A439-26002C012394}
    IP = 169.254.177.216/255.255.0.0
    MAC = 00:ff:c4:e1:b8:74
    GATEWAY = 0.0.0.0/255.255.255.255
    DHCP SERV = 10.1.3.25/255.255.255.255
    DHCP LEASE OBTAINED = Wed Sep 07 03:05:46 2016
    DHCP LEASE EXPIRES = Thu Sep 07 03:05:46 2017
    PRI WINS = 10.1.0.1/255.255.255.255
    SEC WINS =
    DNS SERV = 10.1.0.1/255.255.255.255
    Wed Sep 07 15:46:49 2016 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

    IPv4 routing table :
    0.0.0.0 0.0.0.0 192.168.71.254 192.168.71.48 20
    0.0.0.0 128.0.0.0 10.1.0.89 169.254.177.216 20
    10.1.0.1 255.255.255.255 10.1.0.13 192.168.71.48 21
    10.1.0.1 255.255.255.255 10.1.0.89 192.168.71.48 21
    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.1.0.89 169.254.177.216 20
    169.254.0.0 255.255.0.0 169.254.177.216 169.254.177.216 276
    169.254.177.216 255.255.255.255 169.254.177.216 169.254.177.216 276
    169.254.255.255 255.255.255.255 169.254.177.216 169.254.177.216 276
    178.33.86.20 255.255.255.255 192.168.71.254 192.168.71.48 20
    192.168.71.0 255.255.255.0 192.168.71.48 192.168.71.48 276
    192.168.71.48 255.255.255.255 192.168.71.48 192.168.71.48 276
    192.168.71.255 255.255.255.255 192.168.71.48 192.168.71.48 276
    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.71.48 192.168.71.48 276
    224.0.0.0 240.0.0.0 169.254.177.216 169.254.177.216 276
    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.71.48 192.168.71.48 276
    255.255.255.255 255.255.255.255 169.254.177.216 16
  • HorusLupercalHorusLupercal
    Au pire je me ferait pas chier et réinstallerai le pc complètement vu que je doit le faire bientôt, mais d'ici la si ya une solution pratique que je ne vois pas je suis preneur.
  • 4t0m1k4t0m1k
    Salut,

    As-tu essayé de redémarrer ton PC ?
  • HorusLupercalHorusLupercal
    Salut, désolé de la réponse tardive. j'ai ipconfig /release, flushdns etc... puis redémarrer le pc et cela as fait le nécessaire.
    A priori plus de problèmes donc
Cette discussion a été fermée.