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.

[catalano11]

@Datalink

ok so I removed the power bar. these are my quick results. still loss.

Ping statistics for 64.71.255.204:
Packets: Sent = 99, Received = 85, Lost = 14 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 294ms, Average = 21ms

Ping statistics for 174.117.144.1:
    Packets: Sent = 112, Received = 112, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 297ms, Average = 21ms

my modem is in = dual ipv4 and ipv6

DNS Obtain = auto 

DNS Proxy Status  = enabled 

[Datalink]

Ok, can you run the following command:      ipconfig/all 

Please send that to me via private message as it shouldn't be posted.  I'd like to see if your pc is running IPV6 addresses and what shows up for the DNS addresses.  

Can you ping the following IPV6 addresses.  Your DNS Obtain is set to Auto and you're running Dual Stack.  In theory, the pc and other equipment should be using IPV6 addressing.  Now, its certainly possible to be running applications that need an IPV4 address.  That should be accessible thru the IPV6 Domain Name Server.  There is a problem with packet loss to and from the IPV4 DNS, now I'm wondering what the IPV6 side looks like:

Rogers IPV6 DNS

Primary IPv6 DNS:

2607:f798:18:10:0:640:7125:5204

Secondary IPv6 DNS:

2607:f798:18:10:0:640:7125:5198

[catalano11]

@Datalink

primary: 

Ping statistics for 2607:f798:18:10:0:640:7125:5204:
    Packets: Sent = 46, Received = 41, Lost = 5 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 426ms, Average = 52ms

secondary: 

Ping statistics for 2607:f798:18:10:0:640:7125:5198:
    Packets: Sent = 54, Received = 53, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 287ms, Average = 32ms

[Datalink]

Ugh, that's a terrible result.  Ok, lets see what happens when you switch DNS addresses and run a ping test to those selected addresses.  

I wonder if you would see the same issue thru pingplotter, that is, that the second last hop is where the packet loss arises. Might be worth doing before switching DNS addresses. 

[catalano11]

@Datalink

[KevinTheTurtle]

What is the current version for this modem? When i check it says the software version is 2.0.10.33T3. is this the most recent version? If not how can i update it? 

[KevinTheTurtle]

My modem is the  Hitron CODA-4852U

[Datalink]

@KevinTheTurtle the latest firmware version for the CODA-4582 is V 2.0.10.36T4.  Restart / reboot the modem to load the latest version.  The modem should run a firmware check when it reboots and load the latest version.  Fwiw, log into the modem after the reboot and update is done to confirm the firmware version.  That is seen in the STATUS page that is displayed when you log into the modem.  Its shown as the Software Version.  At the same time, have a look at the upper right hand corner for the WAN IP Address.  You should see two addresses, one IPV4 and one much longer IPV6.  The IPV6 address would be present if the modem was running in Dual Stack mode (IPV4 + IPV6).  If so, then your connected devices would also be running Dual Stack (IPV4 + IPV6).

There is a reboot scheduled into the update.  However, I've always found that a factory reset, or at the very least an additional reboot will usually ensure that the modem performs as it should following a firmware update.  To reboot the modem at this point navigate to ADMIN .... DEVICE RESET ..... Reboot (function) to initiate a reboot. 

The firmware versions for the various modems can be seen in the second post in this thread.  Here's the direct link:

https://communityforums.rogers.com/t5/Internet/FEEDBACK-Rogers-Rocket-Wi-Fi-Modem-Firmware-Trial/m-p...

[JohnBeaudin]

Feedback on Coda 36T5.

I still experience the same issue ( need to reboot modem every day). I get random spikes in online games and while working using VOIP it;s cutting out every couple secs for 1-2 secs until I reboot the modem.

I had this issue on previous firmware version, and I also tried to switch the modem, a Tech came here tested the line , everything is fine he don't see anything wrong but swapped the modem anyway just in case.

The issue is going on still, I have to reboot the modem every day.  I had hopes 36T5 would fix this issue but unfortunately not. Anyone else experience this?

[WestPoint]

@RogersIan I want to start with a thank you, it looks good from what i can tell thus far, the DHCP table is working great for once, and now I feel confident in updating my stuff and configuring my network to be more stable and accessable...

Then I'd like to just ask, wt* happend here, lol;

12	10/05/2018 07:37:14	69010100	notice	SW Download INIT - Via NMS
13	10/05/2018 07:39:22	69010400	error	SW Upgrade Failed Before Download - Server not Present
14	10/05/2018 07:39:22	69010600	error	SW upgrade Failed before download - TFTP Max Retry Exceeded
15	10/05/2018 08:08:07	69010100	notice	SW Download INIT - Via NMS
16	10/05/2018 08:08:37	69011100	notice	SW download Successful - Via NMS

And then lastly, I'd just like to mention, your website, Rogers.com, and the Community Forums....

Wow what a pain somtimes... Not only do I constantly get notified about my browser not being supported, which first off, I've been using for well over 10 years, so get with it and start supporting it, its called Maxthon, and its always been an amzing browser and I cant seen why I cant use it for your site, and your site alone, only site I have issues with.   That said, not only does your site not load correctly, half the time in mobile view even tho I'm clearly on a wired desktop on a gigabit plan, and half the time unless i refresh the page 2 or three times, but once I finally get logged in, and I try to go the to Community Forums here to reply, it says I'm not logged in now... and when I click signin, it flips to Rogers.com where I am logged in, and automatically flips back to the forum thinking im logged in, but im not, and cant do anything... and just keeps going in circles forever... so far the only way I can over come this, is to log out at Rogers.com, go to the forums, click, login from there and try again, most of the time this works, but occationally still, i have to close the browser tab, and reload and try again, just refresh will not work...

Anyways, good work on the DHCP table, I can finally start trying to setup my network correctly and stable and know where my devices are going to be to find them.

[vulture]

Hi all,

Having below sync issues frequently since upgrade to 2.0.10.36T5. It feel more unstable so far after upgrade, anyone else came across the issues ?

No.	Time	Type	Priority	Event
1	10/09/2018 22:58:38	82000200	critical	No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
2	10/09/2018 22:59:06	84020200	warning	Lost MDD Timeout;CM-MAC=;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
3	10/09/2018 22:59:29	82000200	critical	No Ranging Response received - T3 time-out;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
4	10/09/2018 22:59:35	82000300	critical	Ranging Request Retries exhausted;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
5	10/09/2018 22:59:35	82000800	critical	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
6	10/09/2018 22:59:41	82000200	critical	No Ranging Response received - T3 time-out;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
7	10/09/2018 23:00:11	82000300	critical	Ranging Request Retries exhausted;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
8	10/09/2018 23:00:11	82000800	critical	16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
9	10/09/2018 23:00:11	85010100	error	TCS Fail on all Upstream Channels;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
10	10/10/2018 04:02:15	90000000	warning	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
11	10/10/2018 04:02:20	84000700	warning	RCS Partial Service;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
12	10/10/2018 00:21:49	84020200	warning	Lost MDD Timeout;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
13	10/10/2018 00:22:16	84000500	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
14	10/10/2018 10:54:19	84020200	warning	Lost MDD Timeout;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
15	10/10/2018 12:14:08	84000500	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
16	10/10/2018 12:14:13	84020200	warning	Lost MDD Timeout;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
17	10/10/2018 12:14:14	84000500	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
18	10/10/2018 12:15:01	84020200	warning	Lost MDD Timeout;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
19	10/10/2018 17:20:41	90000000	warning	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;
20	10/10/2018 17:20:45	84000700	warning	RCS Partial Service;CM-MAC= ;CMTS-MAC=00:17:10:98:59:97;CM-QOS=1.1;CM-VER=3.1;

[RogersIan]

@WestPoint

Glad to hear that the DHCP reservation feature is working as it should do. Please let us know if the issue arises again.

Looking at your event logs, it seems there was a glitch when connecting to the server.  This can happen once and while which is why we do multiple passes when pushing out firmware to the community.

[WestPoint]

@RogersIan
So I have a question now, I see the CODA modem is MoCA capable, and if so, what additional hardware do I need to be able to use it ?

I'd also like to know why Rogers isnt allowing an upgrade to the new Ignite Gigabit Modem, with whole home internet without changing my grandfathered cable package.

Its just a way to FORCE people out of there service that your not allowed too cancel because its protected by the Consumer Protection Act and its unfair business and sales practices to say, that because i choose too keep my cable package that, which btw, is MUCH better than anything im be offered for the same monthly price under your new, pay-for-every-channel individually policy. I have over 300 channels for $100 now, why would I start at $80 for 150 channels and pay $3/channel for national news, local new in some cases, cartoon network, ect... channels that have been FREE to me for over 10 years in my current package, which has ALWAYS been paid on time. Anyways, its unfair to say because I prefer not to be forced to pay more for less service, that m not allowed to have the current technology, which will limit my ability in the future to reach speeds that would be available with the new device, which I believe, under ideal condtions and testing, is able or will be able too reach speeds up too 10Gbps in the future when the infrastructure is upgraded to match. But the point is, the new device it forward compatable and the CODA will be outdated very soon, and you dont and havnt even yet prefected tohe firmware for this device, which im forced to use unless im willing to cave to Rogers demands I give up a grandfathered service.

I dont know how you guys think media stations are going to react when people start to see what your doing, but it wont be kinda if I get forced into changing my cable package for any reason. You can change my hardware to meet your network needs all you want, but you will not force me to pay the same or more, for less service, I will keep my package no matter what hardware or network changes you make, there is no ligit reason you can give me to make me believe I HAVE TOO change what channels I get based on the network type/hardware, when they are all still available, just at additional cost now, including new additional device rental fees forever... 

Any comment??

[Datalink]

@vulture restart/reboot the modem.  Pull the power off of the modem, wait for 10 to 15 seconds and then plug it back in to force a restart.  Although there is a reboot built into the update, I've always found that a second restart/reboot is necessary to ensure that the modem behaves as it should.  

For an update to the production version firmware, as in production version to production version, I'll usually run a factory reset.  You can't do that with the Trial Firmware as it will load the current production version firmware, which at the present time is 36T4.

[Datalink]

@WestPoint, I can't speak for @RogersIan on the matter, but I do hear what your saying.  

Basically you need MoCA2.0 qualified  adapters at the locations that you want to run intra/internet connected devices.  You will need a MoCA Filter installed on the cable that comes in from the street, and a MoCA 2.0 qualified splitter or amplifier in place of the Rogers splitter.  The requirement for a MoCA 2.0 qualified amp will depend on the number of MoCA 2.0 adapters that you're planning on running.  That's the short answer.  As I indicated, there is a good deal of info in the other thread. 

Edit:  

Have a read thru this thread, starting with this post by @traghipp:

https://communityforums.rogers.com/t5/Internet/Wifi-extender-for-hitron-coda-4582/m-p/425310#M53154

@traghipp might have some advice to offer as he's had his MoCA 2.0 network up and running since the end of July 2018. 

[RogersIan]

Last night we pushed 4.5.8.39T5 to our AC community members.

This build includes:

• Wi-Fi driver update (5GHz SSID is intermittently not broadcast after reboot) - Carried over from 39T2
• Fix: Modem randomly rebooting

RogersIan

[noziel]

Thanks, what is the plan to upgrade the actual production firmware from .27 to 39T5?  I get the trial but I have family members that are not part of the trail program and are running on the .27 which is very outdated with tons of Wifi issues.

[Alex4161]

@Rogerslan

Please push the latest firmware to my modem. I have PM'd you my modem info as I am supposed to be on the beta program.

Thanks

[Alex4161]

Hi

I have the 

Software Version

2.0.10.36T5

and I find that I keep losing the OFDM Downstream connections and my connection goes wonky.  My signal levels are as follows:

Downstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	603000000	256QAM	4.700	9	38.983
2	849000000	256QAM	1.900	2	37.636
3	855000000	256QAM	1.800	3	37.636
4	861000000	256QAM	1.600	4	37.356
5	579000000	256QAM	3.800	5	38.605
6	585000000	256QAM	4.800	6	38.983
7	591000000	256QAM	5.200	7	38.605
8	597000000	256QAM	5.200	8	38.605
9	303000000	256QAM	3.000	1	37.636
10	609000000	256QAM	3.700	10	38.605
11	615000000	256QAM	3.000	11	37.636
12	621000000	256QAM	2.100	12	37.356
13	633000000	256QAM	1.500	13	37.636
14	639000000	256QAM	1.500	14	37.356
15	645000000	256QAM	1.500	15	37.356
16	651000000	256QAM	2.200	16	37.636
17	657000000	256QAM	3.200	17	37.636
18	663000000	256QAM	4.300	18	38.605
19	669000000	256QAM	5.200	19	38.605
20	675000000	256QAM	5.600	20	38.605
21	681000000	256QAM	5.300	21	38.605
22	687000000	256QAM	4.700	22	38.983
23	693000000	256QAM	3.400	23	38.605
24	699000000	256QAM	2.500	24	37.636
25	705000000	256QAM	1.700	25	37.636
26	711000000	256QAM	1.000	26	37.636
27	717000000	256QAM	0.900	27	37.356
28	723000000	256QAM	1.200	28	37.636
29	825000000	256QAM	1.500	29	37.356
30	831000000	256QAM	2.100	30	37.636
31	837000000	256QAM	2.300	31	37.636
32	843000000	256QAM	2.000	32	37.356

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	3.200001

Upstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Bandwidth
1	38596000	ATDMA - 64QAM	33.500	3	3200000
2	30596000	ATDMA - 64QAM	29.750	1	6400000
3	23700000	ATDMA - 64QAM	29.500	2	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

[hoopdogg]

I went back to 36T4 last night.  Was a problem found in 36T5?  looking at page1 nothing is noted.

[JohnBeaudin]

I went back to 36T4 also , not really happy because 36T4 is the worst firmware I ever been on, so many issues while on it, gaming is impossible without at least 3-4 reboot a day. hopefully I don't stay too long on this firmware.