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.
Latency and Ping times have deteriorated
I'm curious what software do you use to gather statistics? I see some people mention latency and ping, but never mention software used to collect that data over a statistically significant time frame.
|WAN Up Time||005 days 13h:06m:01s|
upload/download speed fairly stable. coda in gateway mode, wired connection primary user. Thanks @RogersDave
Based on the feedback received, it appears that the firmware 126.96.36.199T3 is stable (no reboot issue). I have seen reports of increased latency in this thread but it seems limited and the firmware does not contain anything (from .33 to .33T3) that would impact the latency.
During our internal testing, we have however identified a potential issue with Huawei P10 phones in our lab where it seems that it makes the modem reboot when connected to WiFi. My question for the community, does anybody have a Huawei P10 phone used successfully on the CODA-4582 modem running firmware 188.8.131.52T3?
Latency spikes can be caused by a variety of factors, the modem firmware can be a contributor in some cases but there are also potentially load on the network, signal problem, maintenance, etc.
I would like to run an experiment and actively monitor the latency towards between a fixed point on the Internet and your modem over time. This will give me a better view of what happens over time and give me a reference point between versions of software to quickly detect issues.
I would like to start by monitoring about 10 modems and see if there is value. I would like a distribution between CODA modems and CGN3 "AC" series, bridge mode and gateway mode. The only 2 restrictions are that:
If you are interested in participating, send me a private message and I'll take it from there. I'm especially looking at those who complained about latency to me recently (@mozerd, @Mythen, ...). If you are running your own firewall, I can also provide the source IP where the traffic will be monitored from for a more granular firewall rule.
Sounds like a plan. But ...... there is a huge difference between the gaming situation which most likely uses UDP, and ping, which uses ICMP. Fwiw, from my own testing, the 4582 does not have any issues with UDP, TCP/IP or ICMP in terms of latency thru the modem and any UDP losses are negligible. Latency to some far off end point thru several servers is a different matter. I think, at the end of the day, the following questions also need to be asked:
1. What game are you playing and whats the update rate, 30 Hz or maybe 60Hz (Overwatch selectable); and
2. What protocol is in use (UDP or other?): and
3. What's the path to the gaming server, short or long convoluted path using Cogent, and what's the load thru the various servers enroute to the gaming server; and
4. Does Rogers peer with the gaming company thru a server in Toronto for example or does the game traffic take the long route thru various ISPs before it hits the gaming server; and
5. What's the time of day where the issues are seen; and
6. Is there anything else going on in the house in terms of modem traffic, ie; gaming, streaming, VOIP or VPN, etc, etc; and
7. What modem do you have, if you have a CGN3xxxx series modem, where are we in terms of finally resolving the ICMP / TCP/IP / UDP latency for the Puma 6 modems. Are we there yet?; and
8. Is there a resolution to the problem of some 4582's running slow data rates? ; and
9. Are you running the modem in Gateway mode or Bridge mode with a follow on router, and if so, is your router able to handle the load as you are expecting it to; and
10. Are you connecting via ethernet or Wifi, where Wifi brings its own problems into the picture. You should be gaming or running any latency intolerant application via ethernet, personal opinion; and
11. Whats the load on the CMTS, which the modem is connected to;
I'm sure that there are other questions that might be applicable, but these are the first that come to mind.
That's from near academic point of view. But so far what I seen is primarily "modem reboot" posts without any useful info attached or systemic attempt on reporters side to present it in an actionable way. Almost no posts re features restricted or missing, no detail reports on use cases resulting in a certain defect pattern. I guess the thread is still useful as an alert to major FW issues requiring immediate resolution or reversal.
Factory reset which takes you back to .28T2(?) or a modem reboot?
Thanks for the keen eye Datalink ..... and my apologies ... it was a modem reboot not a reset ... still on .33T3
BTW, i had to use Google Chrome to post this message ..... unable to post here using the new Firefox v 57 .... Firefox just loops and loops.
I'm impressed by the 184.108.40.206T3 stability. Nearly 12 days of continuous uptime, compared to the previous 220.127.116.11 levels of only a day or so.
Continuous , but random, network load here, including permanent VPN activity.
Issues connecting chrome cast solved
I tried everything from contacting chrome cast multiple times and Rogers aswell... trial and error... searching online for solutions... finally the 7th or 8th person I talked to that knew what he was talking about. We tried his solution and it worked for me... chrome cast fully operational and connecting properly. The solution for me was to call Rogers and request them to reset the modem back to factory default settings. It will lose a bit of security but will allow chrome cast to connect and that is the reason chrome cast isn't connecting because Rogers has adjusted the security settings on yhe modem so things like chrome cast will not be able to connect properly. I hope this helps some people with the same issues I had for months after many many calls... hours of waiting... hours of talking finally a real solution that worked for me.
Just an update for @RogersDave
Looks great, .33T3, alot of my issues have gone away, however, its still giving me some issues that are oddly strange, for instance, Im occationally disconnected from Netflix servers for sometimes, upto 5min at a time.... I can browse fine in my browser, but every episode I click on I get a No Network error, even if I was in the middle of an episode, itll stop, and ill do absolutly NOTHING to the computer or network, but at somepoint, ill click to resume, or another show, and bam, all good and fine for a while...
Anyways, was just a note to pass along, and see if anyone else has been expreiencing it on 33T3.
As for me, my CODA looks great,
|WAN Up Time||010 days 04h:34m:30s|
but still some DOCSIS Events over that time, not sure if they relate with my netflix issues, didnt record times unfortunatly.....
|15||11/09/2017 13:09:05||90000000||warning||MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=******;CMTS-MAC=******;CM-QOS=1.1;CM-VER=3.1;|
|16||11/11/2017 08:57:10||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=******;CMTS-MAC=******;CM-QOS=1.1;CM-VER=3.1;|
|17||11/12/2017 14:50:33||90000000||warning||MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=******;CMTS-MAC=******;CM-QOS=1.1;CM-VER=3.1;|
|18||11/19/2017 18:39:57||68010300||error||DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=******;CMTS-MAC=******;CM-QOS=1.1;CM-VER=3.1;|
|19||11/20/2017 16:40:56||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=******;CMTS-MAC=******;CM-QOS=1.1;CM-VER=3.1;|
DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=******;CMTS-MAC=******;CM-QOS=1.1;CM-VER=3.1;
Thanks again fro all your work, everyone on the Rogers team
@jeff77 Question about your Chorme Cast issue... cuz I had an issue before, a while ago with mine, and I dont have any of the problems now, and it had NOTHING to do with the modem security settings, well not really.
My question is, are you trying to connect your Chrome Cast on your 5G wifi or 2.4?
Sounds ridiculous, but 5G wont work, and thats Chome Casts fault, not Rogers or the modem.
Took me MONTHS to fix mine, almost thru my FOUR chromes casts out and was going to buy Amazon Fire Sticks or somthing else, but then I found an obscue thread online about the issues, and tried my 2.4 instead, and no more issues since, use mine every single night.
And also, I doubt Rogers would ever intentionally change any security settings to stop any devices, especially a GOOGLE device, from connecting, it would be somthing on the devices end, software or somthing, causing the issue.... They are partnered with Google on the Google Home right now, and I doubt they would risk anything with that for any reason, security or anything, they would just ask Google to update their software to work with the new security, as they should be doing either way.
I am having the same sort of issues some of you are having. 33T3 seem to be stable but I am having events as well (see logs below)
|14||11/20/2017 00:36:46||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=*****;CMTS-MAC=*****;CM-QOS=1.1;CM-VER=3.1;|
|15||11/20/2017 13:53:39||68010300||error||DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=*****;CMTS-MAC=*****;CM-QOS=1.1;CM-VER=3.1;|
|16||11/20/2017 19:49:53||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=*****;CMTS-MAC=*****;CM-QOS=1.1;CM-VER=3.1;|
|17||11/21/2017 22:40:08||90000000||warning||MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=*****;CMTS-MAC=*****;CM-QOS=1.1;CM-VER=3.1;|
|18||11/22/2017 16:06:07||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=*****;CMTS-MAC=*****;CM-QOS=1.1;CM-VER=3.1;|
|19||11/22/2017 22:40:04||68010300||error||DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=*****;CMTS-MAC=*****;CM-QOS=1.1;CM-VER=3.1;|
|20||11/22/2017 22:43:00||90000000||warning||MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=*****;CMTS-MAC=*****;CM-QOS=1.1;CM-VER=3.1;|
First my setup:
I am using the Coda connected to my C7 Archer via LAN to WAN connection. The Coda IP is 192.168.0.1 while the C7 is 192.168.1.1. I had DHCP setup for the Coda at 192.168.0.10 to 192.168.0.100 while the C7 is setup from 192.168.1.101 to 192.168.1.199
What I cannot seem to figure out is why my wifi from the Coda drops out from all my devices and a reboot is necessary to get the wifi connected again (but will drop out again after a few minutes). The wifi from the C7 is stable though except for the last few days which seem to correspond to the event log from the Coda.
Hopefully somebody from the forum will be able to help me out. Thanks in advance.