05-31-2016 08:42 AM - last edited on 03-14-2018 04:23 PM by RogersRoland
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.
07-20-2016 10:24 AM
Again I really appreciate that you communicate the info with us @RogersDave
As a gamer it's frustating again yesterday I was playing CSGO with some of my friends ( they are all with Bell), while they have 15-20 ping.. I am sitting with 75-90 depending on server locations.. speed is great with rogers but latency for gaming horrible right now, hopefully you guys will manage to get this down so we can enjoy online gaming with Rogers too.
Thanks for the insight I really appreciate as a Rogers customer that you are aware and working on it making it high priority.
07-20-2016 01:44 PM
Hey Dave, One thing in terms of peering to look into would be peering to valve servers (viriginia on the east coast) , also chicago and new york peering which are the main servers we all use
the other reason I am replying is because I just experienced yet another dropout of my internet, full modem reboot, my logs are literally FULL of timeouts (t3 and one t4 timeout), a few of the logs have date stamps of 01/01/70 , this is not the first time this has happened My snr is borderline but my line has a 6db bandaid pad on outside on the line, if possible you can look at my signals and my logs.
07-20-2016 02:19 PM - last edited on 07-22-2016 07:06 PM by RogersCilio
I just got the new 1 gigbite Hitron Modem and I called chromecast to resolve a problem. I have 7 chrome cast that were connected to the network, which they all are not working now ever since the change. They told me to contact you guys to get this fixed. Is there something i can do to fix this?
07-20-2016 02:27 PM
07-20-2016 02:41 PM
I remember back in the CISCO CMTS days our ping was bad not as bad as with the CASA CMTS.
I was under the impression that CASA would improved the bad ping we had on CISCO but.. I was quite surprised when I seen it go even higher than it was previously on CISCO.
But it's the first time I heard that they are actually working on the isssue.. so hopefully we see a fix soon!
07-22-2016 04:20 PM
We enrolled in the trial for this firmware in order to fix the problem with we were having with the chromecast. It seems the problem has been fixed and best of all, it was all done remotely with no input or effort on our part. Thank you for a job well done!
07-22-2016 06:16 PM - last edited on 07-22-2016 06:19 PM by RogersCilio
how can u upgrade the modem for chromecast ?
still not working
07-22-2016 07:12 PM
Please refer to the first post of this thread for instructions on how to participate in the firmware trial.
07-22-2016 08:16 PM - last edited on 07-24-2016 01:00 PM by RogersMoin
This firmware 184.108.40.206 seems working fine now. However I observe one strange thing, like I cast from my device to TV, its working fine and then if I switch off the TV, device casting keeps on working and after I switch on my TV again, casting will resume from what is device is casting at that moment.
I feel expected behaviour should once I switch off the TV casting should stop as destination device is OFF.
This I feel is not a big issue and have a workaround to disconnect the casting from the device always. So everything will work fine.
07-23-2016 12:40 AM
07-23-2016 03:33 PM - last edited on 07-24-2016 01:01 PM by RogersMoin
Please sign me up for this.
07-23-2016 05:00 PM
Maybe Let me clearify my IPv6 issue
I am using the device on Bridge Mode
I have connected a Cisco 2800 series router as my main router
First time, I can get DHCP Client v6 to got IPv6 assignment from the WAN port.
but say after 15 minutes, after reboot the Cisco Router
I can no longer get IPv6 Assignment from the WAN Port
I have to reboot the Rogers Modem in order to again get IPv6 address assignment.
Any fix from this?
07-23-2016 10:29 PM - last edited on 07-24-2016 01:01 PM by RogersMoin
What are you signing up for ? Is there a new firmware coming out to fix the latency issues ?
07-24-2016 11:26 AM - last edited on 07-24-2016 01:01 PM by RogersMoin
For the last week I can't even get close to my speeds posted here:
This is what I'm getting for the past week and the only thing I noticed is my IP address has changed which doesn't happen very often.
Any reason why such a fall off in speed? I have the 250/20 plan.......!
07-24-2016 01:10 PM - edited 07-24-2016 01:13 PM
07-24-2016 05:13 PM
220.127.116.11 for my CGN3ACSMR and why because I like testing things.
07-24-2016 08:02 PM
07-24-2016 09:49 PM
I wold like to join the firware trial as I am having issues with using Chromecast with my Rogers Wi-Fi Modem. Thanks.
07-24-2016 09:55 PM
Guys, what the heck? These new modems have broken:
Wifi light on
@RogersDave could you consider letting us bring our own modems? I've had zero issues with my motorola surfboards for over a decade! These hitron modems break everything!
07-24-2016 11:26 PM - edited 07-24-2016 11:37 PM
@user12343543 I'm assuming that your referring to a CGN3ACSMR. Here's a quick summary:
Problem: Fixed in Version:
Chrome cast 18.104.22.168
Wifi light on 22.214.171.124 or .21
ports dying 126.96.36.199
If for some reason you have a CGN3ACSMR with 188.8.131.52 loaded, then yes, you will see those problems. By now I would expect any CGNAC3SMRs to be updated to 184.108.40.206 across the network with 220.127.116.11 available on request. If you have .21 loaded, then the only problem you should be seeing is Chromecast connectivity and latency due to the introduction of the Casa CMTS equipment, which Rogers and Casa are resolving.
07-24-2016 11:36 PM
@ytwytw the first thing I would do is remove the Cisco 2800 from the network, kick the modem back into Gateway mode and determine if a connected pc or laptop retains an IPV6 address longer than 15 min. If so, reboot the device and determine if it picks up an IPV6 address as its rebooting. You could do the same in Bridge mode, just have to keep in mind that your pc firewall is protecting the pc instead of the router. I would run a connected pc or laptop in that configuration only as long as it takes to do the test.
If the test is successful, especially if its in Bridge mode, then I would assume that the problem is with the router settings or scripts for IPV6 operation. If so, then you should probably post your question to a Cisco forum. I suspect that you will see some response. I don't think you will see another response here unless someone else happens to be running a Cisco 2800 router.
If the test is not successful, and the connected pc or laptop loses the IPV6 address, that is something that could be looked at. That would point to a modem or CMTS problem of some type. It would help to run the test with two devices to rule out any issue with one specific device.