Doute sur ping!

Support Debian
#1

salut j’ai le résultat suivant avec ma lenny x86.
ca arrive souvent que les séquences soient mixé de la sorte??? même si je me trouve a mayotte ???

PING www.l.google.com (74.125.232.113) 56(84) bytes of data.
64 bytes from 74.125.232.113: icmp_seq=1 ttl=50 time=961 ms
64 bytes from 74.125.232.113: icmp_seq=3 ttl=49 time=1136 ms
64 bytes from 74.125.232.113: icmp_seq=2 ttl=50 time=685 ms
64 bytes from 74.125.232.113: icmp_seq=5 ttl=50 time=1382 ms
64 bytes from 74.125.232.113: icmp_seq=4 ttl=50 time=1540 ms
64 bytes from 74.125.232.113: icmp_seq=7 ttl=49 time=1130 ms
64 bytes from 74.125.232.113: icmp_seq=6 ttl=50 time=894 ms
64 bytes from 74.125.232.113: icmp_seq=8 ttl=50 time=630 ms
64 bytes from 74.125.232.113: icmp_seq=10 ttl=49 time=1262 ms
64 bytes from 74.125.232.113: icmp_seq=9 ttl=50 time=1098 ms
64 bytes from 74.125.232.113: icmp_seq=12 ttl=49 time=1817 ms
64 bytes from 74.125.232.113: icmp_seq=11 ttl=49 time=1392 ms
64 bytes from 74.125.232.113: icmp_seq=13 ttl=50 time=1297 ms

--- www.l.google.com ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 17979ms
rtt min/avg/max/mdev = 630.197/1171.582/1817.585/319.782 ms, pipe 3

ou encore ceci… commencer par 4 c’est pas mal hein ???

PING www.l.google.com (74.125.230.81) 56(84) bytes of data.
64 bytes from 74.125.230.81: icmp_seq=4 ttl=52 time=3083 ms
64 bytes from 74.125.230.81: icmp_seq=1 ttl=52 time=2081 ms
64 bytes from 74.125.230.81: icmp_seq=2 ttl=52 time=1093 ms
64 bytes from 74.125.230.81: icmp_seq=3 ttl=52 time=1027 ms
64 bytes from 74.125.230.81: icmp_seq=5 ttl=52 time=946 ms
64 bytes from 74.125.230.81: icmp_seq=7 ttl=52 time=1198 ms
64 bytes from 74.125.230.81: icmp_seq=6 ttl=52 time=1325 ms
64 bytes from 74.125.230.81: icmp_seq=8 ttl=52 time=1116 ms
64 bytes from 74.125.230.81: icmp_seq=10 ttl=52 time=1299 ms
64 bytes from 74.125.230.81: icmp_seq=9 ttl=52 time=1036 ms
64 bytes from 74.125.230.81: icmp_seq=11 ttl=52 time=1414 ms
64 bytes from 74.125.230.81: icmp_seq=12 ttl=52 time=1000 ms
64 bytes from 74.125.230.81: icmp_seq=15 ttl=52 time=2518 ms
64 bytes from 74.125.230.81: icmp_seq=13 ttl=52 time=1937 ms
64 bytes from 74.125.230.81: icmp_seq=14 ttl=52 time=1545 ms
64 bytes from 74.125.230.81: icmp_seq=16 ttl=52 time=4045 ms
64 bytes from 74.125.230.81: icmp_seq=17 ttl=52 time=633 ms
^C64 bytes from 74.125.230.81: icmp_seq=18 ttl=52 time=622 ms

en ping sur une machine local j’ai ceci…

#~/>ping 172.16.2.2
PING 172.16.2.2 (172.16.2.2) 56(84) bytes of data.
64 bytes from 172.16.2.2: icmp_seq=1 ttl=128 time=0.420 ms
64 bytes from 172.16.2.2: icmp_seq=2 ttl=128 time=0.209 ms
64 bytes from 172.16.2.2: icmp_seq=3 ttl=128 time=0.211 ms
64 bytes from 172.16.2.2: icmp_seq=4 ttl=128 time=0.198 ms
64 bytes from 172.16.2.2: icmp_seq=5 ttl=128 time=0.214 ms
64 bytes from 172.16.2.2: icmp_seq=6 ttl=128 time=0.219 ms
64 bytes from 172.16.2.2: icmp_seq=7 ttl=128 time=0.207 ms
64 bytes from 172.16.2.2: icmp_seq=8 ttl=128 time=0.205 ms
64 bytes from 172.16.2.2: icmp_seq=9 ttl=128 time=0.211 ms
64 bytes from 172.16.2.2: icmp_seq=10 ttl=128 time=0.203 ms
^C
--- 172.16.2.2 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8999ms
rtt min/avg/max/mdev = 0.198/0.229/0.420/0.066 ms

de loin ça ressemble à “dude in the middle” non ?

#2

Apparemment ta connexion a une latence très importante et fluctuante (satellite ?) qui est du même ordre de grandeur que l’intervalle par défaut entre les requêtes de ping (1 seconde). Dans ces conditions ce n’est pas étonnant que les réponses au ping arrivent dans le désordre. Si tu augmentes suffisamment l’intervalle avec l’option -i, les réponses devraient arriver dans l’ordre.

#3

j’ai un gros doute sur l’origine normal de ce comportement… aujourd’hui j’ai ca…

#~/>ping www.google.fr PING www.l.google.com (74.125.230.83) 56(84) bytes of data. 64 bytes from 74.125.230.83: icmp_seq=3 ttl=53 time=633 ms 64 bytes from 74.125.230.83: icmp_seq=4 ttl=54 time=622 ms 64 bytes from 74.125.230.83: icmp_seq=5 ttl=54 time=615 ms 64 bytes from 74.125.230.83: icmp_seq=12 ttl=53 time=697 ms 64 bytes from 74.125.230.83: icmp_seq=6 ttl=53 time=795 ms 64 bytes from 74.125.230.83: icmp_seq=17 ttl=54 time=601 ms 64 bytes from 74.125.230.83: icmp_seq=14 ttl=53 time=638 ms 64 bytes from 74.125.230.83: icmp_seq=80 ttl=54 time=649 ms 64 bytes from 74.125.230.83: icmp_seq=81 ttl=53 time=640 ms 64 bytes from 74.125.230.83: icmp_seq=82 ttl=54 time=651 ms 64 bytes from 74.125.230.83: icmp_seq=83 ttl=53 time=598 ms 64 bytes from 74.125.230.83: icmp_seq=84 ttl=54 time=616 ms 64 bytes from 74.125.230.83: icmp_seq=85 ttl=54 time=634 ms 64 bytes from 74.125.230.83: icmp_seq=86 ttl=53 time=658 ms 64 bytes from 74.125.230.83: icmp_seq=87 ttl=54 time=615 ms 64 bytes from 74.125.230.83: icmp_seq=88 ttl=54 time=646 ms 64 bytes from 74.125.230.83: icmp_seq=89 ttl=53 time=765 ms 64 bytes from 74.125.230.83: icmp_seq=90 ttl=54 time=610 ms 64 bytes from 74.125.230.83: icmp_seq=91 ttl=53 time=646 ms 64 bytes from 74.125.230.83: icmp_seq=92 ttl=53 time=616 ms 64 bytes from 74.125.230.83: icmp_seq=93 ttl=53 time=616 ms 64 bytes from 74.125.230.83: icmp_seq=94 ttl=54 time=658 ms 64 bytes from 74.125.230.83: icmp_seq=95 ttl=53 time=670 ms 64 bytes from 74.125.230.83: icmp_seq=96 ttl=53 time=634 ms 64 bytes from 74.125.230.83: icmp_seq=97 ttl=53 time=610 ms 64 bytes from 74.125.230.83: icmp_seq=98 ttl=53 time=604 ms 64 bytes from 74.125.230.83: icmp_seq=29 ttl=54 time=811 ms 64 bytes from 74.125.230.83: icmp_seq=100 ttl=54 time=784 ms 64 bytes from 74.125.230.83: icmp_seq=101 ttl=54 time=652 ms 64 bytes from 74.125.230.83: icmp_seq=102 ttl=54 time=832 ms 64 bytes from 74.125.230.83: icmp_seq=110 ttl=53 time=599 ms ^C --- www.l.google.com ping statistics --- 115 packets transmitted, 31 received, 73% packet loss, time 123984ms rtt min/avg/max/mdev = 598.267/658.937/832.069/65.435 ms, pipe 71

#4

Tu n’aurais pas un problème de ligne ou ce connexion tout simplement ?
J’ai déjà rencontré des taux de perte aussi importants sur des connexions rj45 pourries (câbles, fiches, prises murales…)

#5

nop! apparement, les câbles vont bien… ca m’aurrait fait mal…
mais même probleme sur deux T0-RNIS différentes. l’une braché en directe sur le LAN, l’autre au travers de la debian. (je precise que je perd plus de 40% des paquets en plus avec la deb vs WinSeven, cela dit, je me méfi des statistiques windoze). donc deux To atteinte par le même probleme ca sen le probleme de ligne FT.,

Quand on les appelles bien sûr c’est une erreur qui viens de chez nous…puis 5-30 minutes plus tard…CA Marche…

Est ce que le fait que mayotte dispose d’une connexion satellite surchargée peu créer ce genre de comportement qui disparait hors des heures de travail ?

[code]#~/>ping www.google.fr
PING www.l.google.com (74.125.230.84) 56(84) bytes of data.
64 bytes from 74.125.230.84: icmp_seq=1 ttl=54 time=607 ms
64 bytes from 74.125.230.84: icmp_seq=2 ttl=52 time=610 ms
64 bytes from 74.125.230.84: icmp_seq=3 ttl=52 time=628 ms
64 bytes from 74.125.230.84: icmp_seq=4 ttl=52 time=586 ms
64 bytes from 74.125.230.84: icmp_seq=5 ttl=52 time=604 ms
64 bytes from 74.125.230.84: icmp_seq=6 ttl=54 time=688 ms
64 bytes from 74.125.230.84: icmp_seq=7 ttl=52 time=598 ms
64 bytes from 74.125.230.84: icmp_seq=8 ttl=52 time=580 ms
64 bytes from 74.125.230.84: icmp_seq=9 ttl=54 time=621 ms
64 bytes from 74.125.230.84: icmp_seq=10 ttl=54 time=664 ms
64 bytes from 74.125.230.84: icmp_seq=11 ttl=54 time=688 ms
^C64 bytes from 74.125.230.84: icmp_seq=12 ttl=54 time=627 ms

— www.l.google.com ping statistics —
12 packets transmitted, 12 received, 0% packet loss, time 14505ms
rtt min/avg/max/mdev = 580.344/625.523/688.871/35.237 ms
[/code]

#6

Possible.
Il faut “pinguer” l’IP de la passerelle de ton FAI. Ce serait plus simple pour confirmer tes soupçons…