61

Sometimes just one hop on a link stops responding to pings, but I see big bars on all the later hops suggesting this isn't the issue, meaning it's real congestion.

62

The fact that packetloss goes to 2% from the second hop until the endhost on is a decent hint that the path between hop 1 and too introduces this packetloss and that seems to implicated your ISP. But don't you have another cable modem with the same ISP and in the same segment? If yes it would be quite interesting to the results of concurrent pingplotter runs on both of your connections...

63

Another question, was it windy at the time you experienced this packet loss? Wet? What was weather like in general?

64

Hey Guys...
I am going to do a test with other modem / router please standby

65 
################################################################################
traceroute 209.50.128.random
 9  100g-0-1-0-0.cor02.lax01.ca.vocus.net (49.255.255.2)  176.409 ms  180.660 ms  171.864 ms
10  bundle-102.bdr02.lax01.ca.vocus.net (49.255.255.15)  172.034 ms  175.942 ms  172.033 ms
12  eqix-ch2.penteledata.com (208.115.136.159)  211.909 ms  211.961 ms  204.348 ms


################################################################################
traceroute 216.144.160.random
eqix-ch2.penteledata.com (208.115.136.159)  207.017 ms  210.713 ms  206.589 ms
gateway-2-3-haw2haw2-3.haw.ptd.net (207.44.125.210)  248.640 ms  243.584 ms  247.450 ms
gateway-T0-0-0-hawblocal1.cmts.haw.ptd.net (207.44.112.158)  241.963 ms  246.792 ms  246.831 ms



################################################################################
traceroute 50.29.128.random
gateway (10.2.3.3)  0.190 ms  0.197 ms  0.207 ms
10.8.8.1 (10.8.8.1)  10.366 ms  10.436 ms  10.480 ms
43.245.163.161 (43.245.163.161)  18.019 ms  18.075 ms  18.121 ms
43.245.161.237 (43.245.161.237)  18.187 ms 43.245.161.241 (43.245.161.241)  18.509 ms  18.716 ms
43.245.161.253 (43.245.161.253)  17.711 ms  17.780 ms 103.77.232.253 (103.77.232.253)  17.863 ms
ten-2-1-0-679.bdr03.syd04.nsw.VOCUS.net.au (49.255.225.33)  18.423 ms  17.342 ms  17.493 ms
BE-110.cor02.syd04.nsw.VOCUS.net.au (175.45.72.30)  168.240 ms  162.714 ms  162.735 ms
bundle-201.cor02.sjc01.ca.vocus.net (49.255.255.12)  172.314 ms  170.993 ms  171.000 ms
100g-0-1-0-0.cor02.lax01.ca.vocus.net (49.255.255.2)  170.952 ms  171.533 ms  172.146 ms
bundle-102.bdr02.lax01.ca.vocus.net (49.255.255.15)  172.194 ms  176.631 ms  176.664 ms
eqix-ch2.penteledata.com (208.115.136.159)  211.120 ms  211.418 ms  211.447 ms
gateway-be6-mtp2str.mtp.ptd.net (207.44.112.18)  254.306 ms  249.063 ms  249.074 ms
gateway2-p2-mtpblocal1.cmts.mtp.ptd.net (204.186.5.35)  243.475 ms  243.351 ms  239.04


###################################################################################
traceroute 24.152.192.random
 1  gateway (10.2.3.3)  0.229 ms  0.272 ms  0.288 ms
 2  10.8.8.1 (10.8.8.1)  12.301 ms  13.010 ms  13.174 ms
 3  43.245.163.161 (43.245.163.161)  13.358 ms  13.516 ms  13.548 ms
 4  43.245.161.241 (43.245.161.241)  17.186 ms  17.587 ms  18.411 ms
 5  43.245.161.253 (43.245.161.253)  13.218 ms 103.77.232.253 (103.77.232.253)  13.385 ms  13.421 ms
 6  ten-2-1-0-679.bdr03.syd04.nsw.VOCUS.net.au (49.255.225.33)  13.585 ms  12.305 ms  12.360 ms
 7  BE-110.cor02.syd04.nsw.VOCUS.net.au (175.45.72.30)  162.276 ms  160.704 ms  171.579 ms
 8  bundle-201.cor02.sjc01.ca.vocus.net (49.255.255.12)  176.478 ms  180.381 ms  180.647 ms
 9  100g-0-1-0-0.cor02.lax01.ca.vocus.net (49.255.255.2)  180.672 ms  176.508 ms  180.675 ms
10  bundle-102.bdr02.lax01.ca.vocus.net (49.255.255.15)  180.736 ms  180.669 ms  176.579 ms
11  eqix-ch2.penteledata.com (208.115.136.159)  211.013 ms  206.726 ms  206.749 ms
12  gateway2-p2-eph22eph-1.eph.ptd.net (216.144.163.226)  243.464 ms  241.976 ms  245.491 ms
13  gateway3-po2-eph3blocal1.cmts.eph.ptd.net (207.44.125.78)  245.994 ms  246.686 ms  249.513 ms^C
##############################################################################
1 Like
66

Gm Guys,
I'm sorry I didn't respond sooner but I was quit busy trying to figure out the problem with the connection that day.

I guess it was a gut feeling for me to use pingplotter to see If I can see anything on the line. Let me tell you if someone like me (NOVICE) that needs a tool this one would be it. It's expensive to own but I would say it is worth every penny and headaches.

I decided that day, gut feeling again to call the ISP regarding the test results I got using pingplotter and I was able to talk to someone knowledgeable on the phone to really help me out and to diagnose the situation I was having. He informed me that he was doing multiple tests on his end with just the modem plugged in and nothing else. The findings were packet loss and high latency that was interment with just the modem plugged in.

He also wrote an email to my cable provider that there is an issue and that they needed to fix asap. He point out blank said I should have never went through this if they had people to properly diagnose the complaints stuff like this can be resolved quicker. But then again having the proof in the pudding with pingplotter saved the day because it was an intermittent problem. I emailed him all the data that I had.

So it looks like it can be line noise or something to that extent somewhere from my cable company. So at this point I really can't do anymore but to wait. :sleeping: :face_with_raised_eyebrow:

It's amazing that someone like me has very little knowledge about this stuff went ahead and purchased at least 5 new routers thinking that it had something to do with me on my end. All new routers proved to be with the same problems nothing with the routers themselves. Lesson learned!! for sure.

I'm am so very grateful and blessed to you guys and the community welcoming with open arms knowing I don't know :poop:. But you know what you guys didn't care not one bit and tried to rectify that situation at hand. I also can say for sure I learned a lot in the pass few months on networking and what not. :+1::+1::+1::+1::+1::+1::+1::+1::+1:

Even though my journey has not ended yet I do believe I have a place on here to call my home. This is from the bottom of my heart. :heart_eyes:

OK... Enough with the mushy stuff this place is like crack!!! :crazy_face: I just absolutely love it. I'm learning more and more every time you guys happen to post something here. Great job to all!! :clap:

I do feel sorry for the consumers like me not having enough knowledge about this stuff. It's definitly a killer I would say.

To everyone pingplotter saved my day twice. :+1: FYI... I'm not going anywhere. :sweat_smile::rofl::joy:

Thanks again...

1 Like
67

It was slightly windy with some rain.

I tried it with my other modem with the same results... BAD!

Thanks Wulfy!!

68

We have a great community of knowledgeable people here, hurray.

My guess is there is some connection in your neighborhood that is marginal and when wind or rain comes this connection wiggles around or generally causes noise and you get your symptoms. Hopefully a van can roll to your neighborhood and someone will find it and replace it. Good luck!

1 Like
69

Hi Guys,
Hope everyone is well!
? I have the software installed on partition 1 only how would I put back the factory img. to that partition? I know I have partition 2 with factory but I would like to also put it on partition 1 as well.

Thanks guys

70

Make it revert to the OEM partition and flash OEM, that should flash the offline partition back to stock.

I know there is a way to force failure a few times upon boot and it will revert, there's also an OpenWrt app you can install:

https://openwrt.org/packages/pkgdata/luci-app-advanced-reboot

1 Like