*** This post was last edited May 2, 2017 ***
Good morning Community,
As I mentioned in a post two days ago, we have received the next firmware 220.127.116.11 from Hitron. We are currently running initial testing on this version and will push it out to participants in the firmware trial program as soon as it passes initial testing.
However, while running these tests, we discovered abnormal behavior with ICMP and are awaiting feedback from Hitron today to asses how this will be addressed. As soon as I this is confirmed, I’ll update the change log with the correct version information and start pushing it out.
In parallel, we are still working on the following high priority items. In some cases below, I requested affected customers to reach out to me via private message. If you do so, please include your modem MAC address in the subject line (even if we exchange messages daily) as there are a lot of you reaching out to me daily 🙂
UDP Packet Loss
The investigation for what has been reported as UDP packet loss is still ongoing. We have deployed a probe at one fellow forum member on both a CODA-4582 and a CGNM-3552 to collect additional data. We are actively working with Hitron and Intel on the results observed.
Based on what we know so far, in most instances UDP packet loss is coupled with higher uplink usage in the area. Although the impact is noticeable in specific logs (League of Legends), the root cause for the perceivable impact (while playing) is likely related to bufferbloat (see next issue).
When comparing the performance of a CODA-4582 to a CGNM-3552 in the same network conditions, the CODA-4582 consistently reports higher bufferbloat when tested on DSLReports.
Update April 12: The solution for this problem will come in two folds. It will require a change in software which will possibly be included in 18.104.22.168 but more likely in 22.214.171.124 and a change in network configuration.
The network configuration change is not compatible with the current firmware so this change will only come after a vast majority of the modems are running the new code. We are however looking at a way to make the change only for specific modems to support testing in the community.
Update April 22: This problem seems resolved in firmware 126.96.36.199
5 GHz WiFi Low range for channels 36 to 48
Lower WiFi channels on the modem have a much smaller range. This is due in part to the limit imposed by Industry Canada to maximum transmit power.
Furthermore, the current automatic channel selection (auto mode) tends to select the lower channels when in similar load conditions.
Workaround: manually select higher channels (149-153-157-161)
Update April 22: The channel selection algorithm has been improved in firmware 188.8.131.52
Loss of OFDM Channel Lock
Under some RF conditions, the modem fails to lock properly on the OFDM channel. This typically result in variable performance.
Update April 12: This problem is resolved in 184.108.40.206T2
List of connected device does not get fully populated
This is a known issue that has been tracked since firmware 220.127.116.11. We are making improvements at every firmware but it is not a perfect system.
The situation is worst after a reboot or firmware upgrade as the list gets reset and must be repopulated as devices renew their DHCP lease.
NAT Loopback not working for wired clients
When setting up port forwarding to an internal server, it is possible for a client on WiFi to reach the server using the external IP/port. If the client is on a wired interface, it doesn't work.
Update April 12: This problem is resolved in 18.104.22.168T2 (not confirmed)
LAN Counters not working
Some customers reported that LAN counters (especially in bridge mode) are reporting inaccurate values.
This problem has been reported to Hitron for investigation.
Unexpected modem reboot
Some customers reported their modem reboots unexpectedly. We have also seen this behavior in our lab.
Update April 12: This problem is resolved in 22.214.171.124T2
Missing SC-QAM Channels
After a reboot, some modems are missing SC-QAM channels. A fix has been implemented in 126.96.36.199T2 to address this behavior but it has not corrected all scenarios.
Investigation continues with Hitron.
The WiFi Survey functionality in firmware 188.8.131.52T2 (and possibly before) reports incorrect SSID names.
When connecting to the Guest Network, an error message is displayed "only allow DHCP client to use this wireless". This has been reported in firmware 184.108.40.206T2.
Update April 22: This issue has been resolved in firmware 220.127.116.11
Update May 2: It seems this issue is not fully resolved and still experienced by some users
Future Planned Improvements
The following are items that we are working on in parallel of the above.
If your house was built a long time ago it could be wired in RG59 wiring, which is thinner and doesn't deliver the bandwidth that RG6 does. They could be rewiring it with RG6, and given what you said below, it sounds like the wiring could just be the problem. But if your services was fine before the intermittency issues, could there be another existing problem?
Just got off the phone with tech support. They've opened a ticket and while on the phone they ran some tests and said it looked pretty bad. The person on the phone didn't have all of the information (they were talking to someone else while I was on hold) so I don't know exactly what the issue is.
@lethalsniper The CGNM-3552 is much better for gaming at the moment. The modem comes with firmware 18.104.22.168, but I'm having no issues being on the firmware. If you do have Google Chromecast you'll need to sign up for the firmware trial which allows you to stream from it (firmware .21 has issues using chromecast).
It's definitley better for gaming at the moment, and if you don't want to deal with the lag and high pings, switching should be fine. Just make sure the Rogers store near you has the 3552 and you can exchange it.
Hopefully @RogersDave is busy working on pushing Intel and Hitron to fix the UDP packet loss issue, then we'll be able to switch back to the CODA. Without the UDP packet loss problems, the CODA is definitley better at UDP than the 3552. Dave mentioned that the difference b/w the CODA and the rest of the CGN series for UDP is "night and day." So once again, when the issues get fixed I'll move back to the CODA, unless they restort to collecting on-site data from me.
@Max24 It seems that there could be a CMTS issue. You should be hitting the second hop which is your CMTS. I reccomend calling customer support now and have them run some tests to check your connection and as well have them check your area node to see if there's an issue. I'm pretty sure there's an issue given that the jitter is fairly high. Let me know what they say.
Also, try setting the Trace interval to 2.5 seconds. Try doing the trace again and post the results. I wanna make sure that PingPlotter is posting accurate results.
I wish I could have some sort of ETA.. I don't want to switch and then have to switch back in 2 weeks.
It's likely that it's going to take more than that to fix the UDP on CODA but.. at this point I think I will just wait and hope for the best.
It does sound like that it'll take longer than 2 weeks to fix the issues. You can wait, but if it's really bothering you then go ahead and switch. They really need to tunnel vision into this issue and try to have this issue resolved soon, it's hard to game on the CODA-4582 given the UDP issue.
Dave is off the forums for now, but that just sounds like he's busy making our Internet better! lol
Just got back from store and got one of black modems. Girl there was amazing, she put one of them on hold for us. Looks like stores are running low, most i called didnt have any. She mentioned, like the other store i went before; people are bringing the "white" one back all the time asking for the old modems. I have the kids home this week, hopefully i stop getting text and calls about internet.
Hopefully big bugs get fixed soon, the router part so much better than "black" one, when it works.
@mhs2 wrote:Downstream Overview Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB) 4 375000000 256QAM 1.800 12 38.983 6 387000000 256QAM 2.100 14 38.983 9 405000000 256QAM 2.700 17 40.366 12 423000000 256QAM 3.300 20 38.983 14 435000000 256QAM 3.000 22 40.366 15 441000000 256QAM 2.700 23 38.983 16 447000000 256QAM 2.100 24 38.983 20 573000000 256QAM -0.100 28 38.605 29 633000000 256QAM -0.200 37 38.983 30 639000000 256QAM -0.300 38 38.605 32 651000000 256QAM -1.300 40 38.983 OFDM Downstream Overview Receiver FFT type Subcarr 0 Frequency(MHz) PLC locked NCP locked MDC1 locked PLC power(dBmv) 0 NA NA NO NO NO NA 1 NA NA NO NO NO NA
So a couple of things that I haven't seen anyone else mention -- your signal levels, although all within range, are more varied that I would like to see. -1.3 to +3.3 is a 4.6dB difference - that's small but not trivial. They're also not varied really according to frequency (from your full list). This tells me that you might have some wiring problems.
Also, you're on DOCSIS3.0 still.
@tonytoronto let us know how it goes I'm also looking to go back to the black modems for gaming because the coda at this present time is worthless for me.
its been well over an hour and i havent heard nuttin from the kids, so far so good i guess.
The router part not great, might put it in bridge mode and use my old Asus router for now.
@4kgigabitguy can you have a look at the following post and follow the instructions included.
Hopefully this will give me a little more info on the 5g settings for those users who are seeing problems on the 5g network.
Thanks @Datalink , I switched the channel bandwidth & things appear to running smoother. I'm not seeing the same results I used to get with the Rocket AC Modem on 250u in regards to wireless speed tests on 5G....I used to always get above 250-300Mbps where now, things flucate between 150-250Mbps....I have yet to see 290 Mbps which I used hit pretty often with my old modem/package.....Any other suggestions or ideas on why this would be happening ?