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.

[RogersIan]

Good news in a sense, we have replicated the GUI login screen failing to load and sluggish response while in bridge mode on 7.1.1.32. and provided the details to our vendor.

Thank you for bringing it to our attention.

Correction on the event logs intermittently going blank issue, the fix was not applied in .32, but I understand a fix is in hand and should be in the next build.

RogersIan

[lethalsniper]

Just noticed coda modem on 36T8 what’s the improvements if any ?

[RogersIan]

@lethalsniper.36T8 is a small patch which brought a backend certificate update.

RogersIan

[dadealmeister]

Looks like the frame broadcast bug affecting my WiFi Plug devices on the 2.4Ghz network is rearing its ugly head again.

[Ipse]

Coincidence or not? Hitron CGN3ACR updated last night to 4.5.8.40T2 and presto...downstream channel signals dropped around 3dBm. Not outside -7..+7dBm range (but close to -5), however throughput is affected.

What would it take to get a CODA instead? Tired of rebooting this one every 2 days (good thing I have it on a smart switch that is programmed to do just that).

Ignite 300u if that matters.

[noziel]

On the CGN3AC on 4.5.8.43 today trying to login to GUI it's failing.   I will reboot the modem tomorrow am to see if that recovers it.  Never had issues in the past with GUI failing and modem is in bridge mode.   I can ping  the 192.168.100.1, simply get can't connect.  

When I was downgraded t o4.5.8.40T2 and upgraded again, had no issues to login so reporting on a potential issue with this version for GUI failure after a set period of time when the modem is up and running.

Thanks,

[noziel]

Minor update

Able to login to GUI via HTTPS which is great.   Not sure if this firmware removed the ability via HTTP? 

[Ipse]

Anyone from Rogers care to chime in...besides moderating the modem appellation?
Today I noticed that upstream signals increased by 5-6 dBm and my downstream dropped another 1dBm..close to -7 now.
The ONLY change since beginning of the month is this firmware update - I  know, makes no sense if it has nothing to do with signal reading or tuning - but I am getting 110-120Mbps today vs 450+ at the beginning of the month.
If it's not this horrible modem (and we can only rule that out by replacing it with a CODA) than something coincidentally happened to the line. What are odds...been on cable for 10 years at this address.

I started to regret choosing the convenience of staying with Rogers instead of taking the plunge and going with the recently installed Bell fiber.

[CstmrAlwayWrong]

CODA-4582 firmware update NAT Loopback problem

It used to work fine for months. Problem started Around June-8-2020, by Rogers updating firmware of router.

I have web resource running within network for which I have port forward setup e.g.: 443 to 443 to local IP address.

That machine is exposed to the internet via dynamic DNS- URL duckdns.org e.g.: xxxx.duckdns.org

Problem:

I cannot access my resource: https://xxxx.duckdns.org from with-in home network

But same thing works fine when I am accessing form outside of home network

Things I already tried:

1. Router factor re-set

2. Use WIFI band steering on router

Try accessing using LAN port on back of router

[Datalink]

@CstmrAlwayWrong this may be the result of updating the modem to firmware version 7.1.1.30 and now to 7.1.1.32.   If you log into the modem you can check the Software (firmware) version shown on the STATUS page.  That page is displayed automatically when you log into the modem.   The previous version was 2.0.10.36T6. 

[blues_clues]

Looks like 7.1.1.32 is being rolled out to production CODAs.

[CstmrAlwayWrong]

@Datalink 

It says  : Software Version 7.1.1.32.

As soon as they update to this version, problem started.  I think router cannot handle NAT Loop back or Hairpin NAT, not sure what they call in rogers.  below is history:

1. problem started in first week of JUNE-2020

2. But at same time, Internet also stopped working intermittently

3. call Tech support, they replaced the Modem (for intermittently internet problem, not related to NAT )

4. New modem worked for 3 days for NAT Loop back or Hairpin NAT

5. ON 11th or 12th June new Modem also got updated with new Firmware, and Same problem of NAT Loop back  started again. 

General Internet is working. 

[Datalink]

@CstmrAlwayWrong version 7.1.1.32 is built on a new kernel, so there is a very good chance that the NAT loopback or Hairpinning was not included in this version.  That's a problem that Intel may have to resolve.  @RogersIan will have to look at this and ask Hitron to determine what the problem is. 

[noziel]

@RogersIanNot sure if it's coincident but since the 4.5.8.43 the modem has reset.   Originally it was related to server downgrading to production firmware and than corrected to re-install the trail.  

However, I than had issues a week or so with http login that was not responsive and two days later I noticed the modem must have restarted as uptime was 2 days and today evening at around 9 pm the internet went down and had the green light flashing up arrow and stayed that way for a long time.  Once I disconnected the power and connected, modem came back online.    This maybe related to work in area to address congestion or something but appreciate you look into it.  If the modem gives another issue of reboot or login to GUI  will request you put me back to 4.5.8.40.    Please keep me posted.

Thanks,

[DavidYe]

Did 7.1.1.32 go live for production? Had my CODA previously on 2.0.10.36T8 randomly factory reset last night only to notice it received 7.1.1.32.

Was previously with the trial program 7.1.1.30 but I did a modem swap back in March since I was having constant connection lockups that required a reboot- not sure if this was just a MAC update for any swaps that happened in the meantime or whether it's being pushed to production now. Eitherway, hoping that this is a better firmware. Not sure if having modems factory reset without notice is that elegant of an upgrade path though, at least for the average customer.

[ffdhfhf]

7.1.1.32 Just got rolled out to Production, hope the new (Linux) kernel being used might expose more features, like Wireguard for VPN use if Hitron went more bleeding edge kernel 🙂 now that would be great to expose on the modem UI!

Though I'm on the beta program, I assume Rogers suspended beta builds during our current pandemic for obvious reasons.

@Datalink are there plans to expose read-only SNMP support or thats been scrapped? It would be nice if that was still planned.

I did notice my Upstream channels (maybe unrelated) have recovered signal from being in the low 30s now to 39/40 DBmV along with listing unused channels:

Downstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	597000000	QAM256	8.300	8	38.983
2	849000000	QAM256	10.500	2	38.983
3	855000000	QAM256	10.699	3	38.983
4	861000000	QAM256	11.099	4	38.983
5	579000000	QAM256	7.900	5	38.983
6	585000000	QAM256	8.199	6	38.983
7	591000000	QAM256	8.099	7	40.366
8	279000000	QAM256	4.900	1	38.983
9	603000000	QAM256	8.599	9	40.366
10	609000000	QAM256	9.500	10	40.366
11	615000000	QAM256	9.699	11	40.366
12	621000000	QAM256	9.800	12	40.366
13	633000000	QAM256	10.000	13	40.366
14	639000000	QAM256	10.000	14	38.983
15	645000000	QAM256	10.000	15	40.366
16	651000000	QAM256	10.099	16	40.366
17	657000000	QAM256	10.099	17	40.366
18	663000000	QAM256	10.300	18	40.366
19	669000000	QAM256	10.500	19	40.946
20	675000000	QAM256	10.300	20	38.983
21	681000000	QAM256	10.699	21	40.366
22	687000000	QAM256	10.699	22	40.946
23	693000000	QAM256	10.599	23	40.366
24	699000000	QAM256	10.000	24	40.366
25	705000000	QAM256	9.900	25	40.366
26	711000000	QAM256	9.500	26	38.983
27	717000000	QAM256	10.099	27	40.366
28	723000000	QAM256	10.199	28	40.946
29	825000000	QAM256	9.300	29	38.605
30	831000000	QAM256	8.800	30	38.605
31	837000000	QAM256	8.900	31	38.605
32	843000000	QAM256	9.199	32	38.605

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	5.599998

Upstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Bandwidth
1	30596000	64QAM	40.020	3	6400000
2	36996000	64QAM	40.020	4	6400000
3	22100000	64QAM	39.010	1	3200000
4	25300000	64QAM	40.260	2	3200000
5	0	QAM_NONE	-	---	1600000
6	0	QAM_NONE	-	---	1600000
7	0	QAM_NONE	-	---	1600000
8	0	QAM_NONE	-	---	1600000

[adri21]

I'm having the exact same problem as @CstmrAlwayWrong where NAT loopback is no longer working on  7.1.1.32. Does anyone know when the next release is planned and if there will be a fix for the NAT loopback issue? 

@RogersIan 

[dpgupta]

Hi, 

I have a CODA-4852 at latest production firmware 

2.0.10.36T8

I'd like to sign up for trial program, so I can try the new firmware. Please let me know what I have to do to upgrade to latest trial version of the firmware.

Thanks

[RogersAndy]

Hey @dpgupta!

Welcome to the community! Thanks so much for reaching out to us @CommunityHelps, we'll be happy to assist you there.

@RogersAndy

[lethalsniper]

How the modem holding up compare to the coda ? And what’s the model # u got

[lethalsniper]

How it holding up still feel this modem is better then the coda ?