On Fri, 27 Jan 2017, Daniel Bareiro wrote: > >>> What do you think? Will it be a problem with the cablemodem? > >> I don't know which hop is your cable modem, but you need to explain the > >> first hop losing packets. If it drops return packets that often, you > > > The cablemodem is 192.168.1.1, so the CMTS is 10.96.0.1. I've been
10.96.0.1 could be the CMTS, or it could be an aggregation router, depends on the CMTS being transparent or not to the IP L3. > > watching mtr for a few minutes waiting for the ssh connections to freeze > > and I've only seen that the hops from the cablemodem turn red when > > everything freezes. I'm going to do the test again by connecting > > directly via ethernet to ensure the results are reproducible. > > I did the test again by connecting the notebook with a cable to the > TP-Link router (192.168.2.1). When the connections are dropped, all the Do it _directly_ connected to the cable modem, please. And by that I also mean without any VMs, containers, virtual network devices, or NAT in the middle. > https://ibin.co/3ANVFzZi7BHg.png It does look like the cable-modem, but this is not yet certain. And it could also be ethernet cabling or a switch (if you have one), etc. Basically anything between the test node (your laptop/computer) and the cable modem, *including* infrastructure. If you can do it at no cost, ask the ISP to replace that cable modem just in case. These things *do* age, I had to replace three of them over the last 8 years. One of them did not outright die, it would lose packets or connect at low bandwidth at the DOCSIS layer. -- Henrique Holschuh
