03-25-2017 04:10 PM
@4kgigabitguy How many devices were connected to the modem when this test was run?
03-25-2017 04:34 PM - edited 03-25-2017 04:36 PM
@RyzenFX wrote:
@4kgigabitguy How many devices were connected to the modem when this test was run?
I have lots of devices at home as each family member has 3-4 devices . Logged into the modem admin & it shows 18 devices connected.
4kgigabitguy
03-26-2017 01:32 AM
Im on the .26T2 firmware and been having issues lately. Random reboots, 5 GHz wireless network dissapearance. Modem needs rebooting every as it slows down to less than 1mb per sec.
03-27-2017 07:38 PM - edited 03-27-2017 07:39 PM
Could you or someone please have a look at my signal levels as well as signal level at the CMTS and let me know if this looks ok. Thanks
Downstream Overview
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 615000000 | 256QAM | -3.700 | 11 | 35.780 |
2 | 561000000 | 256QAM | -4.900 | 2 | 35.084 |
3 | 567000000 | 256QAM | -5.400 | 3 | 34.926 |
4 | 573000000 | 256QAM | -4.100 | 4 | 34.926 |
5 | 579000000 | 256QAM | -3.000 | 5 | 35.084 |
6 | 585000000 | 256QAM | -2.300 | 6 | 35.780 |
7 | 591000000 | 256QAM | -0.900 | 7 | 36.610 |
8 | 597000000 | 256QAM | -0.400 | 8 | 37.356 |
9 | 603000000 | 256QAM | -0.800 | 9 | 36.610 |
10 | 609000000 | 256QAM | -2.200 | 10 | 36.387 |
11 | 555000000 | 256QAM | -4.200 | 1 | 35.595 |
12 | 621000000 | 256QAM | -5.000 | 12 | 35.084 |
13 | 633000000 | 256QAM | -4.700 | 13 | 35.595 |
14 | 639000000 | 256QAM | -4.000 | 14 | 35.780 |
15 | 645000000 | 256QAM | -3.400 | 15 | 35.595 |
16 | 651000000 | 256QAM | -4.300 | 16 | 35.595 |
17 | 657000000 | 256QAM | -4.700 | 17 | 35.780 |
18 | 663000000 | 256QAM | -4.100 | 18 | 35.780 |
19 | 669000000 | 256QAM | -4.000 | 19 | 35.780 |
20 | 675000000 | 256QAM | -4.000 | 20 | 35.780 |
21 | 681000000 | 256QAM | -3.700 | 21 | 36.387 |
22 | 687000000 | 256QAM | -3.600 | 22 | 36.387 |
23 | 693000000 | 256QAM | -4.500 | 23 | 36.387 |
24 | 699000000 | 256QAM | -4.700 | 24 | 35.780 |
25 | 705000000 | 256QAM | -5.900 | 25 | 35.595 |
26 | 711000000 | 256QAM | -7.500 | 26 | 34.926 |
27 | 717000000 | 256QAM | -8.300 | 27 | 33.957 |
28 | 723000000 | 256QAM | -9.300 | 28 | 33.377 |
29 | 825000000 | 256QAM | -6.700 | 29 | 34.926 |
30 | 831000000 | 256QAM | -7.100 | 30 | 35.084 |
31 | 837000000 | 256QAM | -7.700 | 31 | 34.926 |
32 | 843000000 | 256QAM | -7.700 | 32 | 34.926 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | NA | NA | NO | NO | NO | NA |
1 | 4K | 275600000 | YES | YES | YES | 1.200001 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 23700000 | ATDMA - 64QAM | 30.000 | 2 | 6400000 |
2 | 38595687 | ATDMA - 64QAM | 35.250 | 3 | 3200000 |
3 | 30596000 | ATDMA - 64QAM | 31.500 | 1 | 6400000 |
Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
0 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
1 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
03-27-2017 07:55 PM
Tahnks...Got the .27 Firmware updates...its working so far Ok.
03-27-2017 09:44 PM - edited 03-27-2017 09:52 PM
Hello Community,
Since joining the firmware trial I have been having horrible experience with my WiFi. Before joining it was pretty bad but this is now worst.
60-80% of the time wireless does not work at all, my phone buffers indefinitely and content does not load - forcing me to go on LTE. However the times it does work, the WiFi is fantastic. In my bedroom (35' away from modem) my signal strength is always maximum and when I do run speedtests I typically get ~20 Mbps down and ~5 Mbps up on my Samsung Galaxy S5 (Rogers Ignite 100), however my phone will refuse to load any content. LAN is perfect.
I have restarted my modem several times. Does anyone have suggestions? This has been very frustrating.
On the + side, my Chromecast now works 🙂
MODEM: CGNM-3552-ROG
03-28-2017 10:01 AM
Yes, me ! 4.5.8.27 ! Just got it updated working fine !
03-28-2017 08:04 PM
@dgelman wrote:
Hello Community,
Since joining the firmware trial I have been having horrible experience with my WiFi. Before joining it was pretty bad but this is now worst.
60-80% of the time wireless does not work at all, my phone buffers indefinitely and content does not load - forcing me to go on LTE. However the times it does work, the WiFi is fantastic. In my bedroom (35' away from modem) my signal strength is always maximum and when I do run speedtests I typically get ~20 Mbps down and ~5 Mbps up on my Samsung Galaxy S5 (Rogers Ignite 100), however my phone will refuse to load any content. LAN is perfect.
I have restarted my modem several times. Does anyone have suggestions? This has been very frustrating.
On the + side, my Chromecast now works 🙂
MODEM: CGNM-3552-ROG
factory reset the modem. Use a Pen Tip to press and hold the reset button on the back of the modem for 10 seconds. Next use WPA 2 and AES Encrption for WiFi security, and use channels 149 for 5Ghz, and 1, 6, or 11 for 2.4Ghz. Turn off WPS and Turn off UPNP.
03-29-2017 12:42 PM - edited 03-29-2017 01:10 PM
Ok, just to add a little info to the gaming UDP discussion, here are some results over the last two months with different firmware and DOCSIS configurations. Keep in mind I'm just the messenger here, not the gamer 🙂
First off, Coda-4582 V2.0.10.23 DOCSIS 3.0
Saturday Evening 4 Feb 2017
Tuesday morning 7 Feb 2017 (late Monday evening)
So, definite packet loss there. On to the next firmware update:
Coda-4582 V2.0.10.24 DOCSIS 3.0
Saturday Evening 18 Feb 2017
Tuesday Morning 21 Feb 2017
As with the first V2.0.10.23 images, the packet losses on Saturday evenings are worse when compared to a typical weekday evening / very early morning. On to DOCSIS 3.1:
Coda-4582 V2.0.10.24 DOCSIS 3.1
Saturday afternoon 11 Mar 2017
This shows the packet loss improvement after switching from DOCSIS 3.0 to 3.1, with the same firmware loaded, V2.0.10.24. Saturdays and Sundays on my CMTS are typically worse for modem to CMTS ping times, but, with DOCSIS 3.1 running, that has improved considerably.
Tuesday Morning 14 Mar 2017 (late Monday evening)
Ok, this is looking pretty ugly, but, its very unusual to see something like this in the logs. Definitely an outlier when compared to the other logs.
Friday Morning 17 Mar 2017 (late Thursday evening)
Back to normal. Note that for our CMTS, any weekday evening period, from 9 pm to 12 pm is typically a high ping time, modem to CMTS. Once again that has improved considerably with DOCSIS 3.1 running. So, this is pretty good considering the traffic at the CMTS. Next firmware version:
Coda-4582 V2.0.10.26T1 DOCSIS 3.1
Saturday afternoon 18 Mar 2017
Tuesday morning 21 Mar 2017
14 packets lost is high compared to normal losses.
Tues evening 21 Mar 2017
9 packets lost, most of which appear at the game's end. For the most part, back to normal
While the game is underway, a secondary UDP stream is also in use for voice chart using Discord as the chat application. Checking the voice UDP data stream with Wireshark, the inbound data stream appears to run without any problems, as seen by the incrementing ID number in UDP packet. Just to point out, as noted in other posts, that ID number can be set to anything, so it may not be useful for anything depending on the source of the data stream. The LOL inbound UDP packets that I've looked at are not sequential, so, its definitely more difficult to determine if all of the inbound UDP packets have arrived. There might be some accounting done internally by the game and reported back to Riot, but that's just speculation on my part.
So, fwiw, hope this provides some interesting info of LOL UDP losses taking into account the firmware and DOCSIS implementation.
03-29-2017 12:48 PM - edited 03-29-2017 12:49 PM
The Images are not available yet, but just from reading text , I am getting nearly the same results ,with a different game (CSGO) that also uses UDP.
and just like you said at the end of the post, most gamers also use discord. (And that program also uses UDP).
Defintely not an issue with RIOT or VALVE.. or any other company.. It's an UDP issue on Rogers's end but , they're getting more and more feedback, hopefully they will have enough to start working on a fix soon!