One of the mods will probably contact you if more info is required. If not, later today, 4.5.8.21 will load.
My 4.5.8.21 for CGN3ACSMR signals are very good in my area in Oshawa. I can't see why some would have any -
| 1 | 693000000 | 256QAM | -0.400 | 30 | 38.983 |
Downstream Overview
| Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
| 1 | 597000000 | 256QAM | 8.300 | 2 | 38.605 |
| 2 | 591000000 | 256QAM | 8.600 | 1 | 38.605 |
| 3 | 603000000 | 256QAM | 8.500 | 3 | 38.605 |
| 4 | 609000000 | 256QAM | 8.900 | 4 | 38.983 |
| 5 | 615000000 | 256QAM | 9.700 | 5 | 38.605 |
| 6 | 621000000 | 256QAM | 9.400 | 6 | 38.983 |
| 7 | 633000000 | 256QAM | 7.600 | 7 | 38.983 |
| 8 | 639000000 | 256QAM | 7.100 | 8 | 38.605 |
| 9 | 645000000 | 256QAM | 6.600 | 9 | 38.983 |
| 10 | 651000000 | 256QAM | 6.200 | 10 | 38.605 |
| 11 | 657000000 | 256QAM | 6.100 | 11 | 38.983 |
| 12 | 663000000 | 256QAM | 6.700 | 12 | 38.605 |
| 13 | 669000000 | 256QAM | 7.900 | 13 | 38.983 |
| 14 | 675000000 | 256QAM | 8.400 | 14 | 38.605 |
| 15 | 681000000 | 256QAM | 8.900 | 15 | 38.983 |
| 16 | 687000000 | 256QAM | 9.100 | 16 | 40.366 |
| 17 | 693000000 | 256QAM | 9.700 | 17 | 38.983 |
| 18 | 699000000 | 256QAM | 9.100 | 18 | 38.605 |
| 19 | 705000000 | 256QAM | 8.800 | 19 | 38.983 |
| 20 | 711000000 | 256QAM | 8.200 | 20 | 38.983 |
Upstream Overview
| Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | BandWidth |
| 1 | 30596000 | ATDMA - 64QAM | 39.500 | 2 | 6400000 |
| 2 | 23700000 | ATDMA - 64QAM | 40.250 | 3 | 6400000 |
| 3 | 38596000 | ATDMA - 64QAM | 40.750 | 1 | 3200000 |
The problem isn't the data rate or successful single pings. The problem is the latency that is showing up in applications and ingame. If you look at the following ping test to the first node beyond my modem, you can see the second and forth pings, which are high time pings.
Pinging 99.239.32.1 with 32 bytes of data:
Reply from 99.239.32.1: bytes=32 time=28ms TTL=63
Reply from 99.239.32.1: bytes=32 time=199ms TTL=63
Reply from 99.239.32.1: bytes=32 time=12ms TTL=63
Reply from 99.239.32.1: bytes=32 time=118ms TTL=63
Reply from 99.239.32.1: bytes=32 time=12ms TTL=63
Ping statistics for 99.239.32.1:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 199ms, Average = 73ms
So, with just 5 pings, my average ping time is 73 ms. In a few more pings, there will be another high time ping or equal or greater time. My average ping time to the first node historically has been 10 ms. Now, if I let this run long enough my average ping time will be 20 to 30 ms with visible high time pings. Consider this, this is the first stop on the road to everywhere, and I'm seeing high return times from that node alone. Fwiw, I'm not the only one to see this in an application or possibly in a game. This is seen thru a CGNM-3552 with V4.5.8.21 running gigabit service out to a Casa CMTS. Its an interesting combination, higher data rates and higher latency. So something is up, so to speak.
Here are some examples of graphed ping times out to the first node beyond my CGNM-3552:
http://communityforums.rogers.com/t5/media/gallerypage/user-id/829158/image-id/3520iEE410A8BE2503DD0
http://communityforums.rogers.com/t5/media/gallerypage/user-id/829158/image-id/3521i6C10342CB35F4AB4
From a couple of days earlier, showing the time distribution:
http://communityforums.rogers.com/t5/media/gallerypage/user-id/829158/image-id/3469i5CD04FB9F4FE100B
http://communityforums.rogers.com/t5/media/gallerypage/user-id/829158/image-id/3470i601F2DCE974604A8
In order to see this run a trace to anywhere. Then ping the second address in the trace, which is the first node beyond your modem. Run it for something like 100 or 200 pings and just sit back and watch the ping times as they scroll by. You will probably see pings in the 20 to 30 ms range, then some high time ping possibly in the 200 to 300 ms timeframe. If you do this, please let me know what your results are. If by some chance you have an average in the 10 ms range, I'll probably ask you to send me a copy of the whole ping test so that I can have a look at it, ping by ping. The maximum number of pings that the command window will hold, so that you can copy it, is 293, despite the fact that the test itself might be much longer.
Just as an aside, your signal levels are in spec, but, personal opinion the downstream levels are pretty high. They should be down at 0 dBmV. But, if they aren't presenting any issues at this time, better to let sleeping dogs lie. Over the years that will come down as the external cable ages.
My guess is that you're on a Cisco CMTS at the moment, which is probably set to not respond to pings.
When you have time, can you log into your modem, navigate to the STATUS ...... DOCSIS EVENT page and have a look for one of the following sequences:
a. CMTS-MAC=00:17:10 which indicates that you are connected to a Casa Systems Cable Modem Termination System (CMTS), or;
b. any of the following which indicates that you are connected to a Cisco Systems CMTS.
1. CMTS-MAC=00:05:00
2. CMTS-MAC=00:12:43
3. CMTS-MAC=00:14:f1
4. CMTS-MAC=00:1f:ca
5. CMTS-MAC=e0:2f:6d
Please let me know what CMTS you're on, Cisco or Casa?
Ok, can you delete the events log as it has your modem MAC address in it.
You're on a Casa CMTS. Its interesting that pinging the second IP fails. What happens when you ping something usual, like google.ca or google.com?
Thats a little strange. The IPV4 address times out but the IPV6 addresses work. Try this.
tracert -6 ipv6.google.com
Then, using the second IP address, ping that address. It should return a ping. You can force the use of IPV6 by using "-6" in the command.
looks good, can you do the same, running the test for 250 pings and post just the end results. I might ask you to send me the whole test and a couple of other bits of data.
-
932769 views
-
669 Likes
-
-
