 jmckformerly 'shaded'
join:2010-10-02
Ottawa, ON
 ·TekSavvy DSL
·Start Communicat..
| Packet loss tonightTonight I started noticing a bit of packet loss. To be sure it wasn't my router, cycled the modem and connected it directly to my machine.
Here are 2 mtrs, one from each direction and both show the packet loss happening on the first hop:
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 10.106.248.129 2.2% 46 8.2 8.7 6.1 18.9 2.8
2. 24.156.149.217 2.2% 46 17.8 18.1 13.5 39.1 5.2
3. so-5-0-0.gw02.bloor.phub.net.cable.rogers.com 0.0% 46 19.7 22.7 15.1 37.0 3.9
4. v514.core1.tor1.he.net 0.0% 46 15.1 19.7 14.2 36.4 4.9
5. 10gigabitethernet3-1.core1.nyc5.he.net 0.0% 46 30.1 33.0 28.1 42.0 4.1
6. 10gigabitethernet3-2.core1.nyc1.he.net 0.0% 46 40.5 33.9 30.0 43.5 3.7
7. 216.66.30.218 2.2% 46 34.1 31.9 30.1 34.2 1.0
8. rakis.net 4.3% 46 34.0 33.9 30.6 46.3 2.7
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. nyc.rt2.cyberwarp.net 0.0% 71 0.5 0.5 0.4 0.6 0.1
2. v103.core1.nyc1.he.net 0.0% 71 0.5 3.2 0.4 11.8 3.6
3. 10gigabitethernet3-3.core1.nyc5.he.net 0.0% 71 11.4 3.1 0.4 12.2 3.6
4. 10gigabitethernet3-4.core1.tor1.he.net 0.0% 71 22.6 17.1 14.4 25.6 3.6
5. start-communications.10gigabitethernet3-1.core1.tor1.he.net 0.0% 70 14.5 17.7 14.5 200.5 22.2
6. 64.140.112.146 0.0% 70 22.1 28.6 17.1 657.6 76.3
7. 10.106.248.129 0.0% 70 24.6 26.7 24.4 31.9 2.1
8. dhcp-24-53-250-38.cable.user.start.ca 1.4% 70 31.9 34.6 30.2 55.8 4.7
I have a Thomson 476 modem but I'm not sure how to connect to it to get the line stats (nothing in the 'manual' provided with the modem), nothing coming up in google first page results too. |
|
jmckformerly 'shaded'
join:2010-10-02
Ottawa, ON | Found the default IP (192.168.100.1) for the DCM476, here are the stats:
 |
|
| Same in Kitchener.
Ping statistics for 74.125.226.34:
Packets: Sent = 42, Received = 38, Lost = 4 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 24ms, Average = 14ms
Cant play games at all.
World of tanks, that i am currently playing, ping is between 200-300ms. |
|
jmckformerly 'shaded'
join:2010-10-02
Ottawa, ON Reviews:
·TekSavvy DSL
·Start Communicat..
| well mine wasn't that bad, it only started at around 8pm i think, and lasted until a few minutes around at 11:30pm and it stayed about 2% the entire time.
since it was happening on my first hop, i know it's likely not a Start issue and i'm worried it's a capacity issue on my segment at peak :/ |
|
 dillyhammerA. Good. Start.Premium,MVM
join:2010-01-09
Hamilton, ON
kudos:9
·Start Communicat..
 ·Cogeco Cable
·TekSavvy DSL
·Caneris
| reply to jmck
Just went through the same ordeal a couple days ago. Corrected itself after a while. Down for a good 5 hours. Cogeco (via ticket) denied anything was wrong, said maybe it was a virus.
Mike |
|
|
|
Guru
join:2008-10-01
kudos:2 | LOL... I mean you serious? |
|
 roccaStart.caPremium
join:2008-11-16
London, ON
kudos:11 | reply to jmck
said by jmck:since it was happening on my first hop, i know it's likely not a Start issue and i'm worried it's a capacity issue on my segment at peak :/ Yes the loss at the 10.x address does support that, hopefully it's a Sunday evening anomaly, if not they are pretty good at upgrades. |
|
roccaStart.caPremium
join:2008-11-16
London, ON
kudos:11 | reply to dillyhammer
said by dillyhammer:Cogeco (via ticket) denied anything was wrong, said maybe it was a virus. Yeah, I saw that in the ticket too - surprised our staff mentioned that part, unless it was more tongue in cheek. We have seen in the past though where machines that were infected with botnet's suffer loss when participating in an attack. |
|
jmckformerly 'shaded'
join:2010-10-02
Ottawa, ON Reviews:
·TekSavvy DSL
·Start Communicat..
1 edit | reply to rocca
said by rocca:said by jmck:since it was happening on my first hop, i know it's likely not a Start issue and i'm worried it's a capacity issue on my segment at peak :/ Yes the loss at the 10.x address does support that, hopefully it's a Sunday evening anomaly, if not they are pretty good at upgrades. Even in R land? I believe dilly is on Cogeco. The packet loss seems to have started 15 mins ago again, both directions again:
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 0.0% 103 0.8 0.7 0.6 1.3 0.1
2. 10.106.248.129 2.9% 103 7.1 8.5 6.8 19.2 1.8
3. 24.156.149.217 0.0% 103 20.1 19.6 14.5 43.1 5.6
4. 69.63.249.9 2.9% 102 21.7 21.5 14.8 34.7 4.5
5. v514.core1.tor1.he.net 2.0% 102 19.3 20.3 16.1 29.3 3.8
6. 10gigabitethernet3-1.core1.nyc5.he.net 1.0% 102 30.7 33.3 29.4 41.9 3.9
7. 10gigabitethernet3-2.core1.nyc1.he.net 2.0% 102 36.6 32.6 28.3 58.9 4.7
8. 216.66.30.218 2.0% 102 31.6 31.1 29.1 46.0 2.5
9. rakis.net 1.0% 102 35.5 31.2 28.7 47.0 2.3
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. nyc.rt2.cyberwarp.net 0.0% 101 0.4 0.5 0.4 1.3 0.1
2. v103.core1.nyc1.he.net 0.0% 101 2.0 3.2 0.4 11.4 3.6
3. 10gigabitethernet3-3.core1.nyc5.he.net 0.0% 100 1.2 2.9 0.4 12.9 3.4
4. 10gigabitethernet3-4.core1.tor1.he.net 0.0% 100 17.9 16.8 14.4 25.3 3.3
5. start-communications.10gigabitethernet3-1. 0.0% 100 14.6 24.8 14.5 306.7 42.1
6. 64.140.112.146 0.0% 100 17.6 19.8 17.0 183.4 16.6
7. 10.106.248.129 0.0% 100 24.5 23.6 23.2 40.1 1.7
8. dhcp-24-53-250-37.cable.user.start.ca 1.0% 100 31.2 30.9 28.9 43.2 2.0
It was fine from 11:30pm last night until about 15-20 mins ago (9:30am). |
|
 pnear
join:2002-06-12
Milton, ON | reply to jmck
I've been having issues intermittently as well, and am getting ready for the next incident with a suite of testing tools to run. Not sure if it's packet loss or something else.
What are you using to generate that packet loss report? |
|
jmckformerly 'shaded'
join:2010-10-02
Ottawa, ON Reviews:
·TekSavvy DSL
·Start Communicat..
| I'm using 'mtr' originally it meant "Matts traceroute" but now it means "My traceroute". I use it on Linux and OSX, but there's a windows version of it (WinMTR I think).
It essentially combines traceroute and ping and paints a better picture where the problem is. |
|
pnear
join:2002-06-12
Milton, ON | Thanks, my results look pretty bad through that lens. Will try switching out a few points of failure. Packet loss at every point in the route right now. |
|
roccaStart.caPremium
join:2008-11-16
London, ON
kudos:11 | said by pnear: Packet loss at every point in the route right now. You have to remember that packets to hop 2 also go through hop 1, so if you have problems at hop 1 you're going to see problems further down the line too. (ie hop 2 isn't just hop 2, it's a combination of 1+2, likewise hop 3 is 1+2+3) |
|
Guru
join:2008-10-01
kudos:2 | But if the problem was at hop 1 then, wouldn't it show at hop 1 as well? |
|
roccaStart.caPremium
join:2008-11-16
London, ON
kudos:11 | Yes. I'm replying to the comment about seeing "Packet loss at every point in the route", it's not that every hop has a problem, it's the first one and you see it at all the subsequent hops because the packet still goes through that first hop (or whatever hop the problem first starts at). |
|
Guru
join:2008-10-01
kudos:2 | ah ok. |
|
pnear
join:2002-06-12
Milton, ON Reviews:
·Start Communicat..
| reply to rocca
Tested at various points in my network, this one taken directly connected to the modem after a power cycle is probably the most relevant. |---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.193.4.1 - 9 | 45 | 41 | 6 | 7 | 12 | 7 |
| asr-link1-burlington1.net.start.ca - 11 | 46 | 41 | 8 | 9 | 16 | 9 |
| 64.140.112.157 - 20 | 51 | 41 | 8 | 14 | 107 | 8 |
| gw-google.torontointernetxchange.net - 0 | 42 | 42 | 8 | 13 | 83 | 9 |
| 216.239.47.114 - 15 | 48 | 41 | 8 | 11 | 53 | 10 |
| 72.14.233.142 - 13 | 47 | 41 | 8 | 10 | 24 | 10 |
| yyz06s05-in-f23.1e100.net - 9 | 45 | 41 | 8 | 9 | 14 | 10 |
|________________________________________________|______|______|______|______|______|______|
A description of the symptoms: every once in awhile (sometimes once a week, lately once a day), some sites fail to load. I originally was thinking DNS issues, since some things would come in and others would fail. Sometimes a modem reset fixes it, sometimes it doesn't. I'm conscious of hijacking your thread, sorry. I can start another if it makes more sense. -Pete |
|
pnear
join:2002-06-12
Milton, ON | I should add - I tested with OpenDNS instead of Start's DNS the last time this got really bad and got the same symptoms, so I'm fairly sure it's not a DNS issue. |
|
roccaStart.caPremium
join:2008-11-16
London, ON
kudos:11 | Yeah, DNS doesn't have anything to do with packet loss.
Your MTR shows loss on the first hop, ie the 10.x IP which is the CMTS so you're seeing loss between your modem and the CMTS (ie Cogeco issue). Suggest calling in a ticket. |
|
pnear
join:2002-06-12
Milton, ON Reviews:
·Start Communicat..
| said by rocca:Yeah, DNS doesn't have anything to do with packet loss. Understood, that was just one of the troubleshooting steps I took over the last couple weeks. Just discovered the packet loss issue today.
Will call in a ticket. |
|
