FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
I'm a Reliable Contributor
Posts: 579

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

@4kgigabitguy How many devices were connected to the modem when this test was run?

Rogers Employee 4kgigabitguy
Rogers Employee
Posts: 45

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial


@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

 

I Plan to Stick Around
Posts: 98

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

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.

I'm a Reliable Contributor
Posts: 338

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

@RogersDave

 

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 IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1615000000256QAM-3.7001135.780
2561000000256QAM-4.900235.084
3567000000256QAM-5.400334.926
4573000000256QAM-4.100434.926
5579000000256QAM-3.000535.084
6585000000256QAM-2.300635.780
7591000000256QAM-0.900736.610
8597000000256QAM-0.400837.356
9603000000256QAM-0.800936.610
10609000000256QAM-2.2001036.387
11555000000256QAM-4.200135.595
12621000000256QAM-5.0001235.084
13633000000256QAM-4.7001335.595
14639000000256QAM-4.0001435.780
15645000000256QAM-3.4001535.595
16651000000256QAM-4.3001635.595
17657000000256QAM-4.7001735.780
18663000000256QAM-4.1001835.780
19669000000256QAM-4.0001935.780
20675000000256QAM-4.0002035.780
21681000000256QAM-3.7002136.387
22687000000256QAM-3.6002236.387
23693000000256QAM-4.5002336.387
24699000000256QAM-4.7002435.780
25705000000256QAM-5.9002535.595
26711000000256QAM-7.5002634.926
27717000000256QAM-8.3002733.957
28723000000256QAM-9.3002833.377
29825000000256QAM-6.7002934.926
30831000000256QAM-7.1003035.084
31837000000256QAM-7.7003134.926
32843000000256QAM-7.7003234.926
OFDM Downstream Overview
ReceiverFFT typeSubcarr 0 Frequency(MHz)PLC lockedNCP lockedMDC1 lockedPLC power(dBmv)
0NANANONONONA
14K275600000YESYESYES1.200001
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandwidth
123700000ATDMA - 64QAM30.00026400000
238595687ATDMA - 64QAM35.25033200000
330596000ATDMA - 64QAM31.50016400000
OFDM/OFDMA Overview
Channel IndexStatelin Digital AttDigital AttBW (sc's*fft)Report PowerReport Power1_6FFT Size
0DISABLED0.50000.00000.0000-inf-1.00004K
1DISABLED0.50000.00000.0000-inf-1.00004K
I Plan to Stick Around
Posts: 18

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

Tahnks...Got the .27 Firmware updates...its working so far  Ok.

I Plan to Stick Around
Posts: 9

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

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

I Plan to Stick Around
Posts: 18

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

Yes, me !  4.5.8.27   !  Just got it updated working fine ! 

Highlighted
Resident Expert
Resident Expert
Posts: 1,076

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial


@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


@dgelman

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. 



Resident Expert
Resident Expert
Posts: 6,111

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

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

 

1_Sat 4 Feb Coda-4582 V2.0.10.23  DOCSIS 3.0.png

 

 

Tuesday morning  7 Feb 2017  (late Monday evening)

 

2_Tues 7 Feb Coda-4582 V2.0.10.23  DOCSIS 3.0.png

 

 

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

 

3_Sat 18 Feb Coda-4582 V2.0.10.24  DOCSIS 3.0.png

 

 

Tuesday Morning   21 Feb 2017  

 

4_Tues 21 Feb Coda-4582 V2.0.10.24  DOCSIS 3.0.png

 

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

 

5_Sat 11 Mar Coda-4582 V2.0.10.24  DOCSIS 3.1.png

 

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)

 

6_Tues 14 Mar Coda-4582 V2.0.10.24  DOCSIS 3.1.png 

 

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)

 

7_Fri 17 Mar Coda-4582 V2.0.10.24  DOCSIS 3.1.png

 

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

 

8_Sat 18 Mar Coda-4582 V2.0.10.26T1  DOCSIS 3.1.png

 

 

Tuesday morning   21 Mar 2017

 

9_Tues 21 Mar Coda-4582 V2.0.10.26T1  DOCSIS 3.1.png

 

14 packets lost is high compared to normal losses.

 

 

Tues evening   21 Mar 2017

 

10_Tues 21 Mar Coda-4582 V2.0.10.26T1  DOCSIS 3.1.png

 

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. 



I'm a Reliable Contributor
Posts: 609

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

@Datalink

 

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!