CODA-4582 - Open Issues for Investigation

[RogersDave]

*** 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*

[Telek]

I tried that already. They told me that, pretty much, all of the 3552 modems have been yanked. No store within 50km of me has one, and the techs don't carry them anymore.

[lethalsniper]

i,m having the  same issue as you on coda modem with black sticker .23 with MDD timeouts

1 591000000 256QAM 6.300 7 40.366
2 567000000 256QAM 6.300 3 40.366
3 573000000 256QAM 5.900 4 38.983
4 579000000 256QAM 6.000 5 38.983
5 585000000 256QAM 6.400 6 40.366
6 561000000 256QAM 6.500 2 40.366
7 597000000 256QAM 6.300 8 38.983
8 603000000 256QAM 6.600 9 40.366
9 609000000 256QAM 6.800 10 38.983
10 615000000 256QAM 6.900 11 38.983
11 621000000 256QAM 7.100 12 40.366
12 633000000 256QAM 6.800 13 40.366
13 639000000 256QAM 7.100 14 38.983
14 645000000 256QAM 7.200 15 38.983
15 651000000 256QAM 7.200 16 38.983
16 657000000 256QAM 7.200 17 40.366
17 663000000 256QAM 6.900 18 38.605
18 669000000 256QAM 7.400 19 38.983
19 675000000 256QAM 7.200 20 38.983
20 681000000 256QAM 6.700 21 38.605
21 687000000 256QAM 6.500 22 38.983
22 693000000 256QAM 6.200 23 38.983
23 699000000 256QAM 6.300 24 38.605
24 705000000 256QAM 6.300 25 38.605
25 711000000 256QAM 5.900 26 38.605
26 717000000 256QAM 5.800 27 38.605
27 723000000 256QAM 5.800 28 38.983
28 825000000 256QAM 5.200 29 37.636
29 831000000 256QAM 4.900 30 37.356
30 837000000 256QAM 4.600 31 37.356
31 843000000 256QAM 5.000 32 37.356
32 555000000 256QAM 6.700 1 38.983

OFDM Downstream Overview
Receiver FFT type Subcarr 0 Frequency(MHz) PLC locked NCP locked MDC1 locked PLC power(dBmv)
0 4K 275600000 YES YES YES 3.700001
1 NA NA NO NO NO NA

Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth
1 30596000 ATDMA - 64QAM 34.250 1 6400000
2 38595824 ATDMA - 64QAM 38.000 3 3200000
3 23700000 ATDMA - 64QAM 33.500 2 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

[soundwave80]

@Telek thats a shame Rogers pulled the only somewhat stable modem from their network. Ive read on other fourms people have had decent speeds disabling the 2.4 network and just running 5g. It might be a temporary fix . Good luck

[Telek]

Doesn't matter, I get the same problem in bridged mode and gateway mode with all wifi disabled.

[RogersDave]

Hello Community,

As I mentioned earlier this week, Intel is working with Hitron and CASA to resolve the slowly degrading speed issue. They have made some headway and provided me a new firmware today.

Now, I must warn all of you this is completely fresh off the press and this firmware did not undergo any internal testing yet.

This firmware is exactly the same as 2.0.10.23 with a change in some internal Intel settings. In fact, after I load this firmware, the GUI will still display version 2.0.10.23. If you are not experiencing this issue, there is no point in loading this firmware yet.

If anybody wants to receive this firmware (maximum 5 participants today while we perform some testing), please reply below. You must already be a firmware trial program participant. Otherwise, I won’t be able to upgrade your modem.

Dave

[Jeffj]

---

@RogersDave wrote:

Hello Community,

As I mentioned earlier this week, Intel is working with Hitron and CASA to resolve the slowly degrading speed issue. They have made some headway and provided me a new firmware today.

Now, I must warn all of you this is completely fresh off the press and this firmware did not undergo any internal testing yet.

This firmware is exactly the same as 2.0.10.23 with a change in some internal Intel settings. In fact, after I load this firmware, the GUI will still display version 2.0.10.23. If you are not experiencing this issue, there is no point in loading this firmware yet.

If anybody wants to receive this firmware (maximum 5 participants today while we perform some testing), please reply below. You must already be a firmware trial program participant. Otherwise, I won’t be able to upgrade your modem.

Dave

---

Please I need this desperatly

[Telek]

Yes please, sign me up!

[pacerdjl]

Count me in. Speed degrades frequently. pacerdjl

[jjunge]

I'll take the updated firmware Dave!!

[jjunge]

Hi all, just got the revised .23 - initial report is that the speed is very fast and very stable - no bouncing around on speed tests.... Fingers crossed that it keeps performing well!

[Bob35789]

Hi @RogersDave I would like to please participate in this beta please. Thanks in advance. I will private mesage you my detail in case.

[RogersDave]

Thanks to all for quick responses.

I've pushed the firmware to @Jeffj, @Telek, @pacerdjl, @jjunge, @Bob35789

Let me know how it goes. Hopefully I will have enough feedback on this firmware by Friday to roll it out to all participants.

Dave

[Bob35789]

Hi @RogersDave my download speed is now sitting at about 60 Mbps insted of 250Mbps...

[pacerdjl]

Dave, will push the 4582 tonight and tomorrow. So far, good speeds, decent latency, jitter. Feedback on this thread or "FEEDBACK..." thread?

[BS]

I wonder if Rogers is starting to learn yet, that in their attempts to keep up with their competitors products in cable and Internet, that the chip makers, modem producers, and purchaser of these devices (in this case Rogers), are pushing these out with probably every toe and finger crossed hoping it will work.

The whole industry is responsible for this one - like Navigatr and IPTV, we now see on the Internet side that Rogers with their suppliers are scrambling to figure out how to move forward, while customers bear the consequences and suffer through it all.

In the same way that it is often said for us as customers, to just move to another provider that can provide stable services, maybe Rogers should be doing the same with their suppliers.

It is killing Rogers reputation, at least for me, of being a leader in technology, and a provider of high level tech support.  I know the beta testing is highly in the open this time, and the beta testers are asking to be involved, but these same boxes are going out to the general consumer who wants to move to higher speeds.

I think someone has already taken this issue to CRTC and CCTC, I recall reading in another thread.

Taking shortcuts to get product out to the consumer in order to stay competitive with the competitors fibre is getting the company into a lot of hot water and building a lack of trust in the products.

Remember that your major competitor started on all this upgrading and implementation of high speed over fibre and IPTV 10 years ago, started small, and took their time to get it right from the beginning, and now continues to add more value to their service and technology every day.

I hope we get through this mess soon.  Probably can't go back to the old modems, because they probably aren't available, but you may be able to buy one used, if Rogers is weilling to register it to their network.

We keep trying to be patience, but patience wears thing after a while and leads to frustration, fight flight or freeze.

One other suggestion, ask for a refund on all the higher end speeds if they haven't been stable, and switch down to a 100 or 60 Mhz and ask for the unlimited - it runs very stable on my ACR.

Good luck everybody. I do feel your pain.

Bruce

[JohnBeaudin]

I never suffered from the speed issue but I hope it will be fixed, so we can focus on fixing the other isssues after.

[RogersDave]

---

@Bob35789 wrote:

Hi @RogersDave my download speed is now sitting at about 60 Mbps insted of 250Mbps...

---

You may want to reboot your modem one more time.

---

@pacerdjl wrote:
Dave, will push the 4582 tonight and tomorrow. So far, good speeds, decent latency, jitter. Feedback on this thread or "FEEDBACK..." thread?

---

Here is good. I'm trying to keep the CODA-4582 issues here and the other devices in the other thread.

Dave

[timfolkins]

@RogersDave

Looking forward to the results of your mini test. Feel free to add me to the second wave or if you want any additional guinea pigs. Cheers!

[Jeffj]

---

@jjunge wrote:
Hi all, just got the revised .23 - initial report is that the speed is very fast and very stable - no bouncing around on speed tests.... Fingers crossed that it keeps performing well!

---

I noticed this immedietly as well and my pings are lower as well.

[JohnBeaudin]

Ping lower?? OMG I WANT IN lol

[lethalsniper]

Let's hope so