Send a message to @CommunityHelps requesting a reload of 33T3. I suspect that Dave is busy as usual so it might take a day or two to accomplish.
@mozerd wrote: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. 
@arnym21 wrote:
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.
Based on the feedback received, it appears that the firmware 2.0.10.33T3 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 2.0.10.33T3?
--Dave
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:
- You must be part of the firmware trial program
- You must allow pings from the Internet (in the firewall configuration, "allow ping from WAN")
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.
--Dave
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.
-
931927 views
-
669 Likes
-
-
