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.
On bridge mode, the router was reporting no internet. I reset the power of the modem, even though the lights were normal thinking it would get back on.
Same issues, resetting the power did not work. I then rebooted my router as well. Still no internet, and lights on the modem were normal.
I then figured it was a firmware update gone wrong. I did a hard reset and after 10 minutes or so internet was working on gateway mode.
I then turned gateway mode off and internet was working in bridge mode again.
Good Morning all,
Please remove me from the beta program.
I lost 3hrs of work (working remotely from home) because of 188.8.131.52.4b13 firmware . This firmware required a full reset, which I didn't know about. It would be nice if we were getting heads up emails about new firmware being pushed.
@RogersIan Another update since Tuesday.
Everything is working normally in bridge mode. Access to the GUI is still working well.
After the initial issues with the modem locking up after the firmware download and a hard reset by the Rogers tech, I did another hard reset and it booted with the latest 184.108.40.206.4b13 firmware.
I set the modem to bridge mode and everything was nominal.
I then set the modem back to gateway mode and tested out the wireless. Excellent signal strength and all devices were accessing the modem properly except my google nest which required a reset which I did not want do for this brief test. My Alexa fire stick was working with no issues. GUI working normally as well.
I had not previously paid any attention to the dashboard on the modem, but it appears that there is a higher level of controls for the modem in this mode.
Switched back to bridge mode with no issues.
Fingers crossed everything stays stable.
Okay I got the new firmware last night 220.127.116.11.4b13 firmware lost 2.4Ghz so I did a Factory Reset then I put in all my data back in because I had Wi-Fi extenders and it will not work with them now and Band Steering was Enabled by default so I disabled but still couldn't connect to my extenders so I don't know what to say?
Hi there I’ve also been upgraded to the beta firmware but I’ve asked several times now to be removed from beta testing and put on the most stable production firmware as I no longer wish to participate. Not sure why nobody is listening to me but if a rogers employee can please permanently remove me from the firmware trials I’d really appreciate it!!
If you are interested in participating, please send a private message to @CommunityHelps with the subject line “Rogers Rocket Wi-Fi Modem Firmware Trial”. A member of our team will be in contact with you and provide you with further instructions.
Do the above to get removed!
@Triple_Helix Sorry to hear about your experience from the upgrade.
When you say the 2.4GHz band was lost did you happen to notice whether the band was enabled in the GUI?
Were the SSIDs set to the same names as prior to the upgrade?
Were either the 2.4GHz or 5GHz bands broadcasting?
Could clients see either bands broadcasting?
Glad to see you have your extenders working.
@RogersIan my devices wouldn't connect to 2.4 everything looked good in the UI and I tried rebooting and like I said Band Steering was Enabled so I disabled but that wouldn't work so I did a Factory reset and forgot I had 2.4 on 20MHz only, but everything is working well since. 5G and Ethernet worked fine!
This new code prevents the wifi from finding the TV. Where as the previous code for the 4582 worked perfectly this 18.104.22.168code is worthless to me. Please reengage the previous code ( 7.1 ) and take me off the beta trial. I worked hard to get the wifi signal recognized as a problem and that was corrected. Now the modem wifi is back to not connecting the TV on the network.
Appreciate the feedback so far from everyone, please keep it coming.
How is the performance wired/wireless vs the previous code?
Are you experiencing any issues in the GUI?
Has anyone tried out DDNS (fyi this setting has moved to the advanced tab), port forwarding, DMZ, custom LAN IP ranges etc..
This menu displays general information of the device
|Port ID||Frequency (Hz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)||Bytes||Correcteds||Uncorrectables|
|Receiver||FFT type||Subcarr 0 Frequency(MHz)||PLC locked||NCP locked||MDC1 locked||PLC Location||Occupied BW(MHz)||Subcarriers||PLC power(dBmv)|
|0||4K||275600000||YES||YES||YES||1544||283 ~ 472.95||3736||0.799999|
|1||NA||NA||NO||NO||NO||NA||0 ~ 0||NA||NA|
|Port ID||Frequency (Hz)||Modulation||Signal strength (dBmV)||Channel ID||Bandwidth|
|Channel Index||State||lin Digital Att||Digital Att||BW (sc's*fft)||Report Power||Report Power1_6||FFT Size|
© 2021 Hitron Technologies Inc. All rights reserved.
I wonder if CGN3ACR still having FW updates or trials? The problem I'm experiencing is the modem in Gateway mode never delegates via WiFi an IPv6 prefix to a downstream router. Its still possible to obtain IPv6 addresses for PC clients hooked to the downstream router by switching all IPv6 options to Relay mode (in factory or OpenWRT router FW). But such addresses are exposed directly to the web, and shown on visited webpages regardless of chosen modem firewall mode.
So my concerns are:
1. Some customers reported on this forum getting /56 length IPv6 prefixed from Rogers with modem in Bridge mode. Can current modem firmware get such length prefix in Gateway mode, then delegate a smaller prefix, like /60 to the downstream WiFi Client router that would assign via DHCPv6 /64 length addresses to its PC and device wired and wireless clients? As you know many houses aren't wired in every room, and downstream router is often connected to the modem via WiFi which is only possible in Gateway mode. Many people prefer their LAN segment isolated behind own router (that's why the modem Bridge mode is so popular), which is not possible in IPv6 without the modem delegating a longer prefix in Gateway mode to the router.
2. Currently only the modem IPv4 address is exposed to websites browsed by the Gateway clients. Why then the modem firewall exposes IPv6 addresses of connected clients directly to the web instead of exposing only the modem IPv6 address to the web? Any FW updates planned on this?
Thank you for providing your feedback. We do appreciate you being on the trial and assisting with this process!
We do apologize that you are experiencing these issues. @RogersIan are you able to look into this?
CODA-4582 hw version 1A fw 22.214.171.124 in gateway mode. Over the last 7 days I am having issues with dhcp not serving up ipv4 addresses. It is working for ipv6 but nothing showing for ipv4. This is happening on Windows (various versions), an older iPad and a couple of voip phone attachments. Anyone else ever experienced this?
Just noticed I am on 126.96.36.199.4b15 as well. This is the first time I think I've been upgraded to a firmware trial release, yet I do recall enrolling quite a while ago. Is this the first firmware trial in a while? Can you please provide list of changes and what we should be looking for? I'm going to monitor the issues that I receive with it.