*** 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*
@notregistering can you run a modem restart/reboot now. Pull the power, wait for 30 seconds and plug the power back in to force a restart. After that, check to ensure that you have 32 DOCSIS 3.0 channels running and the DOCSIS 3.1 channel as well. If you have any issues after the restart, consider running a factory reset.
Okay just upgraded to the Gigabit sevice so here are my first results!
Wired results!
Now this is Wireless 5g via the Hitron Modem and Killer Wireless-n/a/ac 1525 Wireless Network Adapter!
Downstream Overview
| Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
| 1 | 591000000 | 256QAM | 4.100 | 31 | 38.605 |
| 2 | 363000000 | 256QAM | 2.100 | 10 | 40.366 |
| 3 | 369000000 | 256QAM | 2.800 | 11 | 38.983 |
| 4 | 375000000 | 256QAM | 2.300 | 12 | 38.983 |
| 5 | 381000000 | 256QAM | 1.500 | 13 | 38.983 |
| 6 | 387000000 | 256QAM | 2.000 | 14 | 38.605 |
| 7 | 393000000 | 256QAM | 2.300 | 15 | 40.366 |
| 8 | 399000000 | 256QAM | 2.800 | 16 | 38.983 |
| 9 | 405000000 | 256QAM | 2.700 | 17 | 38.983 |
| 10 | 411000000 | 256QAM | 2.700 | 18 | 40.366 |
| 11 | 417000000 | 256QAM | 3.400 | 19 | 40.366 |
| 12 | 423000000 | 256QAM | 3.800 | 20 | 38.983 |
| 13 | 429000000 | 256QAM | 3.600 | 21 | 38.983 |
| 14 | 435000000 | 256QAM | 3.000 | 22 | 40.366 |
| 15 | 441000000 | 256QAM | 3.200 | 23 | 38.983 |
| 16 | 447000000 | 256QAM | 3.100 | 24 | 38.605 |
| 17 | 555000000 | 256QAM | 4.600 | 25 | 38.983 |
| 18 | 561000000 | 256QAM | 4.800 | 26 | 38.605 |
| 19 | 567000000 | 256QAM | 5.100 | 27 | 38.983 |
| 20 | 573000000 | 256QAM | 4.500 | 28 | 38.983 |
| 21 | 579000000 | 256QAM | 4.900 | 29 | 38.983 |
| 22 | 585000000 | 256QAM | 4.400 | 30 | 38.605 |
| 23 | 357000000 | 256QAM | 2.100 | 9 | 38.983 |
| 24 | 597000000 | 256QAM | 3.800 | 32 | 38.605 |
| 25 | 603000000 | 256QAM | 4.500 | 33 | 38.605 |
| 26 | 609000000 | 256QAM | 5.600 | 34 | 38.983 |
| 27 | 615000000 | 256QAM | 5.900 | 35 | 38.983 |
| 28 | 621000000 | 256QAM | 6.100 | 36 | 38.983 |
| 29 | 633000000 | 256QAM | 5.600 | 37 | 38.605 |
| 30 | 639000000 | 256QAM | 4.900 | 38 | 38.605 |
| 31 | 645000000 | 256QAM | 4.100 | 39 | 37.636 |
| 32 | 651000000 | 256QAM | 3.900 | 40 | 38.605 |
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 |
Upstream Overview
| Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
| 1 | 23700000 | ATDMA - 64QAM | 39.750 | 2 | 6400000 |
| 2 | 38596000 | ATDMA - 64QAM | 42.750 | 3 | 3200000 |
| 3 | 30596000 | ATDMA - 64QAM | 40.750 | 1 | 6400000 |
OFDM/OFDMA Overview
| Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
| 0 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
| 1 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
Modified my Killer Wireless-n/a/ac 1525 Wireless Network Adapter and got this.
@merms, @hen555, @ghost1001, @MegnaGaming, see the following post to request the latest firmware for the 4582:
That request will also place your modem on the trials list for future trial builds and on the exclusion list to prevent the firmware from rolling back due to the nightly or weekly firmware check that runs across the network.
@MegnaGaming, ok understand. If that still isn't done, I'd call tech support or get back on twitter to have them push the firmware tonight. Note, that this isn't normal ops for the CSRs to push trial firmware. That is usually done thru @CommunityHelps and crew, or directly by Dave. Also note that the request still has to go in thru @CommunityHelps to ensure that the modem is placed on the exclusion list, otherwise it will roll back during the night to the latest production version which is currently .19
@ghost1001 wrote:
I got this too! I was on .24, but got downgraded to .19. Looks like the message appeared after the downgrade.
I know some of you got downgraded back to 2.0.10.19. I'm really sorry for that. I pushed the upgrade to thousands of modems over the week-end and may have missed a batch in the exclusion list.
I have re-upgraded you and correctly added you to the list.
I also processed most trial firmware requests up to the ones received Sunday. I will handle the rest today.
Now, the firmware 2.0.10.24 is scheduled to go live in production today (unless something major comes up) with automatic upgrade on boot. Once this is done, all that will be needed is a reboot of the modem (or for a new modem to plug it in) to receive the latest firmware.
Dave
-
481740 views
-
295 Likes
-
-
