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.
Good news in a sense, we have replicated the GUI login screen failing to load and sluggish response while in bridge mode on 188.8.131.52. 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.
Coincidence or not? Hitron CGN3ACR updated last night to 184.108.40.206T2 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.
On the CGN3AC on 220.127.116.11 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 o18.104.22.168T2 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.
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.
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
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:
Router factor re-set
Use WIFI band steering on router
Try accessing using LAN port on back of router
@CstmrAlwayWrong this may be the result of updating the modem to firmware version 22.214.171.124 and now to 126.96.36.199. 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 188.8.131.52T6.
It says : Software Version 184.108.40.206.
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.
@RogersIanNot sure if it's coincident but since the 220.127.116.11 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 18.104.22.168. Please keep me posted.
22.214.171.124 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:
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|Receiver||FFT type||Subcarr 0 Frequency(MHz)||PLC locked||NCP locked||MDC1 locked||PLC power(dBmv)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Bandwidth|
I have a CODA-4852 at latest production firmware
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.