Jump to content

Ping Plotter showing over 50% packet loss on R1


Joe

Recommended Posts

I've posted about this in this thread: http://forum.netduma.com/topic/19906-ping-plotter-showing-packet-loss/. But I'm now starting my own thread for less confusion. I apologize for the sloppiness. Just bringing my posts over here so that everything is in one place for my own specific problem. Thanks.

 

 

"I'm having the same issue when pinging the R1 with Ping Plotter. I tried using different cables at first but I was still getting about 55-58% packet loss to the R1. I then tried a test directly connected to my ISP router (Technicolor tc8305c) without the R1 with the same cables I used for the R1 tests and I got zero packet loss (multiple tests as well). Any thoughts on what could be causing that much packet loss to my R1? It's very strange because my gaming seems to run OK, but I imagine it would run 100x smoother if I reduced over 50% packet loss like that."

 

 

"My results with the R1: https://share.pingpl...com/dq9fQQMJx23

 

With my ISP router: https://share.pingpl...com/Ls6tgKcKGS4

 

Just copy and paste the last 11 characters of the link to view the results. Thanks."

 

 

 

Note: I'm using 2.5 second intervals for my Ping Plotter test. The cable is also not the issue because I've tried switching it already, and got no packet loss to my ISP router but did on my R1.

 

 

 

 

 

 

Link to comment
Share on other sites

I can't see those ping plotter results at all, can you just take screenshots and upload here please.

Sure thing.  1485193735-U6326.png

 

1485193818-U6326.png     

Link to comment
Share on other sites

  • Administrators

Well it appears you're having packet loss on a hop way down the line which you can't do anything about. Doesn't seem to affect your over all ping that much. If you look at the graphs you can see that big red line which occurs on both graphs so appears it could be an issue with your line. 

 

I would continue to test direct without the duma and see if it keeps occurring.

Link to comment
Share on other sites

Well it appears you're having packet loss on a hop way down the line which you can't do anything about. Doesn't seem to affect your over all ping that much. If you look at the graphs you can see that big red line which occurs on both graphs so appears it could be an issue with your line. 

 

I would continue to test direct without the duma and see if it keeps occurring.

Maybe this screenshot of a test I did to Google is better. For some reason I get that packet loss at the bottom of the line ONLY to pingplotter.com. As you can see in this screenshot to Google, it's only appearing at hop1. My ping looks good, my bufferbloat is good (http://www.dslreports.com/speedtest/9319338), but that packet loss is very high to my R1. As I have said, I get zero packet loss when doing these tests to my ISP router. For whatever reason, pingplotter.com is the only thing that gives me all that packet loss at the bottom of the line.

 

 

1485195440-U6326.png

Link to comment
Share on other sites

Have you switched out the Ethernet from your modem/router to the Netduma to rule out a bad cable?

Yes. That was the first thing I did but I was still getting all that packet loss at hop1. 

Link to comment
Share on other sites

What happens if you slow the interval down to say 5 and restart the test?

It actually shows even more packet loss at 5 seconds. 

 

 

1485202984-U6326.png

Link to comment
Share on other sites

Is it unusual that I'm getting this amount of packet loss but still a good ping? I get my full speeds with exceptional results for everything (and no packet loss) when doing an Internet Diagnostics test on my Duma, but as you can see my results on ping plotter show a ridiculous amount of packet loss lol I would assume it's only a cable issue, but I've already ruled out that it's not because my ISP router shows no packet loss using the same cable.  

Link to comment
Share on other sites

I think there maybe a bug with ping plotter with your set up.

 

On a windows machine, start > run > type cmd > type

 

ping twitter.com -n 25

 

or

 

ping twitter.co.uk -n 25

 

This will ping twitter 25 times if it shows no packet loss its a ping plotter bug.

Link to comment
Share on other sites

I think there maybe a bug with ping plotter with your set up.

 

On a windows machine, start > run > type cmd > type

 

ping twitter.com -n 25

 

or

 

ping twitter.co.uk -n 25

 

This will ping twitter 25 times if it shows no packet loss its a ping plotter bug.

 

I'm hoping it's just a bug like you say lol Still kind of seems odd though if I'm getting a massive 50-80% loss, while getting zero loss on my ISP router. 

 

Here's the results:

 

Reply from 104.244.42.1: bytes=32 time=33ms TTL=54
Reply from 104.244.42.1: bytes=32 time=30ms TTL=54
Reply from 104.244.42.1: bytes=32 time=32ms TTL=54
Reply from 104.244.42.1: bytes=32 time=29ms TTL=54
Reply from 104.244.42.1: bytes=32 time=28ms TTL=54
Reply from 104.244.42.1: bytes=32 time=28ms TTL=54
Reply from 104.244.42.1: bytes=32 time=29ms TTL=54
Reply from 104.244.42.1: bytes=32 time=29ms TTL=54
Reply from 104.244.42.1: bytes=32 time=29ms TTL=54
Reply from 104.244.42.1: bytes=32 time=30ms TTL=54
Reply from 104.244.42.1: bytes=32 time=28ms TTL=54
Reply from 104.244.42.1: bytes=32 time=31ms TTL=54
Reply from 104.244.42.1: bytes=32 time=29ms TTL=54
Reply from 104.244.42.1: bytes=32 time=33ms TTL=54
Reply from 104.244.42.1: bytes=32 time=28ms TTL=54
Reply from 104.244.42.1: bytes=32 time=28ms TTL=54
Reply from 104.244.42.1: bytes=32 time=28ms TTL=54
Reply from 104.244.42.1: bytes=32 time=29ms TTL=54
Reply from 104.244.42.1: bytes=32 time=28ms TTL=54
Reply from 104.244.42.1: bytes=32 time=28ms TTL=54
Reply from 104.244.42.1: bytes=32 time=29ms TTL=54
Reply from 104.244.42.1: bytes=32 time=24ms TTL=54
Reply from 104.244.42.1: bytes=32 time=30ms TTL=54
Reply from 104.244.42.1: bytes=32 time=30ms TTL=54
Reply from 104.244.42.1: bytes=32 time=36ms TTL=54
 
Ping statistics for 104.244.42.1:
    Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 24ms, Maximum = 36ms, Average = 29ms
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...