FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

[RogersMargaret]

Hello Community,

We are currently offering our users an exclusive opportunity to participate in an upcoming trial of the new firmware for our Rocket Wi-Fi Modem (CGN3ACR, CGN3AMR and CGN3ACSMR) and Rocket Gigabit Wi-Fi Modem (CGN3552 and CODA-4582). For details of this program, please see this thread.

This thread will be used for feedback regarding the firmware.  We've invited @RogersSergio, @RogersSyd & @RogersBob from our Networking team to participate in this thread.  Your feedback is very valuable and will be used to enhance the firmware before it is released publicly.

Thank you for your continued feedback and support.

[bla2342342342]

---

@Jeffj wrote:

The beta firmware should resolve the majority of your issues. 

As for how long it takes, its liek The Ring. 7 Days or so.

Well, I can report back that between Saturday and now, I've been migrated to the test firmware and it DOES fix my network share problem.  Thanks to everybody who's been trying to get these issues resolved.

Speed test (or initial runs) seem fine with similar speeds as before so I consider myself lucky.  Just glad to be able to not only see the machines connected in my network (via the 4582 gui) but also be able to move data between them.

---

[User1445713]

I'm on 2.0.10.23 as of today around 3pm.

Wireless SMB works.

Wireless client list works.

My other issue is host name list from DHCP.

It wasn't working very well for me on firmware .19 and it is still the same. The list in CODA interface is somehow random showing some names, some as "Unknown" and some as "0" even though there were registered in DHCP reservation table and still visible with names there.

The problem is that I can't use drive mapping like \\WDMYCLOUD\Share. I need to use IP addressing like \\192.168.X.X\Share. I was able to log into Raspberry Pi from PuTTy using "RaspberryPi" host name before I got into CODA. Now I need to use IP address of Raspberry Pi even if the name is visible in "Connected Devices" list form  CODA page.

Can someone confirm this issue with host names or should I do a factory restore after the firmware update and test the host names on default settings?

The same issue applies to wireless and wired network.

[Datalink]

@User1445713 after a firmware update, you should as a minimum do a modem restart.  Pull the power plug from the electrical socket, wait for 30 seconds and plug it back in to force a restart.  If you find that the restart doesn't do the job, run a factory reset.  

[Exrobbers]

I upgraded to the CODA 4852 as I received the email to do so on Friday. I've updated my info for the firmware trial to receive .23. Still on .13. My speeds are inconsistent just as they were withe the 3552 but I'm finding the 2.4 Wifi range superior while the 5G range is worse

[RyzenFX]

@CommunityHelps

Despite having .23 pushed to my modem yesterday afternoon, you forgot to exclude me from having the production firmware being sent to my modem. As a result, I was downgraded to .19 last night and will need to haveat. 23 pushed again.

[blues_clues]

---

@Exrobbers wrote:

I upgraded to the CODA 4852 as I received the email to do so on Friday. I've updated my info for the firmware trial to receive .23. Still on .13. My speeds are inconsistent just as they were withe the 3552 but I'm finding the 2.4 Wifi range superior while the 5G range is worse

---

I have found both 2.4Ghz and 5.Ghz band wireless much better on .23 than on .19.  Please do a co-channel interference scan to find uncongested channels.  You can set your 5Ghz channel to 149+ as the transmit power is higher for channels above 149.

[Mythen]

Anyone have any idea what exactly the 4582 with the black dot does differently than one without the black dot

[markopas]

---

@Mythen wrote:
Anyone have any idea what exactly the 4582 with the black dot does differently than one without the black dot

---

The black dot version previous shielding for the 2.4 antenna which has improved performance but I am sure someone can correct me on that.

My original non-black dot version has been working perfectly.

[Exrobbers]

---

@RyzenFX wrote:
@CommunityHelps

Despite having .23 pushed to my modem yesterday afternoon, you forgot to exclude me from having the production firmware being sent to my modem. As a result, I was downgraded to .19 last night and will need to haveat. 23 pushed again.

---

@Send a pm to @CommunityHelps. My modem was upgraded last night from .13 to .19. Haven't received .23

[RogersDave]

Hello Community,

I am sorry that I haven’t been able to answer all your questions in the last 3 weeks but I have been really busy trying my best to make everybody’s Internet better 🙂

I know that some of you are getting lower speeds than they expected and unfortunately, I can’t help much at this point. There is a lot going on right now on the network and performing a single complete review of a speed complaint can take me between 30 minutes to an hour. I simply can’t handle this at the moment (my time is better used addressing global issues than localized ones right now).

I am still trying to quickly go through the last 2 weeks of messages on the forum but that is a lot so I may not catch everything. I will post CODA-4582 and DOCSIS 3.1 specific updates in the CODA thread here. On the CGN3 series (AMR, AMF, ACSRM, ACR, 3552), we are still working on an updated release that will improve latency stability and fix the uplink speed issue that was introduced in 4.5.8.27 (especially on the CGNM-3552). That release should be 4.5.8.29 and I soon as I have it, I will push it out to participants of the firmware trial program. We are also working on other fixes that may make it into that release.

As always, you can keep an eye on the release notes in the 2nd message of this thread. I try to update it as information becomes available to me.

Dave

[JohnBeaudin]

Thanks for the update @RogersDave

So happy to see you back in the forums 😉

[markopas]

Had a weird incident happen tonight - thought another firmware was being pushed out but after the internet came back online I noticed that the firmware was still at .23

Checked my logs, just don't know what to make of it.  You can see the first incident happend at 23:10 and this lasted for a good 10-15mins.  I did a power reset by pulling the power cord for 60sec. and plugging back in, after it came back online I noticed that I got all 32 channels back (2-10 and 32 were missing for quite some time) and might signal levels slightly improved but I am still getting speeds of 700-750 down on Rogers Speed Check.

15	02/14/2017 23:10:28	82000400	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
16	02/14/2017 23:10:55	84020200	warning	Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
17	02/14/2017 23:24:58	82000400	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
18	02/14/2017 23:25:18	82000200	critical	No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
19	02/14/2017 23:49:58	82000400	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

[Datalink]

My guess is that the MDD Timeout resulted in the modem going offline.  Have a look at the following page, paying attention to the MAC Domain Descriptor (MDD):

https://volpefirm.com/docsis-3-0-cable-modem-registration/

From another linked page:

MDD messages are periodically transmitted on all Downstream Channel(s) of DOCSIS 3.0 CMTSs. The MDD message contains the Downstream Channel ID of the Primary Downstream Channel for the CMTS sending the MDD message.  The value of the MDD occurs when a cable modem locks onto a non-primary capable downstream channel, the cable modem will read the MDD and know immediately where to tune to in order to lock on to the Primary Downstream Channel.  The MDD can also be used for load balancing cable modems in a DOCSIS 3.0 network.  The MDD also contains additional information for the cable modem, such as available downstream channels, available upstream channels, upstream frequency range and more.

I suspect that for some reason, the modem is losing track of the Primary Downstream Channel, goes offline and as a result has to go thru the entire modem registration process.  I had that happen to my 4582 at some point as well.   This also makes me wonder if the CMTS is changing the Primary Downstream Channel with the result that the modem goes offline and has to register with the CMTS again. 

[joker2168]

Recived the .23 update yesterday afternoon. At first it seemed to be very good. My wireless was getting very good speeds. I am on 250 and I was seeing 200 on my wireless. Also the ports were working normally as I could once again connect to a NAS. I was unable for some reassn on the pervioud version I could not connect to my NAS on anyone of the ports.

I am missing some of my channels as you can seee below.

Downstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	615000000	256QAM	-1.000	11	38.605
12	621000000	256QAM	-1.100	12	38.605
13	633000000	256QAM	-2.100	13	37.356
14	639000000	256QAM	-2.900	14	36.610
15	645000000	256QAM	-2.700	15	37.636
16	651000000	256QAM	-2.100	16	37.356
17	657000000	256QAM	-1.200	17	37.356
18	663000000	256QAM	-0.500	18	37.636
19	669000000	256QAM	0.100	19	38.605
20	675000000	256QAM	-0.900	20	37.636
21	681000000	256QAM	-2.200	21	37.356
22	687000000	256QAM	-2.800	22	37.636
23	693000000	256QAM	-3.400	23	37.636
24	699000000	256QAM	-3.700	24	37.356
25	705000000	256QAM	-2.800	25	37.636
26	711000000	256QAM	-2.300	26	37.636
27	717000000	256QAM	-2.100	27	38.605
28	723000000	256QAM	-1.800	28	38.605
29	825000000	256QAM	-6.300	29	36.610
30	831000000	256QAM	-6.500	30	36.387
31	837000000	256QAM	-7.000	31	36.387
32	843000000	256QAM	-7.100	32	35.780

OFDM Downstream Overview

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.400002

Upstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Bandwidth
1	23700000	ATDMA - 64QAM	41.250	2	6400000
2	38596000	ATDMA - 64QAM	41.250	3	3200000
3	30596000	ATDMA - 64QAM	39.250	1	6400000

OFDM/OFDMA Overview

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

This morning I am seeing disconenctions very bad ping rates to servers that are normally 1-5MS away are now in the 100's. Disconnections of the wireless. The ETH port access is the same also. Using the rogers speed test site I am downlaoding at maybe 10Mbps then it will jump to 90Mbps.

[User1445713]

I'm on .23 since Monday afternoon and from the log file it looks like the firmware was flashed on my modem couple times more Monday night and yesterday around 4pm. I'm still on .23 at the end.

So far so good. I have my main issue resolved SMB access over Wifi.

Second issue that I experienced LAN connection working only when using IP's and rejecting hostnames was not modem related.

Couple of hours reading Internet about hostnames not resolving on local LAN got me in the right direction. Hostnames were blocked by McAfee firewall automatic setting that started to act when I upgraded to CODA and was trying to get NAS working over Wifi. I got it resolved without factory reset on CODA modem. New Dell laptop with free 1 year subscription to McAfee protection was at fault 😉

One small issue that could use a little fixing is the Connected Devices table on CODA modem.

After fixing my Firewall, multiple firmware flashes and reboots the table shows similar number of devices compared to the network scanned list. However hostnames are not properly transferred from DHCP reservation table. Some names from reservation are correct in Connected Devices table, some listed as "Unknown" and some as "0". I can't find any relation to what controls the listing. I have 2 PC's with Windows 10 side by side with reserved IP's. One is showing proper name and the other is listed as "Unknown". Both of them show up with correct names using network device scanner.

Another point not really impacting performance but annoying is "Green-Blinking Ethernet active" front light. This should be steady green for Ethernet active status and randomly blinking for activity like the rest of the Ethernet connected devices in the whole world. Steady blinking typically is used to draw attention to some sort of alarm or warning.

Multi port forwarding is working well for me. No issues with Gigabit switch.

No issues with speed here as well. All channels ON. I don't have 1 Gigabit account with Rogers 😉

[Datalink]

@joker2168, try running a modem restart.  Pull the power, wait for 30 seconds and plug it back in to see if that resolves the missing channel issue.  You have DOCSIS 3.1 in operation, and you're also noticing inconsistent speeds.  That speed issue is being addressed at the present time by Rogers, Hitron, Intel and Casa.  Hopefully there will be a solution found fairly soon. 

Does your modem have a black dot on the back of it near the power cable?

You could also try an experiment after the restart, and that is to shut down the 2.4 Ghz wifi if it happens to be running and restart the modem once again.  

The last resort measure would be to run a factory reset and check the channel situation after the modem reboots.  

[joker2168]

I did a restart of the modem yesterday it did not seem to help bring the channels back. Will try the factory reset. I do have the modem with a black dot.

Thanks for the reply.

[lethalsniper]

@RogersDave what about a fix for UDP issues hopefully thats in the works also.

[markopas]

@Datalink wrote:

My guess is that the MDD Timeout resulted in the modem going offline.  Have a look at the following page, paying attention to the MAC Domain Descriptor (MDD):

https://volpefirm.com/docsis-3-0-cable-modem-registration/

From another linked page:

MDD messages are periodically transmitted on all Downstream Channel(s) of DOCSIS 3.0 CMTSs. The MDD message contains the Downstream Channel ID of the Primary Downstream Channel for the CMTS sending the MDD message.  The value of the MDD occurs when a cable modem locks onto a non-primary capable downstream channel, the cable modem will read the MDD and know immediately where to tune to in order to lock on to the Primary Downstream Channel.  The MDD can also be used for load balancing cable modems in a DOCSIS 3.0 network.  The MDD also contains additional information for the cable modem, such as available downstream channels, available upstream channels, upstream frequency range and more.

I suspect that for some reason, the modem is losing track of the Primary Downstream Channel, goes offline and as a result has to go thru the entire modem registration process.  I had that happen to my 4582 at some point as well.   This also makes me wonder if the CMTS is changing the Primary Downstream Channel with the result that the modem goes offline and has to register with the CMTS again. 

---

I wonder if I should trade in my original CODA modem for the black dot version, the only reason why I say this is that people who had the black dot version seem to be working much better after they have received the .23 firmware.  I know this shouldnt matter but I have seen stranger things happens that are complelety unrelated to one another to cause issues.

[lethalsniper]

I have the original coda with the black dot and I get those MDD time out , but heard the newer ones are better

[Datalink]

I'm still running the original CODA-4582 as well and have only seen one MDD Timeout from what I remember.  I keep the modem parked several feet from my router and haven't seen any issues with it, but, my CMTS is still on DOCSIS 3.0 at the present time.