*** 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*
@ishine80 do you have anything that is connected via ethernet to one of the ethernet ports at the back of the modem? Does your laptop have an ethernet port that you can use for test purposes? I suspect that you lose all connectivity from the modem, ethernet and wifi, but it would be good to ensure that the ethernet connection would also be affected. All depends on whether or not you can connect to the modem via ethernet.
Hello Community!
I'm sorry it has been a little while since my last visit (5 full pages in this thread) but as I said previously, from time to time my boss still wants me to do my real job which I have to do if I want to be able to keep said job and support all of you on the side 🙂
That being said, I read all the messages in this tread (will follow up with the other regular threads where I'm active and private messages in the next couple of hours) and picked up a few items for Hitron.
Version 2.0.10.29 and 2.0.10.30T1 were initial test code of a brand new development branch. These firmwares were not as stable as I would have wanted but there was a lot more work done on it in the last 2 weeks. We have 2 new firmwares coming soon with a lot of fixes while will hopefully bring on par with the general stability of 2.0.10.27 along with the new features.
We have also broken down that was original planned in 2.0.10.30T1 in 2 different builds coming between now and the end of July. The first one will include some of the DFS and band steering changes while the second will focus on WiFi speed improvement.
Given the comments in here, I will definitely re-run all my latency tests on these new versions and compare with 2.0.10.27.
@Max24, noted you have a speed issue and will look into it.
@RyzenFX, OFDM loss (I think it's a localized problem). Did you make any progress with this issue?
@ishine80, I understand that you have intermittent connectivity issue. Will wait for the hardwired test to troubleshoot further.
Dave
@Raptor2148, personal opinion, I'd recommend running a factory reset on the router. That usually clears up problems when you switch modems from one ISP to another ISP. Also look at your DNS settings in the router. If you happened to have Bell's DNS set in the router, you might want to switch them for Rogers (leave the fields empty) or use Google or OpenDNS for example.
Can you also log into the modem and confirm which firmware version is loaded? Its listed as the Software Version on the Status page. That page comes up automatically when you log into the modem.
Also take note, Bell does not use IPV6. Rogers uses Native IPV6, so, if you happened to have IPV6 enabled in your router, using anything other than Native IPV6, you will have to reset the IPV6 type and change the remaining settings. Here are the IPV6 settings for the 68U, which I also run:
Connection type NATIVE
DHCP-PD Enable
IPv6 LAN Setting
LAN IPv6 Address No entry this will fill in on its own after a router reboot where the router negotiates
with the CMTS.
LAN Prefix Length No entry this will fill in on its own after a router reboot where the router negotiates
with the CMTS.
LAN IPv6 Prefix No entry this will fill in on its own after a router reboot where the router negotiates
with the CMTS.
Auto Configuration Setting Stateless / Stateful I've tested both in the past and prefer to run stateful
as it offers more protection for IPV6 operations
IPv6 DNS Setting
Connect to DNS Server automatically Disable If this is enabled the router and connected devices
will use Rogers IPV6 DNS
IPv6 DNS Server 1 2620:0:ccc::2 (OpenDNS)
IPv6 DNS Server 2 2620:0:ccd::2 (OpenDNS)
IPv6 DNS Server 3 2001:4860:4860:0:0:0:0:8888 (Google)
Auto Configuration Setting
Enable Router Advertisement Enable
@ishine80 can you tell me which SSID is yours? When the ethernet and wifi goes down on the modem, you shouldn't be able to stream video on that other cell phone unless that phone is only using IPV4 for example, or, if the phone is connected to someone else's open wifi network. The fact that you lose the ethernet connections should indicate that the modem can't supply either ethernet or wifi networks. That's my current thinking about this. The only other possibility is that this is an IPV4/IPV6 issue, but, I'll have to reread your previous comments to see if you have IPV6 disabled. If so, then this is a modem to CMTS connection issue.
Community,
Quick update for everybody. I just pushed code 2.0.10.31 to some of you. Based on feedback, I will continue deployment in the coming days (and will resume firmware upgrades for new participants as well).
Code 2.0.10.31 on CODA is the same as 2.0.10.29 with the following changes:
- Band steering is visible in GUI (advanced WiFi 2.4 GHz and 5 GHz)
- DFS is visible in GUI (advanced WiFi 5GHz)
- Available DFS channel list updated
- USB function control displayed in gateway function GUI
Dave
-
496422 views
-
295 Likes
-
-
