*** 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 2.0.10.20 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).
Bufferbloat
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 2.0.10.27 but more likely in 2.0.10.28 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 2.0.10.27
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 2.0.10.27
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 2.0.10.26T2
List of connected device does not get fully populated
This is a known issue that has been tracked since firmware 2.0.10.13. 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 2.0.10.26T2 (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 2.0.10.26T2
Missing SC-QAM Channels
After a reboot, some modems are missing SC-QAM channels. A fix has been implemented in 2.0.10.26T2 to address this behavior but it has not corrected all scenarios.
Investigation continues with Hitron.
WiFi Survey
The WiFi Survey functionality in firmware 2.0.10.26T2 (and possibly before) reports incorrect SSID names.
Guest Network
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 2.0.10.26T2.
Update April 22: This issue has been resolved in firmware 2.0.10.27
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.
- Improvement in WiFi speeds
- Improvement in latency / bufferbloat
Dave
*Edited Labels*
Personal opinion, I would run a factory reset. That's a last resort option if a modem restart doesn't resolve the problem.
@QueJoder I've forwarded your entire post to Dave. Please delete the entire post, except perhaps for the last paragraph if that is what you would like to do. The entire post contains the modem MAC address, serial number etc, which shouldn't be left in an open forum. Dave can either respond to your post or message you via private message when he has the time. As he has indicated previously, he is working with the Rogers, Hitron, Intel and Casa Systems engineers to determine the cause of the poor performance issue observed with DOCSIS 3.1 and develop the firmware changes necessary to correct the problem. As a result, he does not have the time to address individual issues as he would like to, so, as a result, we will have to be patient while the combined staff of Rogers, the chipset developers (Intel), manufacturer (Hitron), and CMTS manufacturer (Casa Systems) work out the details to correct the problem.
Tested 4:00 am Thursday, February 16. On version 2.0.10.13.
On Rogers' own speed test service, the results were 805dn, 33up & 8ms latency.
What speed *should* I be getting? What speed test is most accurate?
This test firmware has been running for over 12 hours on a few modems. I am trying to provide some feedback on the effectiveness and make a decision by the end of the day to extend to program to a larger audience. Any feedback is appreciated...
@JohnBeaudin wrote:Ping lower?? OMG I WANT IN lol
@JohnBeaudin, I know you want lower pings but in your case, the biggest problem is simply physical distance and the laws of physics apply....
There are core network improvements in the work this year and next year which may help you a bit but no silver bullet on the modem.
@jjunge wrote:
With this revised .23 firmware I now have a new problem. Nothing hardwired with Ethernet is connecting anymore. My VoIP modem and Xbox - as if they are not plugged in at all. Wireless is fine - help! Anyone else?
@jjunge, I tried looking at your modem and see 1 ethernet port up and was able to ping from the modem GUI a device which I believe is hardwired. Was there any change last night?
@Bob35789 wrote:@RogersDave I Have done a restart my speeds are even slightly worse. 50v/8^
@Bob35789, I tried investigating your modem but you are running in bridge mode and I therefore have no visibility or ability to run performance tests. From what I see everything looks fine on my side.
Dave
So far so good for me here. Did a bunch of Streaming with Beam.pro last night. Their new FTL protocol allows for latency free streaming and my connection did not let me down. I was able to maintain a 60fps 1080p Stream with latencts sub second to my viewers.
Spent the rest of the evening streaming media from streaming services untill i fell asleep, woke up this morning to the internet STILL WORKING as expected. *so happy*
We may have something nice here.
http://www.speedtest.net/result/6057838885.png
-
475885 views
-
295 Likes
-
-
