*** 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*
.27 firmware is working great for me!
@RogersDave Hope you can have a look and give some help here.
Going on 7 days now this is what my Logs look like daily
No. Time Type Priority Event
1 05/09/2017 18:36:45 82000300 critical Ranging Request Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
2 05/09/2017 18:36:45 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
3 05/09/2017 18:36:45 85010200 warning TCS Partial Service;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
4 05/09/2017 18:37:01 82000500 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
5 05/09/2017 18:37:02 82000300 critical Ranging Request Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
6 05/09/2017 18:37:02 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
7 05/09/2017 18:37:18 82000500 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
8 05/09/2017 18:37:19 82000300 critical Ranging Request Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
9 05/09/2017 18:37:19 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
10 05/09/2017 18:38:03 82000500 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
11 05/09/2017 18:38:13 82000300 critical Ranging Request Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
12 05/09/2017 18:38:13 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
13 05/09/2017 18:39:52 82000500 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
14 05/09/2017 18:39:57 84000500 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
15 05/09/2017 18:40:03 84020200 warning Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
16 05/09/2017 18:40:28 82000400 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
17 05/09/2017 18:46:05 84020200 warning Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
18 05/09/2017 18:48:54 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
19 05/10/2017 02:26:09 90000000 warning MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
20 05/10/2017 17:14:03 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:17:10:93:6b:90;CM-QOS=1.1;CM-VER=3.1;
Talking to support I have been told such things as, there is nothing wrong, Their Tools to check the Node and my connection are down for service and "You should use wired connections instead of wireless, that will solve your problems"
My connection starts to lag out, i get packet loss and then the modem reboots its self eventually.
To signup for the trial firmware if you're interested, send a private message to @CommunityHelps. Follow that link to the public page for @CommunityHelps and then select the link on the right hand side to "Send this user a private message" to navigate to the message composition page. It will already be addressed.
Fill in the title: CODA-4582 Modem Firmware Trial
In the text area, add your modems: MAC Address
Serial Number
Modem Model: CODA-4582
The first two can be found in the Status page when you log into the modem or on the back of the modem. They can be copied from the Status page and pasted into the message.
When you're logged into the forum, watch for a number overlaid on your avatar at the top right hand corner signifying a response from one of the moderators. Select that link and follow it down to your message inbox. You should see a disclaimer that has to be acknowledged prior to loading the latest version of trial firmware.
Keep an eye open on this thread or the Open Issues thread for any particular requirements for rebooting or running a factory reset on a modem with trial firmware loaded. Usually there are no special instructions, but, that can happen occasionally. For V2.0.10.27, you can reboot or restart the modem after disconnecting the modem power and the modem will remain at V2.0.10.27. If you run a factory reset the modem will revert back to V2.0.10.26T2 which is the current network wide version for the CODA-4582.
@Jeffj can you log into the modem, navigate to the STATUS .... DOCSIS WAN page, copy the downstream and upstream tables and paste them into a post. Maybe the signal levels will indicate something??
Are you using VPNs by any chance?
Whats the target for the pingplot? Just wondering why its so high to start with?
-
481696 views
-
295 Likes
-
-
