*** 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 22.214.171.124 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).
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 126.96.36.199 but more likely in 188.8.131.52 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 184.108.40.206
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 220.127.116.11
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 18.104.22.168T2
List of connected device does not get fully populated
This is a known issue that has been tracked since firmware 22.214.171.124. 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 126.96.36.199T2 (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 188.8.131.52T2
Missing SC-QAM Channels
After a reboot, some modems are missing SC-QAM channels. A fix has been implemented in 184.108.40.206T2 to address this behavior but it has not corrected all scenarios.
Investigation continues with Hitron.
The WiFi Survey functionality in firmware 220.127.116.11T2 (and possibly before) reports incorrect SSID names.
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 18.104.22.168T2.
Update April 22: This issue has been resolved in firmware 22.214.171.124
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.
Still waiting for the new Firmware .23! http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/message-id/331...
*IPv6 remains disabled on this modem until all modems are upgraded
Will everyone please be patient! When Dave is ready to push .23 to the modems registered for the trials builds, it will happen. If that hasn't happened so far, its either because he's busy, or there are some i's to dot and t's to cross before the distribution can happen. A day or two isn't a big deal!
I have swapped my modem as you suggested and have PM'd you my serial number and info. When you get a chance, can you please push the latest firmware to it and also feel free to connect to it at any time for your testing.
A couple of nights ago, my internet connection died around midnight on Tuesday (so Wednesday morning) and I tried to call Rogers (But it said there was a wait of about 40min) so I decided to just wait it out. It came back online about an hour after but since then it's been REALLY slow.
Online gaming gets severely laggy, and speed tests show my uploads have gone down from my usual 27-29Mbps down to around 5Mbps-10Mbps Max. Websites hang and load slow as well.
Download speeds seem to be okay but erratic. There's definitely something wrong with theconnection though as this wasn't happening before.
Note I have tested the speeds using Rogers speedcheck and Speedtest.net, as well as on my Xbox One, wired directly to my Nighthawk R7000 modem. I have the new Rogers CODA-4582 White tower that's been set up in Bridge mode.
Can anyone from Rogers look into this for me, or anyone get similar issues on their lines?
Just got .23 pushed down to me so that is something exciting for a Friday afternoon.
With the modem rebooting due to the software upgrade I am now missing ports 17- 24 so that leads me to believe my modem has begun to suffer from the interference issue and will need to be replaced by a black dot modem.
Quick speed tests give an approximate 650/45 over Wifi so that is also a positive.
*Update* - Did a full powerdown of the network devices after the software upgrade and the missing ports came back and everything is back in order. Speedtests give 720/45 over wired (highest I ever get is in the 720-750 range so its back to normal speed) with ping/jitter being 6 and 6 respectively. Will keep an eye on the channels for possible modem issues but positive initial results!
@Hybrid_Noodle, might have to wait until tonight's change window to factory reset
I just got .23 as well. I'll have to reboot the pfSense box tomorrow morning when everyone is asleep.
@RogersDave, here's my results on 100u bridged (did not do any factory reset - it just rebooted after the SW load);
|18||01/27/2017 19:15:59||69010100||notice||SW Download INIT - Via NMS|
|19||01/27/2017 19:16:47||69011100||notice||SW download Successful - Via NMS|
|20||01/27/2017 19:19:06||90000000||warning||MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=a8:4e:3f:xx:yy:zz;CMTS-MAC=00:17:10:xx:yy:zz;CM-QOS=1.1;CM-VER=3.1;|