Jump to content

13% packet loss?


jeycee

Recommended Posts

Hi Guys,

 

i have a problem here if if test on my mac (terminal) traceroute..

 

exampel:

 

traceroute -S -q 30 www.golem.de > ~/Desktop/pathping.txt

 

then the Duma cause 13% packet loss

 

see here:

 

1  r1 (192.168.88.1)  0.625 ms  0.405 ms  0.410 ms  0.290 ms  0.278 ms  0.275 ms *  0.501 ms  0.309 ms  0.283 ms  0.297 ms  0.291 ms *  0.489 ms  0.372 ms  0.301 ms  0.298 ms  0.299 ms *  0.487 ms  0.383 ms  0.304 ms  0.287 ms  0.284 ms *  0.482 ms  0.374 ms  0.378 ms  0.296 ms  0.285 ms

 

(13% loss)

 

 

 2  192.168.1.1 (192.168.1.1)  0.743 ms  0.518 ms  0.488 ms  0.449 ms  0.446 ms  0.435 ms  0.473 ms  0.437 ms  0.459 ms  0.437 ms  0.558 ms  0.443 ms  0.562 ms  0.429 ms  0.485 ms  0.446 ms  0.472 ms  0.443 ms  0.517 ms  0.440 ms  0.436 ms  0.463 ms  0.436 ms  0.431 ms  0.463 ms  0.498 ms  0.437 ms  0.440 ms  0.440 ms  0.503 ms
 
(0% loss)
 
If i disconnect the Duma and use my DLink modem only ... 0% Loss
 
 
I have tested it also with my TP-Link Modem (Dlink is disconected) and this Modem cause also 13% packet loss,
so if i have the TP-Link + the Duma both cause 13% packet loss...
 
see here:
 
 1  r1 (192.168.88.1)  0.531 ms  0.316 ms  0.288 ms  0.284 ms  0.280 ms  0.280 ms *  0.426 ms  0.367 ms  0.324 ms  0.289 ms  0.288 ms *  0.510 ms  0.297 ms  0.291 ms  0.274 ms  0.271 ms *  0.469 ms  0.358 ms  0.300 ms  0.290 ms  0.271 ms *  0.509 ms  0.392 ms  0.358 ms  0.294 ms  0.291 ms (13% loss)
 2  192.168.1.1 (192.168.1.1)  0.815 ms  0.674 ms  0.601 ms  0.584 ms  0.580 ms  0.582 ms *  0.890 ms  0.681 ms  0.656 ms  0.650 ms  0.651 ms *  0.859 ms  0.603 ms  0.599 ms  0.586 ms  0.581 ms *  0.841 ms  0.690 ms  0.657 ms  0.661 ms  0.660 ms *  0.878 ms  0.685 ms  0.702 ms  0.717 ms  0.704 ms (13% loss)
 3  rdsl-mnch-de81.nw.mediaways.net (213.20.57.11)  18.550 ms  6.457 ms  6.833 ms  6.396 ms  6.283 ms  6.137 ms  7.129 ms  6.913 ms  6.371 ms  6.211 ms  6.476 ms  6.602 ms  7.505 ms  6.087 ms  6.370 ms  7.031 ms  6.327 ms  6.135 ms  6.106 ms  6.397 ms  6.779 ms  6.566 ms  7.306 ms  7.218 ms  6.104 ms  6.849 ms  6.336 ms  7.046 ms  17.740 ms  7.667 ms
(0% loss)
 
 
Can anybody explain it to me?
 
How i said if i disconnect the Duma and TP-Link Modem and use my old Dlink Modem... 0% Loss
 
Thank You very much guys
 
 
Link to comment
Share on other sites

Hmm that's very strange that they both do that. Can you try swapping out ethernet cables please?

no, still the same Dlink 0% loss / Tp-Link and Netduma 13% loss  :blink: (both)

Link to comment
Share on other sites

 

Hi Guys,

 

i have a problem here if if test on my mac (terminal) traceroute..

 

exampel:

 

traceroute -S -q 30 www.golem.de > ~/Desktop/pathping.txt

 

then the Duma cause 13% packet loss

 

see here:

 

1  r1 (192.168.88.1)  0.625 ms  0.405 ms  0.410 ms  0.290 ms  0.278 ms  0.275 ms *  0.501 ms  0.309 ms  0.283 ms  0.297 ms  0.291 ms *  0.489 ms  0.372 ms  0.301 ms  0.298 ms  0.299 ms *  0.487 ms  0.383 ms  0.304 ms  0.287 ms  0.284 ms *  0.482 ms  0.374 ms  0.378 ms  0.296 ms  0.285 ms

 

(13% loss)

 

 

 2  192.168.1.1 (192.168.1.1)  0.743 ms  0.518 ms  0.488 ms  0.449 ms  0.446 ms  0.435 ms  0.473 ms  0.437 ms  0.459 ms  0.437 ms  0.558 ms  0.443 ms  0.562 ms  0.429 ms  0.485 ms  0.446 ms  0.472 ms  0.443 ms  0.517 ms  0.440 ms  0.436 ms  0.463 ms  0.436 ms  0.431 ms  0.463 ms  0.498 ms  0.437 ms  0.440 ms  0.440 ms  0.503 ms
 
(0% loss)
 
If i disconnect the Duma and use my DLink modem only ... 0% Loss
 
 
I have tested it also with my TP-Link Modem (Dlink is disconected) and this Modem cause also 13% packet loss,
so if i have the TP-Link + the Duma both cause 13% packet loss...
 
see here:
 
 1  r1 (192.168.88.1)  0.531 ms  0.316 ms  0.288 ms  0.284 ms  0.280 ms  0.280 ms *  0.426 ms  0.367 ms  0.324 ms  0.289 ms  0.288 ms *  0.510 ms  0.297 ms  0.291 ms  0.274 ms  0.271 ms *  0.469 ms  0.358 ms  0.300 ms  0.290 ms  0.271 ms *  0.509 ms  0.392 ms  0.358 ms  0.294 ms  0.291 ms (13% loss)
 2  192.168.1.1 (192.168.1.1)  0.815 ms  0.674 ms  0.601 ms  0.584 ms  0.580 ms  0.582 ms *  0.890 ms  0.681 ms  0.656 ms  0.650 ms  0.651 ms *  0.859 ms  0.603 ms  0.599 ms  0.586 ms  0.581 ms *  0.841 ms  0.690 ms  0.657 ms  0.661 ms  0.660 ms *  0.878 ms  0.685 ms  0.702 ms  0.717 ms  0.704 ms (13% loss)
 3  rdsl-mnch-de81.nw.mediaways.net (213.20.57.11)  18.550 ms  6.457 ms  6.833 ms  6.396 ms  6.283 ms  6.137 ms  7.129 ms  6.913 ms  6.371 ms  6.211 ms  6.476 ms  6.602 ms  7.505 ms  6.087 ms  6.370 ms  7.031 ms  6.327 ms  6.135 ms  6.106 ms  6.397 ms  6.779 ms  6.566 ms  7.306 ms  7.218 ms  6.104 ms  6.849 ms  6.336 ms  7.046 ms  17.740 ms  7.667 ms
(0% loss)
 
 
Can anybody explain it to me?
 
How i said if i disconnect the Duma and TP-Link Modem and use my old Dlink Modem... 0% Loss
 
Thank You very much guys
 
Check your MTU and change accordingly in Router and console. Use this http://www.letmecheck.it/mtu-test.php

 

Link to comment
Share on other sites

 

 

 
Check your MTU and change accordingly in Router and console. Use this http://www.letmecheck.it/mtu-test.php

 

 

no, still the same 13% does anybody have a mac to test his duma or tp-link with the traceroute... like this

traceroute -S -q 30 www.google.com > ~/Desktop/pathping.txt

 

or am i the only one with 13% loss  :D 

Link to comment
Share on other sites

Are your congestion control sliders set to 100% when testing? If not try that and test again. Also press reset distribution on that page.

yes of course man :) the TP-Link modem router does the same... only my old Dlink DSL modem has 0% packet loss, i dont understand it.

if i do the duma  Ping Diagnostics everything is green and perfect. just wondering about the 13%...

Link to comment
Share on other sites

I have seen higher pings from a test in the past and rebooted my pc and whalla back to normal, glitch's with machines can cause this.

 

This might not be your case but it is worth doing.

 

So reboot your machine, reboot the duma from settings misc and try again jaycee.

Link to comment
Share on other sites

  • Administrators

Can you also try instead of doing a trace route

 

ping 8.8.8.8 in the terminal

 

let it run for a little while like 100 pings or so, and then press Cmd + C to stop it, it should give you the statistics including packet loss, do you get the same packet loss this way?

Link to comment
Share on other sites

Thank you fraser :)

 

153 packets transmitted, 153 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 4.724/5.479/6.688/0.304 ms

 

in terminal no loss...

 

 

with this command "traceroute -S -q 30 8.8.8.8 > ~/Desktop/pathping.txt"   13% loss  ...i dont understand it  :blink:

 

interesting (?)

Link to comment
Share on other sites

I have seen higher pings from a test in the past and rebooted my pc and whalla back to normal, glitch's with machines can cause this.

 

This might not be your case but it is worth doing.

 

So reboot your machine, reboot the duma from settings misc and try again jaycee.

Thank you Zennon.. will try it out...

Link to comment
Share on other sites

  • Administrators

Thank you fraser :)

 

153 packets transmitted, 153 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 4.724/5.479/6.688/0.304 ms

 

in terminal no loss...

 

 

with this command "traceroute -S -q 30 8.8.8.8 > ~/Desktop/pathping.txt"   13% loss  ...i dont understand it  :blink:

 

interesting (?)

 

Tried the exact same command and through my ISP router I got 13% loss exactly. It seems to me that this must be quite common, we already know that trace can be quite inaccurate so I would not worry about this at all if I'm honest

Link to comment
Share on other sites

Tried the exact same command and through my ISP router I got 13% loss exactly. It seems to me that this must be quite common, we already know that trace can be quite inaccurate so I would not worry about this at all if I'm honest

Great! Thank you much for testing this, very much appreciated.

 

cheers Fraser, great support as always here!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

Guest
This topic is now closed to further replies.
×
×
  • Create New...