[Résolu] [crous] Filtrage toujours actif

janvier 2014 modifié dans Support technique
Bonsoir,

Je suis abonnée HTF depuis décembre et ça marchait plutôt bien, merci.
Mais depuis le début du mois j'ai eu des soucis. Régulièrement lorsque je me connecte à FW le filtrage de mon crous (nancy-metz qui nécessite de laisser une pop-up ouverte) reste actif et je dois attendre au moins une dizaine de minute pour espérer qu'il disparaisse (ce qui est assez gênant car ce forum ne passe bien sur pas le filtrage par exemple). Pire, de temps en temps, quand je me connecte je n'ai plus de connexion du tout :/
De plus je ne vois le ping que du premium 4.
Depuis ce matin FW n'agit plus du tout, voici un journal :




FrozenWay version 1.6.5
----------------------------------
Server: premium-04-fr-04
Protocol: OpenVPN
----------------------------------
Sun Jan 19 19:31:29 2014 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013

Sun Jan 19 19:31:30 2014 Control Channel Authentication: using 'C:/Users/M/Desktop/Launch/FrozenWay 1.6.5/etc/keys/auth.key' as a OpenVPN static key file
Sun Jan 19 19:31:30 2014 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan 19 19:31:30 2014 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan 19 19:31:30 2014 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Jan 19 19:31:30 2014 Attempting to establish TCP connection with [AF_INET]88.190.203.75:443
Sun Jan 19 19:31:30 2014 TCP connection established with [AF_INET]88.190.203.75:443
Sun Jan 19 19:31:30 2014 TCPv4_CLIENT link local: [undef]
Sun Jan 19 19:31:30 2014 TCPv4_CLIENT link remote: [AF_INET]88.190.203.75:443
Sun Jan 19 19:31:30 2014 TLS: Initial packet from [AF_INET]88.190.203.75:443, sid=39435b7a e0ab06cf

Sun Jan 19 19:31:30 2014 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com
Sun Jan 19 19:31:30 2014 VERIFY OK: nsCertType=SERVER
Sun Jan 19 19:31:30 2014 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com

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

Sun Jan 19 19:31:33 2014 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)
Sun Jan 19 19:31:33 2014 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.182 10.4.3.181'
Sun Jan 19 19:31:33 2014 OPTIONS IMPORT: --socket-flags option modified
Sun Jan 19 19:31:33 2014 OPTIONS IMPORT: --ifconfig/up options modified
Sun Jan 19 19:31:33 2014 OPTIONS IMPORT: route options modified
Sun Jan 19 19:31:33 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sun Jan 19 19:31:33 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Sun Jan 19 19:31:33 2014 open_tun, tt->ipv6=0
Sun Jan 19 19:31:33 2014 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{8C5F2084-CEF8-4142-9B00-C637664DB441}.tap
Sun Jan 19 19:31:33 2014 TAP-Windows Driver Version 9.9
Sun Jan 19 19:31:33 2014 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.4.3.182/255.255.255.252 on interface {8C5F2084-CEF8-4142-9B00-C637664DB441} [DHCP-serv: 10.4.3.181, lease-time: 31536000]
Sun Jan 19 19:31:33 2014 Successful ARP Flush on interface [6] {8C5F2084-CEF8-4142-9B00-C637664DB441}

Sun Jan 19 19:31:38 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:38 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:44 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:44 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:45 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:45 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:46 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:46 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:47 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:47 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:48 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:48 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:49 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:49 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:50 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:50 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:51 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:51 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:53 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:53 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:54 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:54 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:55 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:55 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:57 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:57 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:58 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:58 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:31:59 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:31:59 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:32:00 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:32:00 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:32:01 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:32:01 2014 Route: Waiting for TUN/TAP interface to come up...

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

Waking up the interface...
Sun Jan 19 19:32:03 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:32:03 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:32:04 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:32:04 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:32:05 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:32:05 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:32:06 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:32:06 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:32:07 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:32:07 2014 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 19 19:32:08 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 19 19:32:08 2014 C:\WINDOWS\system32\route.exe ADD 10.4.0.1 MASK 255.255.255.255 10.4.3.181
Sun Jan 19 19:32:08 2014 Warning: route gateway is not reachable on any active network adapters: 10.4.3.181
Sun Jan 19 19:32:08 2014 Route addition via IPAPI failed [adaptive]
Sun Jan 19 19:32:08 2014 Route addition fallback to route.exe
Sun Jan 19 19:32:08 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 192.168.195.254 p=0 i=3 t=4 pr=3 a=108 h=0 m=30/0/0/0/0
10.3.3.148 255.255.255.252 10.3.3.150 p=0 i=6 t=3 pr=2 a=4141 h=0 m=286/0/0/0/0
10.3.3.150 255.255.255.255 10.3.3.150 p=0 i=6 t=3 pr=2 a=4141 h=0 m=286/0/0/0/0
10.3.3.151 255.255.255.255 10.3.3.150 p=0 i=6 t=3 pr=2 a=4141 h=0 m=286/0/0/0/0
10.4.0.1 255.255.255.255 10.4.3.181 p=0 i=3 t=4 pr=3 a=0 h=0 m=26/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=29395 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=29395 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=29395 h=0 m=306/0/0/0/0
192.168.194.0 255.255.254.0 192.168.194.251 p=0 i=3 t=3 pr=2 a=18246 h=0 m=281/0/0/0/0
192.168.194.251 255.255.255.255 192.168.194.251 p=0 i=3 t=3 pr=2 a=18246 h=0 m=281/0/0/0/0
192.168.195.255 255.255.255.255 192.168.194.251 p=0 i=3 t=3 pr=2 a=18246 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=29395 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 10.3.3.150 p=0 i=6 t=3 pr=2 a=29376 h=0 m=286/0/0/0/0
224.0.0.0 240.0.0.0 192.168.194.251 p=0 i=3 t=3 pr=2 a=29371 h=0 m=281/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=29395 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 10.3.3.150 p=0 i=6 t=3 pr=2 a=29376 h=0 m=286/0/0/0/0
255.255.255.255 255.255.255.255 192.168.194.251 p=0 i=3 t=3 pr=2 a=29371 h=0 m=281/0/0/0/0
SYSTEM ADAPTER LIST
Realtek PCIe GBE Family Controller
Index = 16
GUID = {A4420123-438A-4778-978B-B415CB74FF16}
IP = 0.0.0.0/0.0.0.0
MAC = 60:a4:4c:d5:f6:74
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Sun Jan 19 19:32:08 2014
DHCP LEASE EXPIRES = Sun Jan 19 19:32:08 2014
DNS SERV =
Carte virtuelle directe Wi-Fi Microsoft
Index = 15
GUID = {6AEAE704-B417-46CA-9505-DB673F453B65}
IP = 0.0.0.0/0.0.0.0
MAC = 0c:8b:fd:1c:1f:52
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Sun Jan 19 19:32:08 2014
DHCP LEASE EXPIRES = Sun Jan 19 19:32:08 2014
DNS SERV =
TAP-Windows Adapter V9
Index = 6
GUID = {8C5F2084-CEF8-4142-9B00-C637664DB441}
IP = 10.3.3.150/255.255.255.252
MAC = 00:ff:8c:5f:20:84
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV = 10.3.3.149/255.255.255.255
DHCP LEASE OBTAINED = Sun Jan 19 18:23:07 2014
DHCP LEASE EXPIRES = Mon Jan 19 18:23:07 2015
PRI WINS = 10.3.0.1/255.255.255.255
SEC WINS =
DNS SERV = 10.3.0.1/255.255.255.255
Intel(R) Dual Band Wireless-N 7260
Index = 3
GUID = {CF2E0A98-93A3-4767-A059-C05F8C9687E4}
IP = 192.168.194.251/255.255.254.0
MAC = 0c:8b:fd:1c:1f:51
GATEWAY = 192.168.195.254/255.255.255.255
DHCP SERV = 1.1.1.1/255.255.255.255
DHCP LEASE OBTAINED = Sun Jan 19 19:21:04 2014

DHCP LEASE EXPIRES = Sun Jan 19 19:51:04 2014
DNS SERV = 193.50.27.66/255.255.255.255 193.50.27.67/255.255.255.255
Sun Jan 19 19:32:09 2014 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.195.254 192.168.194.251 9999
0.0.0.0 0.0.0.0 10.4.3.181 10.3.3.150 30
10.3.3.148 255.255.255.252 10.3.3.150 10.3.3.150 286
10.3.3.150 255.255.255.255 10.3.3.150 10.3.3.150 286
10.3.3.151 255.255.255.255 10.3.3.150 10.3.3.150 286
10.4.0.1 255.255.255.255 10.4.3.181 192.168.194.251 26
88.190.203.75 255.255.255.255 192.168.195.254 192.168.194.251 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
192.168.194.0 255.255.254.0 192.168.194.251 192.168.194.251 281
192.168.194.251 255.255.255.255 192.168.194.251 192.168.194.251 281
192.168.195.255 255.255.255.255 192.168.194.251 192.168.194.251 281
193.51.224.144 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.148 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.152 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.154 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.155 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.159 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.163 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.165 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.166 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.170 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.174 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.176 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.177 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.181 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.185 255.255.255.255 192.168.195.254 192.168.194.251 25
193.51.224.187 255.255.255.255 192.168.195.254 192.168.194.251 25
193.54.6.236 255.255.255.255 192.168.195.254 192.168.194.251 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 10.3.3.150 10.3.3.150 286
224.0.0.0 240.0.0.0 192.168.194.251 192.168.194.251 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.3.3.150 10.3.3.150 286
255.255.255.255 255.255.255.255 192.168.194.251 192.168.194.251 281

Réponses

  • Salut,

    Va dans la liste de tes connexions réseau Windows et désactive la connexion "FrozenWay", puis réactive là.

    Pour garder la connexion à FrozenWay active malgré le popup à laisser ouvert, il faut ajouter l'url de cette fenêtre dans les options réseau de FrozenWay / Redirections statiques / Destination.
  • Salut et merci ! Ça fonctionne en désactivant/réactivant le connexion FW quand j'ai le problème, sachant que j'avais déjà la redirection statique.
Cette discussion a été fermée.