 NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:9
 ·SONIC.NET
·Pacific Bell - SBC
| reply to dtherbert
Re: [Connectivity] Latency IssueWhy are you pinging an intermediary router, which is likely going to be unresponsive to ICMP?
How about pinging Google for 50 iterations; and just post the summary, because that has all the information that you need to show:
Ping statistics for 74.125.224.146:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 26ms, Average = 25ms
I don't think your signals show a problem, but I will defer to any DOCSIS experts, if they disagree.
Your trace doesn't look bad, but it is a single point in time. A PingPlot might show something.
PingPlot to Google over time.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
| I will do these things you suggest.
To answer your question about pinging an intermediary router, I thought I would try pinging the addresses listed in the trace, starting with my router, then the modem (not listed, at 192.168.100.1), then beyond, to see if I got spikes anywhere. It happened that the first address listed after my router showed these ping spikes, so I didn't try any further ones since I thought that was where the problem was. Isn't the fact that I'm getting a response mean that it is responding to ICMP, or is my reasoning flawed (timeouts/spikes due to low-priority or something like that)?
Anyway, thank you for the response, I'll post the new information after I get home later. |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:9 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| Many routers are programmed to give low priority to diagnostic packets directed at them. Their primary job is forwarding TCP/IP traffic up the path. Response to diagnostics, unlike routing through, requires processor time; which may cause throughput delays if the router is 100% responsive to ICMP, and the like.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
| Is there a recommendation for a Mac-compatible alternative to PingPlotter? |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:9 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| said by dtherbert:Is there a recommendation for a Mac-compatible alternative to PingPlotter?
Maybe Smokeping, though I don't know how to interpret the results.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
| reply to dtherbert
said by dtherbert:Is there a recommendation for a Mac-compatible alternative to PingPlotter?
mtr - »www.bitwizard.nl/mtr/ |
|
|
|
| Thanks devnuller, I'll check that out.
Also, I've been running smokeping for awhile now, see link:
»/r3/smokeping.···99f40735
Anybody care to interpret the results?
I'm definitely seeing some packet loss, on the order of a few percentage points. Also, the period on the graphs corresponding to 8:30PM-midnight, I was streaming Netflix for a good portion of that time, and it seems to have dropped a few more packets, and the pings were definitely less consistent (I probably should have prioritized ICMP packets on my router). |
|
