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.
Don't have code we can deploy here yet, sorry guys. It's not from a lack of trying I promise.
We are expecting a .27 version to hit us the beginning of next week.
We continue to flush out issues found during the upgrade flow from 2.0 to 7.1 code. Seems we fix one and another pops up.
For those of you currently on 184.108.40.206 how is the code performing?
Appreciate the feedback,
I received 220.127.116.11. A couple weird things started happening:
1) Guest account showed up even though it's disabled
2) both 2.4G and 5G wireless showed up as Open instead of Secured. And was able to connect without any password. Rebooted to fix
3) Hitron router page times out quickly while logged in
4) Some devices refuse to connect (not sure of the pattern here)
I just received this firmware, the one some of you received up to a month ago. I really need a downgrade to 2.0. Who do I need to contact to get that done? Thanks.
We were all under the impression that 18.104.22.168 was halted from being rolled out any further. Those who asked to be rolled back were accommodated. Some of us who have it are waiting for 22.214.171.124. Noone should be getting 126.96.36.199 at this time.
@mf152- Very strange,we haven't pushed code out since the initial push of .21 and I don't see anything in your logs. Do you want to message me some more info on your wireless connectivity issue including which clients are having issues?
I decided to enable band steering and DFS and will see how it goes. Got the weird issue again today where guest account showed up again. Rebooted. Since 27 is coming along soon will wait.
As per what you mentioned, I may have had 188.8.131.52 for a while and didn't even realize it. But I only started experiencing some strange issues the few days or so.
Hello Team - don't know when I was upgraded to the new CODA-4582 however this morning I woke up with "barely" my router working. Ethernet was fully borked, Wifi was half borked, MoCA was also borked.
192.168.0.1 simply said "UnknownError" in the HTML
Did a factory reset and I'm still on 7.x.x.x (too lazy to go back a page) and I was able to use the internet again. Disabled 2.4Ghz, setup 5Ghz, enabled MoCA, went to "Show Connected Devices" and basically it seems 192.168.0.1 is dead again.
Internet is working as I'm able to post this so I'm not going to fiddle with anything for now.
edit: UnknownError on 192.168.0.1 again.
edit2: By setting my DNS explicitly (on PC side) to Google DNS I seem to be able to use the internet again at least. Still getting unknown error on CODA.
I have been upgraded to 184.108.40.206
1) Had to reboot modem to be able to access 192.168.0.1 again (was hanging and then unknown username error)
2) Speeds have dropped to 35mbps according to fast.com (was 150mbps on 220.127.116.11 and 250+ on version 2, this is while paying for 500mpbs speeds)
Edit: I disabled DFS, and poof, speeds back up to normal levels. Will monitor for the next while.
Update to my previous post - I woke up again basically with dead internet, DNS only didn't work, however setting a static IP may have helped.
Might be DHCP messing up + UnknownError = sad times?
Personal opinion, on any firmware update, especially if you have any issues following the update, reboot/restart the modem at the very least. I'd suggest a factory reset, but, at this point I'm not sure what that will load, the same 18.104.22.168, or will it attempt to return to 36T6? I suspect that returning to 36T6 requires deliberate action from Rogers staff.
I've always found that a modem reboot at the very least, moving from there to a factory reset, has been required to see the modem function as expected after a firmware update, despite the reboot that is scheduled into the update.
In this particular case, this is a big jump, moving to a new kernel.
I'm still on 36T6 at the moment.