Solved

Packet loss 5%

4 years ago

Hallo zusammen,

 

ich hab hier auf meiner DSL-Leitung (MagentaZuhause L, 100/40Mbit) rund 5% packet loss was ein Remote-Arbeiten per ssh vergleichsweise schwierig macht.

 

Problem:

Packet-Loss von rund 5%

 

Analyse:

== ping von Gateway zu Speedport:

$ ping -c 100 192.168.2.1
PING 192.168.2.1 (192.168.2.1): 56 data bytes
64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=1,022 ms
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=1,795 ms

...
64 bytes from 192.168.2.1: icmp_seq=99 ttl=64 time=1,265 ms
--- 192.168.2.1 ping statistics ---
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0,658/1,092/3,755/0,335 ms

 

== ping von einem LAN-Device zu Gateway:

$ ping -c 100 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 Bytes von 192.168.1.2: icmp_seq=1 ttl=64 Zeit=1.27 ms
64 Bytes von 192.168.1.2: icmp_seq=2 ttl=64 Zeit=1.23 ms

...
64 Bytes von 192.168.1.2: icmp_seq=99 ttl=64 Zeit=1.03 ms
64 Bytes von 192.168.1.2: icmp_seq=100 ttl=64 Zeit=1.01 ms

--- 192.168.1.2 ping statistics ---
100 Pakete übertragen, 100 empfangen, 0% packet loss, time 99240ms
rtt min/avg/max/mdev = 0.425/1.184/1.771/0.201 ms

 

btw, von nem LAN-Device direkt zum Speedport gibt ebenfalls 0%

 

== ping vom Gateway zu einer mir bekannten hochgradig stabilen Internet-Adresse:

$ ping -c 100 217.x.x.1
PING 217.x.x.1 (217.x.x.1): 56 data bytes
64 bytes from 217.x.x.1: icmp_seq=0 ttl=61 time=10,608 ms
64 bytes from 217.x.x.1: icmp_seq=1 ttl=61 time=9,425 ms

...
64 bytes from 217.x.x.1: icmp_seq=98 ttl=61 time=9,014 ms
64 bytes from 217.x.x.1: icmp_seq=99 ttl=61 time=7,857 ms
--- 217.x.x.1 ping statistics ---
100 packets transmitted, 95 packets received, 5% packet loss
round-trip min/avg/max/stddev = 7,210/8,874/17,449/1,456 ms

 

== ping vom Gateway zu Google:

$ ping -c 100 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=119 time=6,310 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=6,432 ms

...

4 bytes from 8.8.8.8: icmp_seq=98 ttl=119 time=6,844 ms
64 bytes from 8.8.8.8: icmp_seq=99 ttl=119 time=6,339 ms
--- 8.8.8.8 ping statistics ---
100 packets transmitted, 97 packets received, 3% packet loss
round-trip min/avg/max/stddev = 5,470/6,850/25,245/2,670 ms

 

== ping mit ein bisschen mehr "Workload":

$ ping -c 100 -s 2048 217.x.x.1
PING 217.x.x.1 (217.x.x.1): 2048 data bytes
2056 bytes from 217.x.x.1: icmp_seq=0 ttl=61 time=10,963 ms
2056 bytes from 217.x.x.1: icmp_seq=1 ttl=61 time=8,559 ms

...

2056 bytes from 217.x.x.1: icmp_seq=98 ttl=61 time=8,652 ms
2056 bytes from 217.x.x.1: icmp_seq=99 ttl=61 time=14,756 ms
--- 217.x.x.1 ping statistics ---
100 packets transmitted, 95 packets received, 5% packet loss
round-trip min/avg/max/stddev = 7,911/9,912/18,357/1,876 ms

 

Frage:

Was kann man hier tun? Einen bestimmten Zeitpunkt ab dem die Probleme begannen kann ich leider nicht ausmachen.

Danke für ne Info!

 

--

Thomas

499

0

3

    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...

    This could help you too

    Solved

    in  

    15683

    0

    3

    Solved

    568

    0

    1