0 Membres et 1 Invité sur ce sujet
Pas sûr que ce soit Covage. Un problème DHCP chez K-Net je pense.@Stef, dès que tu perds tes ACL DHCP, tu ne ping plus même le premier hop, ce qui peut expliquer ton graph.
- Le résolveur 2 (plaque Nord 178.250.208.135) répond au ping mais pas aux requêtes DNS.
pju@fedora:~$ ping -4 -c 2 resolver2.k-net.frPING (178.250.208.135) 56(84) bytes of data.64 bytes from resolver2.kwaoo.net (178.250.208.135): icmp_seq=1 ttl=56 time=25.1 ms64 bytes from resolver2.kwaoo.net (178.250.208.135): icmp_seq=2 ttl=56 time=20.2 ms--- ping statistics ---2 packets transmitted, 2 received, 0% packet loss, time 1001msrtt min/avg/max/mdev = 20.222/22.657/25.092/2.435 mspju@fedora:~$ ping -c 2 resolver2.k-net.frPING resolver2.k-net.fr(resolver2.kwaoo.net (2a03:4980::f:0:6)) 56 data bytes64 bytes from resolver2.kwaoo.net (2a03:4980::f:0:6): icmp_seq=1 ttl=56 time=17.8 ms64 bytes from resolver2.kwaoo.net (2a03:4980::f:0:6): icmp_seq=2 ttl=56 time=16.5 ms--- resolver2.k-net.fr ping statistics ---2 packets transmitted, 2 received, 0% packet loss, time 1001msrtt min/avg/max/mdev = 16.501/17.160/17.820/0.659 mspju@fedora:~$ dig @resolver2.k-net.fr www.free.fr;; communications error to 2a03:4980::f:0:6#53: timed out;; communications error to 2a03:4980::f:0:6#53: timed out^Cpju@fedora:~$ dig -4 @resolver2.k-net.fr www.free.fr;; communications error to 178.250.208.135#53: timed out;; communications error to 178.250.208.135#53: timed out;; communications error to 178.250.208.135#53: timed out; <<>> DiG 9.18.24 <<>> -4 @resolver2.k-net.fr www.free.fr; (1 server found);; global options: +cmd;; no servers could be reached
Bonjour,T'es sur que SeRum et Krougher sont encore chez K-net? Il n'ont pas eu l'air coupé.
DHCP revenu à l'instant
K-Net