abbrechen
Suchergebnisse werden angezeigt für 
Stattdessen suchen nach 
Meintest du 
Aktuelle Eilmeldungen

TV: Kabelfernsehen wird Mietersache. Jetzt handeln!
Deine Störung ist nicht dabei? Dann nutz unseren Störungsfinder!

1

Frage

2

Antwort

3

Lösung

Big Packet loss on router - Compal CH7466CE
alexnastas1
Digitalisierer
Digitalisierer

Hello, 

I'm sorry that it's in english. I moved to Germany one year ago and my German is not so good. 

I have big packet loss on the cable router. 

Everything is ok when I do a normal ping to the gateway (192.168.44.1)

However, when I send a fast-ping (ping 192.168.44.1 -i 0.1) (10 packets / second), after the packet 20 - i start having very big loss: 

 

147 packets transmitted, 21 packets received, 85.7% packet loss
round-trip min/avg/max/stddev = 2.345/4.507/11.967/2.175 ms

same with MTR: 

 

Alexs-MacBook-Pro-2.local (192.168.44.5)                                                                                                                        2018-10-30T10:45:45+0100
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                                                                                                Packets               Pings
 Host                                                                                                                                         Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. compalhub.home                                                                                                                            99.5%   194    6.1   6.1   6.1   6.1   0.0
 2. ???
 3. ip5886dd1e.static.kabel-deutschland.de                                                                                                     0.0%   193   10.4  13.7   9.5 169.3  12.3
 4. ip5886c2cd.static.kabel-deutschland.de                                                                                                     0.0%   193   11.1  15.3  10.4 226.0  18.5
 5. ip5886edf8.static.kabel-deutschland.de                                                                                                     0.0%   193   16.1  19.0  15.8 150.7   9.8
 6. ip5886eda1.static.kabel-deutschland.de                                                                                                     0.0%   193   18.0  18.8  13.6 103.4  10.9
 7. 100ge7-2.core1.fra1.he.net                                                                                                                 0.0%   193   14.9  17.8  14.0 206.9  13.9
 8. 100ge1-1.core1.par2.he.net                                                                                                                 0.0%   193   30.5  41.0  23.0 221.5  27.5
 9. 100ge14-1.core1.nyc4.he.net                                                                                                                0.0%   193   96.8 100.6  93.9 312.9  25.7
10. 100ge16-1.core1.sjc2.he.net                                                                                                                1.6%   193  161.1 162.9 157.9 241.0   8.7
11. v1537.core3.fmt2.he.net                                                                                                                    2.1%   193  171.8 179.6 157.3 409.3  44.3

These tests have been done via wired ethernet connection (not Wifi). I have tried disabling the Firewalling function on the router and restarting it. Nothing changes. Whenever I start sending packet bursts - it starts choking and stops forwarding. 

 

Anyone has any idea ? 

Thanks in advance

Alex

1 Akzeptierte Lösung

Akzeptierte Lösungen

Ok ! 

 

So after some extensive testing I have found out that the link seems to be ok. 

It turns out that only bursts with the destination IP of the router itself, get dropped. This must be some kind of a DDoS protection of the router. 

 

If I actually try to ping google or some other public IP, then the results are ok. 

 

sudo ping google.com -i 0.01 -c 5000
64 bytes from 172.217.23.174: icmp_seq=0 ttl=54 time=17.116 ms
64 bytes from 172.217.23.174: icmp_seq=1 ttl=54 time=17.606 ms
64 bytes from 172.217.23.174: icmp_seq=2 ttl=54 time=15.737 ms
64 bytes from 172.217.23.174: icmp_seq=3 ttl=54 time=16.875 ms
....

--- google.com ping statistics ---
5000 packets transmitted, 4999 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 10.419/17.042/43.682/2.936 ms

Only 1 packet lost from 5000 packets, sent with a rate of 100 packet/second. Which is an acceptable loss  rate

 

Jens, 

Thanks for your help

The issue may be closed. 

 

Regards

Alex

Lösung in ursprünglichem Beitrag anzeigen

13 Antworten 13
alexnastas1
Digitalisierer
Digitalisierer

Anyone has any idea ? It can't be that I'm the only one to have this issue. Is this a case to request a router change ? 

Vodafone support guys, 

 

Please advise on how to proceed

Jens
Moderator:in
Moderator:in

Hello alexnastas1,

 

sorry for the late reply. Did you checked a other ethernet cable? And is it the same on another port?

 

Regards

Jens

Bewertet hilfreiche Beiträge mit Likes und Sternen!
alexnastas1
Digitalisierer
Digitalisierer
Hi Jens,

Well, I checked over wifi and wired connection. And I have the exact same behaviour. So I kinda excluded the Cable and Port problem.

But i can check, no problem
Will check in 1h and write back

Just checked. It's exactly the same behaviour. 

 

ping 192.168.44.1 -i 0.1
PING 192.168.44.1 (192.168.44.1): 56 data bytes
64 bytes from 192.168.44.1: icmp_seq=0 ttl=64 time=6.446 ms
64 bytes from 192.168.44.1: icmp_seq=1 ttl=64 time=5.271 ms
64 bytes from 192.168.44.1: icmp_seq=2 ttl=64 time=4.188 ms
64 bytes from 192.168.44.1: icmp_seq=3 ttl=64 time=5.560 ms
64 bytes from 192.168.44.1: icmp_seq=4 ttl=64 time=3.892 ms
64 bytes from 192.168.44.1: icmp_seq=5 ttl=64 time=4.090 ms
64 bytes from 192.168.44.1: icmp_seq=6 ttl=64 time=4.014 ms
64 bytes from 192.168.44.1: icmp_seq=7 ttl=64 time=4.902 ms
64 bytes from 192.168.44.1: icmp_seq=8 ttl=64 time=5.465 ms
64 bytes from 192.168.44.1: icmp_seq=9 ttl=64 time=4.295 ms
64 bytes from 192.168.44.1: icmp_seq=10 ttl=64 time=5.724 ms
64 bytes from 192.168.44.1: icmp_seq=11 ttl=64 time=6.047 ms
64 bytes from 192.168.44.1: icmp_seq=12 ttl=64 time=7.920 ms
64 bytes from 192.168.44.1: icmp_seq=13 ttl=64 time=9.299 ms
64 bytes from 192.168.44.1: icmp_seq=14 ttl=64 time=5.178 ms
64 bytes from 192.168.44.1: icmp_seq=15 ttl=64 time=7.125 ms
64 bytes from 192.168.44.1: icmp_seq=16 ttl=64 time=5.264 ms
64 bytes from 192.168.44.1: icmp_seq=17 ttl=64 time=4.403 ms
64 bytes from 192.168.44.1: icmp_seq=18 ttl=64 time=6.122 ms
64 bytes from 192.168.44.1: icmp_seq=19 ttl=64 time=4.228 ms
Request timeout for icmp_seq 20
64 bytes from 192.168.44.1: icmp_seq=21 ttl=64 time=4.648 ms
Request timeout for icmp_seq 22
64 bytes from 192.168.44.1: icmp_seq=23 ttl=64 time=10.203 ms
Request timeout for icmp_seq 24
64 bytes from 192.168.44.1: icmp_seq=25 ttl=64 time=5.392 ms
Request timeout for icmp_seq 26
64 bytes from 192.168.44.1: icmp_seq=27 ttl=64 time=9.378 ms
Request timeout for icmp_seq 28
64 bytes from 192.168.44.1: icmp_seq=29 ttl=64 time=11.379 ms
Request timeout for icmp_seq 30
64 bytes from 192.168.44.1: icmp_seq=31 ttl=64 time=4.142 ms
Request timeout for icmp_seq 32
64 bytes from 192.168.44.1: icmp_seq=33 ttl=64 time=6.272 ms
Request timeout for icmp_seq 34
64 bytes from 192.168.44.1: icmp_seq=35 ttl=64 time=4.350 ms
Request timeout for icmp_seq 36
64 bytes from 192.168.44.1: icmp_seq=37 ttl=64 time=3.621 ms
^C
--- 192.168.44.1 ping statistics ---
38 packets transmitted, 29 packets received, 23.7% packet loss
round-trip min/avg/max/stddev = 3.621/5.821/11.379/1.988 ms
Jens
Moderator:in
Moderator:in

Hello alexnastas1,

 

thanks for that. Give me your private data in a pm. 🙂

 

Regards

Jens

Bewertet hilfreiche Beiträge mit Likes und Sternen!

Hi Jens, 

 

Thanks a lot, I just sent you the details that you asked for. 

Hi Jens, 

 

What comes next for me in this case ? 

Will there be an equipment exchange or something ? 

It's just that I have some travels planned during December, here and there and would like to plan accordingly

 

Thanks

Alex

Jens
Moderator:in
Moderator:in

Hey Alex,

 

can't see some problems at the cablerouter. But in this time, i see some issues from the signal to the cablerouter. This may have led to impairments.

Is it still like that now? If yes, please check your port forwarding or make  a factory reset.

 

Regards

Jens

Bewertet hilfreiche Beiträge mit Likes und Sternen!

Hi Jens, 

 

I just did a hard-reset and nothing has changed. This is what the PING output looks like for 100 packets: 

 

 $ ping 192.168.0.1 -i 0.1 -c 100
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=2.687 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.548 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=3.153 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.981 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=2.426 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=2.899 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=2.876 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=2.795 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=3.341 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=2.211 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=2.454 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=2.558 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=2.969 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=2.000 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=1.966 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=2.733 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=2.512 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=2.399 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=2.570 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=2.359 ms
Request timeout for icmp_seq 20
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=2.101 ms
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28
Request timeout for icmp_seq 29
Request timeout for icmp_seq 30
Request timeout for icmp_seq 31
Request timeout for icmp_seq 32
Request timeout for icmp_seq 33
Request timeout for icmp_seq 34
Request timeout for icmp_seq 35
Request timeout for icmp_seq 36
Request timeout for icmp_seq 37
Request timeout for icmp_seq 38
Request timeout for icmp_seq 39
Request timeout for icmp_seq 40
Request timeout for icmp_seq 41
Request timeout for icmp_seq 42
Request timeout for icmp_seq 43
Request timeout for icmp_seq 44
Request timeout for icmp_seq 45
Request timeout for icmp_seq 46
Request timeout for icmp_seq 47
Request timeout for icmp_seq 48
Request timeout for icmp_seq 49
Request timeout for icmp_seq 50
Request timeout for icmp_seq 51
Request timeout for icmp_seq 52
Request timeout for icmp_seq 53
Request timeout for icmp_seq 54
Request timeout for icmp_seq 55
Request timeout for icmp_seq 56
Request timeout for icmp_seq 57
Request timeout for icmp_seq 58
Request timeout for icmp_seq 59
Request timeout for icmp_seq 60
Request timeout for icmp_seq 61
Request timeout for icmp_seq 62
Request timeout for icmp_seq 63
Request timeout for icmp_seq 64
Request timeout for icmp_seq 65
Request timeout for icmp_seq 66
Request timeout for icmp_seq 67
Request timeout for icmp_seq 68
Request timeout for icmp_seq 69
Request timeout for icmp_seq 70
Request timeout for icmp_seq 71
Request timeout for icmp_seq 72
Request timeout for icmp_seq 73
Request timeout for icmp_seq 74
Request timeout for icmp_seq 75
Request timeout for icmp_seq 76
Request timeout for icmp_seq 77
Request timeout for icmp_seq 78
Request timeout for icmp_seq 79
Request timeout for icmp_seq 80
Request timeout for icmp_seq 81
Request timeout for icmp_seq 82
Request timeout for icmp_seq 83
Request timeout for icmp_seq 84
Request timeout for icmp_seq 85
Request timeout for icmp_seq 86
Request timeout for icmp_seq 87
Request timeout for icmp_seq 88
Request timeout for icmp_seq 89
Request timeout for icmp_seq 90
Request timeout for icmp_seq 91
Request timeout for icmp_seq 92
Request timeout for icmp_seq 93
Request timeout for icmp_seq 94
Request timeout for icmp_seq 95
Request timeout for icmp_seq 96
Request timeout for icmp_seq 97
Request timeout for icmp_seq 98

--- 192.168.0.1 ping statistics ---
100 packets transmitted, 21 packets received, 79.0% packet loss
round-trip min/avg/max/stddev = 1.966/2.597/3.341/0.358 ms

PLEASE, let us take some kind of action on this issue. This has been going on for too long now. I'm ready to provide any kind of details. I'm a network engineer, so I have perfect knowledge of how this works and I can guarantee that everything on my end is well. (cabling, wifi, IP parameters, etc...). I think that the cable modem has an issue. Maybe a firmware update would solve this - if not - it just needs replacing. 

 

I would call the phone support, to take more urgent action on this - but I'm not profecient in German, so this will take me nowhere. 

 

Please, tell me what should be my next steps. 

 

Thank you 

Alex