*** 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*
@f3ndotwrote:CODA-4582 reboots when Huawei P10 connects to 2.4G Wi-Fi
This one had me stumped pretty bad. Wondering why my internet dropped every time my friend's new Huawei P10 attempted to join the network.
Model: CODA-4582
Hardware Version: 1A
MAC: xx:xx:xx:xx:xx:xx
Current Firmware: 2.0.10.33T3
We've tested on two separate occasions, around 5x each. The last 3 times today, I sat with `ping 8.8.8.8` running and had her connect to WiFi. Immediately I got "Request timeout for icmp_seq nnn". Having her disconnect herself from WiFi at this point is too late and I watch the router reboot itself and come back online in ~3min. We can then repeat and reproduce the issue, although sometimes it takes up to 60sec before it times out.
I have never seen this before and not sure how to proceed. I consider myself pretty technically savvy and am clueless. I'm hoping maybe @RogersDave can shed some light on this... Is her phone's MAC buffer overflowing my router?
My friend's phone details:
Model: Huawei P10, VTR-L09
Android Version: 7.0
Please help, this is a sucky thing to try and diagnose 😞
We have not heard from Rogers on this. I'd say that this is important. How can you attract their attention?
Perhaps you should start a new topic. Maybe they would notice.
Perhaps you could phone Rogers Support.
Any other ideas?
@qwerk007, the biggest problem that you have is the lower frequency response below 500 Mhz. That port ID 14 at 303 Mhz is either above or below the OFDM channel, which is 192 Mhz wide to support 4k DOCSIS 3.1. Compared to the DOCSIS 3.0 channels running above 500 Mhz, that port 14 is very low and while still in spec (theoretically), could result in a performance penalty if the modem was running DOCSIS 3.0 on the downstream side. One can probably consider that DOCSIS 3.0 channel as a good indicator of the health of the DOCSIS 3.1 OFDM channel, as the OFDM data is not entirely correct in the user interface. Your modem is running DOCSIS 3.1 on the downstream side, so, if you're seeing poor performance from the modem, that low signal level would certainly explain it. The upstream DOCSIS 3.0 channels aren't too bad, but channel 2, which is the highest channel in terms of frequency is running at a slightly higher power level than the other 2 channels. So, my guess is that your local tap and possibly your underground cabling need some attention to get the 0 to 500 Mhz performance back to where it should be. When the work is done, have a look for that 303 Mhz DOCSIS 3.0 channel and see if its back up around 0 dBmV where it should be. That should be a good indicator of whether or not to expect reasonable performance out of the DOCSIS 3.1 OFDM channel.
-
495593 views
-
295 Likes
-
-
