Pas de connecion frozenway

nsdtnsdt
dans Support technique
Bonjour,
Ma connexion à frozenway est plus longue que d'habitude et surtout ça ne marche pas -.-
( windows indique: Identification .... pas d'accès internet )

Mon log ( j'ai enlevé une partie du début pour le nombre de caractères):

FrozenWay version 1.6.5
----------------------------------
Server: premium-04-fr-04
Proxy: 129.104.247.2:8080
Protocol: OpenVPN
----------------------------------

Sat Aug 29 11:06:54 2015 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)
Sat Aug 29 11:06:54 2015 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.4.0.1,dhcp-option WINS 10.4.0.1,route 10.4.0.1,topology net30,socket-flags TCP_NODELAY,ifconfig 10.4.3.42 10.4.3.41'
Sat Aug 29 11:06:54 2015 OPTIONS IMPORT: --socket-flags option modified
Sat Aug 29 11:06:54 2015 OPTIONS IMPORT: --ifconfig/up options modified
Sat Aug 29 11:06:54 2015 OPTIONS IMPORT: route options modified
Sat Aug 29 11:06:54 2015 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sat Aug 29 11:06:54 2015 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Sat Aug 29 11:06:54 2015 open_tun, tt->ipv6=0
Sat Aug 29 11:06:54 2015 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{78505CC0-03BE-495F-B032-7A5F0041DF60}.tap
Sat Aug 29 11:06:54 2015 TAP-Windows Driver Version 9.9
Sat Aug 29 11:06:54 2015 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.4.3.42/255.255.255.252 on interface {78505CC0-03BE-495F-B032-7A5F0041DF60} [DHCP-serv: 10.4.3.41, lease-time: 31536000]
Sat Aug 29 11:06:54 2015 Successful ARP Flush on interface [7] {78505CC0-03BE-495F-B032-7A5F0041DF60}

Sat Aug 29 11:06:59 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sat Aug 29 11:06:59 2015 Route: Waiting for TUN/TAP interface to come up...


Waking up the interface...
Sat Aug 29 11:07:29 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sat Aug 29 11:07:29 2015 C:\WINDOWS\system32\route.exe ADD 10.4.0.1 MASK 255.255.255.255 10.4.3.41
Sat Aug 29 11:07:29 2015 Warning: route gateway is not reachable on any active network adapters: 10.4.3.41
Sat Aug 29 11:07:29 2015 Route addition via IPAPI failed [adaptive]
Sat Aug 29 11:07:29 2015 Route addition fallback to route.exe
Sat Aug 29 11:07:29 2015 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 129.104.215.253 p=0 i=5 t=4 pr=3 a=462 h=0 m=20/0/0/0/0
10.4.0.1 255.255.255.255 10.4.3.41 p=0 i=5 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=486 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=486 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=486 h=0 m=306/0/0/0/0
129.104.212.0 255.255.252.0 129.104.212.25 p=0 i=5 t=3 pr=2 a=462 h=0 m=276/0/0/0/0
129.104.212.25 255.255.255.255 129.104.212.25 p=0 i=5 t=3 pr=2 a=462 h=0 m=276/0/0/0/0
129.104.215.255 255.255.255.255 129.104.212.25 p=0 i=5 t=3 pr=2 a=462 h=0 m=276/0/0/0/0
169.254.0.0 255.255.0.0 169.254.224.66 p=0 i=7 t=3 pr=2 a=32 h=0 m=286/0/0/0/0
169.254.224.66 255.255.255.255 169.254.224.66 p=0 i=7 t=3 pr=2 a=32 h=0 m=286/0/0/0/0
169.254.255.255 255.255.255.255 169.254.224.66 p=0 i=7 t=3 pr=2 a=32 h=0 m=286/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=486 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 129.104.212.25 p=0 i=5 t=3 pr=2 a=478 h=0 m=276/0/0/0/0
224.0.0.0 240.0.0.0 169.254.224.66 p=0 i=7 t=3 pr=2 a=110 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=486 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 129.104.212.25 p=0 i=5 t=3 pr=2 a=478 h=0 m=276/0/0/0/0
255.255.255.255 255.255.255.255 169.254.224.66 p=0 i=7 t=3 pr=2 a=110 h=0 m=286/0/0/0/0
SYSTEM ADAPTER LIST
Realtek PCIe GBE Family Controller
Index = 5
GUID = {3A5D4D7E-7388-4A03-A4DD-C93B62228AD0}
IP = 129.104.212.25/255.255.252.0
MAC = 20:6a:8a:ea:ef:a9
GATEWAY = 129.104.215.253/255.255.255.255
DHCP SERV = 129.104.201.57/255.255.255.255
DHCP LEASE OBTAINED = Sat Aug 29 11:00:12 2015
DHCP LEASE EXPIRES = Sat Aug 29 14:50:27 2015
DNS SERV = 129.104.201.53/255.255.255.255 129.104.201.51/255.255.255.255
Carte virtuelle directe Wi-Fi Microsoft #3
Index = 3
GUID = {1FFA745C-6773-41E2-8CA7-883DEE181659}
IP = 0.0.0.0/0.0.0.0
MAC = 16:17:31:36:31:57
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Sat Aug 29 11:07:29 2015
DHCP LEASE EXPIRES = Sat Aug 29 11:07:29 2015
DNS SERV =
Microsoft Hosted Network Virtual Adapter
Index = 6
GUID = {46F4D453-9A26-4523-B1D6-4835914C197B}
IP = 0.0.0.0/0.0.0.0
MAC = 56:17:31:36:31:57
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Sat Aug 29 11:07:29 2015
DHCP LEASE EXPIRES = Sat Aug 29 11:07:29 2015
DNS SERV =
Qualcomm Atheros AR5BWB222 Wireless Network Adapter
Index = 8
GUID = {F46A3D86-C6D7-401D-A561-93166ECADB27}
IP = 0.0.0.0/0.0.0.0
MAC = a4:17:31:36:31:57
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Sat Aug 29 11:07:29 2015
DHCP LEASE EXPIRES = Sat Aug 29 11:07:29 2015
DNS SERV =
TAP-Windows Adapter V9
Index = 7
GUID = {78505CC0-03BE-495F-B032-7A5F0041DF60}
IP = 169.254.224.66/255.255.0.0
MAC = 00:ff:78:50:5c:c0
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Sat Aug 29 11:07:29 2015
DHCP LEASE EXPIRES = Sat Aug 29 11:07:29 2015
DNS SERV =
Sat Aug 29 11:07:29 2015 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

IPv4 routing table :
0.0.0.0 0.0.0.0 129.104.215.253 129.104.212.25 20
0.0.0.0 128.0.0.0 10.4.3.41 169.254.224.66 30
10.4.0.1 255.255.255.255 10.4.3.41 129.104.212.25 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.4.3.41 169.254.224.66 30
129.104.212.0 255.255.252.0 129.104.212.25 129.104.212.25 276
129.104.212.25 255.255.255.255 129.104.212.25 129.104.212.25 276
129.104.215.255 255.255.255.255 129.104.212.25 129.104.212.25 276
129.104.247.2 255.255.255.255 129.104.215.253 129.104.212.25 20
169.254.0.0 255.255.0.0 169.254.224.66 169.254.224.66 286
169.254.224.66 255.255.255.255 169.254.224.66 169.254.224.66 286
169.254.255.255 255.255.255.255 169.254.224.66 169.254.224.66 286
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 129.104.212.25 129.104.212.25 276
224.0.0.0 240.0.0.0 169.254.224.66 169.254.224.66 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 129.104.212.25 129.104.212.25 276
255.255.255.255 255.255.255.255 169.254.224.66 169.254.224.66 286

J'ai essayé d'installer la dernière version de TAP windows V9 adapter, de mettre à jour son pilote, de l'installer après avoir démarrer frozenway
J'ai installé Open VPN ...

Aucune de ces méthodes n'a marché, je suis sous Windows 10 depuis sa sortie.

Hier, frozenway marchait et rien n'a changé au niveau logiciel entre le moment où ça marchait et celui ou cela ne marchait pas à moins que windows ait été mis à jour automatiquement à l'arrêt ...

Merci d'avance pour la réponse ;)

Réponses

  • nsdtnsdt
    Finalement, j'ai trouvé la (une?) solution en cherchant dans les posts du forum
    J'ai modifié la méthode d'attribution de l'adresse IP dans les options réseau et ça a marché de nouveau
    Désolé du post inutile ( peut être qu'il servira à quelqu'un, qui sait ?)
  • 4t0m1k4t0m1k
    Salut,

    Merci pour ton retour. Je vais sortir aujourd'hui ou demain une nouvelle version de FrozenWay compatible Windows 10.
Connectez-vous ou Inscrivez-vous pour répondre.