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.
@italstalguy I'm running 184.108.40.206.4b15 in Bridge mode, and so far, accessing the modem hasn't been an issue. I logged into the modem after I saw your post, just to make sure. Fwiw, here's the LAN and WAN uptimes:
LAN Up Time 079 days 16h:47m:36s
WAN Up Time 079 days 16h:49m:03s
@italstalguy, on previous versions always had trouble logging into the GUI. Generally no issues with internet access.
This trial is no longer very active so, probably not much point in joining it. Add to that the fact that they will eventually push everyone to the new Ignite XB6 and XB7 modems.
Folks, on 220.127.116.11.4b15, the keyword filter just stopped working last week.
I had this keyword filter working last year before 18.104.22.168.4b15 upgrade. I was also able to set the days of the week for it. I had to figure out the timezone of the modem should be set to Eastern Standard time as the default is UTC. So it was working after 22.214.171.124.4b15, I didn't even know about this thread and just came across last week due to these issues.
Last week, it just stopped working and then followed by router login password had reverted back to "password". Initially I thought the modem got hacked as I was not able to log in but I figured it out tried the default password. Only the default password had reverted back and not the settings.
I already reset this router to factory default just to make sure if keyword filter would work, but no luck. Even with the manage in some days of the week setting disabled.
Then yesterday, had issues connecting to wifi. And I noticed the SSID for 2.4GHz was not coming up. So today after checking, the SSID that you put on 2.4 GHz would also be inputted by the GUI on 5GHz. So I just disabled 2.4GHz for now.
I find it amazing that a large telecom company like Rogers, pushes a beta firmware, and then does zero follow up in this forum for months. This is after they solicit feedback. What is going on? There have to be thousands of Rogers customers, including business, who still use the CODA. Is there ever going to be a final release?
Is this still Beta/tester firmware. If so I have it and did NOT ask for it. Also now Im not able to log into Coda anymore. I have it bridged. I have tried 2 factory resets on Coda.
Ping times are 54ms and speed tests are slow on 1Gb package.
If this is Beta firmware. PLEASE remove it from me. Thanks
Cannot log in to my Coda 4582 modem in bridge mode at 192.168.100.1 any longer from my Asus RT-AC86U router. The modem is on beta firmware 126.96.36.199.4b15. This worked since the beta was released, up until today.
I've tried everything including resetting the modem to factory defaults and putting it into bridge mode again.
Why would it stop working all of a sudden? @HitronDave, any idea?
I wanted to take a few minutes tonight to provide some updates. As I mentioned in a previous message, I do not have the time to respond to everybody individually. Still, I read the messages and report some items for review and improvement to the Hitron Engineering team.
First and foremost, there are a few mentions of firmware 188.8.131.52.4b15 as a beta firmware. However, I can assure you that this is a production firmware and widely deployed in North America.
Historically, Rogers used a custom version of the firmware. This firmware is a unified code used by all cable companies in North America. This is why there are some minor changes in the GUI compared to the previous production version. Moving forward, all firmwares will be unified as it is a lot easier to keep a consistent experience and ensure that any item reported anywhere in North America gets addressed for everybody.
I see one major trend in this forum, and it is related to accessing the modem GUI while in bridge mode. It seems that some of you are reporting no problem, while some of you have no issue. There is a difference in the way the bridge mode GUI was handled in the Rogers custom firmware vs the Hitron generic firmware, and I suspect that this is the cause of the issue you are seeing. I will have my QA team investigate next week and see if we can make this easier moving forward in a future version.
Nice to hear from you Dave.
I had reported not having any issues logging into the GUI and now I cannot log in to my Coda 4582 modem in bridge mode at 192.168.100.1
I'm also using an Asus RT-AC86U router.
The modem is on 184.108.40.206.4b15. This worked up until just this week.
If so, this is a completely different problem than what I expected. There was a change this week, not in the firmware but rather in some parameters used by Rogers to manage modems and I suspect that this is related. I'll have Hitron QA team validate my theory next week and hopefully provide a temporary workaround.
I have the same setup too,
I'm also using an Asus RT-AC86U router. I could always log into Coda on the previous version. I started to notice slow speeds/throughput and proceeded to log into Coda. That was unsuccessful so I tried two factory resets on Coda (thats when I noticed the new version). Still no luck
@ybrik the keyword filtering issue is caused by the omnipresence of IPv6 enabled websites, HTTPs and secured DNS. This makes it very difficult to correctly filter traffic based on simple keyword criteria without a full-fledged online cloud-based security solution. It has gradually allowed more and more traffic to evade the filtering over the years.
Given the false sense of security that this feature provides, we have made the decision to completely remove it starting with firmware 220.127.116.11.2b1.