*** 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*
@crazyshot, yes you have packet loss between the modem and the CMTS. What I would suggest is to download Pingplotter and use it to look for packetloss occurance so that you can cue tech support to have a look at the modem to CMTS path when the packetloss is at its worst. You don't have to buy the program unless you decide to. After 14 days it will kick down to a limited freebie mode which is still usefull to look for packetloss. Have a look at the following post on how to set that up:
You are also showing packet loss at the following Rogers servers, which are the last Rogers servers before jumping off to the Riot Games servers:
209.148.230.134
209.148.230.138
Keep an eye on those servers to see if the packet loss continues throughout the day, as in its a persistent loss. If so, call tech support and ask to speak with a Level II tech regarding the server. The Level I tech won't be able to help as this is a network issue. The Level II tech probably won't be able to resolve it but, he or she should be able to report the problem to the NOC or the Network Engineering staff. If you have no success with reporting this, please let us know.
Fwiw, I'm running a WinMTR to 104.160.131.101 at the moment and do not see any packet loss all the way to 104.160.131.101
That is correct. Just to make sure that you have the correct address, try this:
1. Enter www.google.ca as a target in the address bar and hit the go button. You should see the bottom panel display the www.google.ca address results.
2. Right click on the second IP address, which will be the IP address following the modem. In this case its the CMTS. Select the second option to copy the IP address.
3. Pause pingplotter and paste that address into the address bar. Change the interval time to 1 second. Hit the restart selection at the right side of the address bar.
When pingplotter is running with that CMTS address in the address bar, you're monitoring the modem to CMTS path, looking for packet loss and high ping times. If you see persistent packet losses, thats the time to call tech support to have the CSR run a signal check on the modem and then ping the modem from the CMTS or ping the CMTS from the modem. If you can see packet loss via pingplotter, then the CSR should be able to see the same. That will probably lead to a tech visit.
Pingplotter automatically puts the target address display on the bottom panel. If you click or double click on any of the intermediate addresses on the way to the target it will open up another panel to show the ping results from that intermediate address. To hide a display, right click on the display and select "Hide". In this particular case, and at this particular time, we're only interested in the modem to CMTS path, so, anything beyond the CMTS won't help in determining what the problem might be.
Hope this helps. Please let me know if you have further difficulties running Pingplotter.
-
496034 views
-
295 Likes
-
-
