*** 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*
As indicated in the following link:
If you are interested in participating, please send a private message to @CommunityHelps with the subject line “Rogers Rocket Wi-Fi Modem Firmware Trial”. A member of our team will be in contact with you and provide you with further instructions.
Follow this link to the @CommunityHelps public page. On the right is another link to "Send this user a private message". Follow that link to the message composition page. Its already addressed. Add in the title Rogers Rocket Wi-Fi Modem Firmware Trial.
In the text of the message, include your modems MAC address and serial number which can be found on the modem's STATUS page when you log into the modem. When done, hit SEND.
Watch for a number overlaid on your avatar in the upper right hand corner when you are logged into the forum. That will indicate a message is waiting for you in the message inbox. Click on the avatar of follow the procedding links to the inbox to acknowledge the required waiver.
@QueJoder If you ever do notice DHCP RENEW WARNING or MIMO Event MIMO, these are just normal tasks the modem carries out so you don't need to worry about this. The only thing I would worry about is if I see excessive amounts of No Ranging Response received - T3. For instance, if you saw 4-10 all under 1 date then that would be an obvious sign that something is wrong.
From the looks of everything, it looks good. If I were you I wouldn't need to worry about anything. 
@NBomb wrote:So, when is .26 supposed to be going live to everyone? AFAIK I'm not on it yet, but everyone seems happy with it.
Firmware 2.0.10.26T1 and 2.0.10.26T2 have been quite successful but they are interim test builds that will likely not be distributed outside of the trial program.
We are currently working on firmware 2.0.10.27 which additional performance improvements. That firmware should be available for general release after completing our internal validation and testing with the community. Before someone asks, I do not have the date or release notes yet but I expect this firmware in the next 2 weeks.
Dave
@belowme you're missing the DOCSIS 3.0 Downstream channels from 9 to 32. Are you running an original CODA-4582 or one that has a single or double black dot (round black sticker) near the power cord of the modem? In either case, the missing channels would suggest severe cable signal issues. Two things need to happen.
1. If you have an original CODA-4582, you should swap that for one that has a single or double black sticker which indicates that there is additional shielding above the DOCSIS cable tuner. That is designed to prevent 2.4 Ghz wifi interference with the DOCSIS tuner which results in missing cable channels.
2. Call tech support and ask the CSR to run a signal check on the modem. With your current DOCSIS 3.0 channels, that should fail automatically, leading to a tech visit at your convenience. When all is said and done, can you repost the signal levels, just to see how they turned out.
-
466405 views
-
295 Likes
-
-
