*** 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*
Hello, @igorella1
Thank you for posting your concern in the Community. I appreciate your patience throughout the ordeal, we can definitely look into it for you. Please send us a private message at @CommunityHelps. Our private messaging system is explained in this blog.
Thanks, @Telek and @Datalink for your continuous contribution to the Community.
Regards,
RogersMoin
@igorella1, fwiw, the CGN3ACR will handle your internet plan data rates. The slow wifi could be the result of wifi settings, channel setting or physical construction of the modem.
The CGN3 series modems have three 2.4 Ghz antenna and three 5 Ghz wifi antenna which are all mounted on one side the motherboard. That motherboard sits vertically in the modem. The CODA-4582 has three 2.4 Ghz antenna and four 5 Ghz antenna all of which are mounted at the top of the modem, and therefore away from any interference and shielding from the motherboard. The motherboard sits below the antenna. All other things being equal, my personal opinion is that the 4582 would deliver better omni-directional wifi service although I would have to see the wifi test results to really confirm that.
Slow wifi speeds can also be caused by the wifi settings and the wifi environment that you're in, ie: who are you competing with for clear wifi channels. With that in mind, when you have time, can you read thru the following post and make any changes necessary to the wifi settings. The aim of course is to bring the wifi data rates up to where they should be.
http://communityforums.rogers.com/t5/Internet/slow-wifi/m-p/399949#M47222
For the external connections, the green box that you referred to is the local tap, which services your internet, cable tv and Home Phone, and that of your neighbors as well. If you're having problems running a CODA-4582, then your neighbors are probably suffering the same problem. If the tech swapped cable ports at the tap to check the signal levels thru those ports, that would have indicated whether or not the issue was with your cable port or with the whole tap itself or further upstream. Its possible that the tap across the street was on another cable entirely, which runs to the neighborhood Cable Modem Termination System (CMTS). That CMTS is a green metal box, about three feet high, and approximately three feet by three feet square, possibly slightly larger. The CMTS services all of the neighborhood taps, and therefore all of the neighborhood cable internet, tv and Home Phone services provided by Rogers and TPIAs, thru the Rogers cable system. You might walk past it or drive past it every day, not realizing what its for.
So, there are three possible locations for problems, at your local tap, at the CMTS, or, in the cable that runs from the CMTS to the local tap. Its conceivable that the problem was thought to have been isolated at the CMTS, and therefore the work order was cancelled. If the tech that cancelled the work order did not check for the results at the local tap, then, as you discovered, the problem could still exist at the local tap. Someone will have to go back in, determine what the problem is and call in the necessary resources to see that the problem is corrected. Small consolation at this point, but, just pointing out what might have happened.
While the CGN3ACR can handle the speeds that you're at, this will potentially be a bigger problem for anyone running gigabit service on a CODA-4582 thru your tap. Your neighbors should be complaining if they're in that situation.
I'm hoping that @RogersMoin can get this back on track and get your internet service back to where it was previously.
I just ran a speedtest from the Eastlink server @gp-se and my speeds were 298.29 and 36.92. Pretty pathetic for a 1 GB service.
Here is the speedtest from the Toronto Speedtest.net server:
@gborges, when you call tech support, ask the CSR if the OFDM channel signal level and signal to noise ratio is within spec. The data for the OFDM DOCSIS 3.1 channel isn't correct in the user interface, but, tech support has access to the correct data. As for the low upstream DOCSIS 3.0 levels, these days, on the 4582 modem, the low upstream levels are more noticeable. That shouldn't cause any issues, but, its rather strange to see given the historical levels with previous DOCSIS 3.0 modems which ran somewhere in the 36 to 40 dBmV range. The CMTS actually determines the modem output levels, commanding an increase or decrease, so, if the CMTS is satisfied with low upstream levels, thats ok. You could ask the CSR for the upstream signal level and signal to noise ratio at the CMTS. It should be at or above 0 dBmV with a signal to noise ratio at or above 25 dBmV. That will tell you if the modem output is ok, or if perhaps the CMTS isn't commanding the required levels to meet those input levels.
While you're on the phone with tech support, ask the CSR to check the modem provisioning and ensure that its set for your internet plan, 150/15 if I remember that correctly.
-
495744 views
-
295 Likes
-
-
