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]

@JohnBeaudin Not sure if that was to me, but, I'm not saying that the firmware can't help latency - I'm saying that the problem that we had, or at least as I experienced it, wasn't about latency.

My pings to google before, even when the connection was sub-megabit, were always in the 8-12ms range. After the firmware update, still. Actually, with this beta firmware, the pings are more erratic and are in the 8-25ms range now.

There may be some placebo effect, as this firmware was specifically setup to address the issue of the connection dropping out over time. Maybe it does also help other things, but off of just a couple comments here, I'm just trying to avoid people having an unrealistic expectation if that's not what the actual fix is for.

[Telek]

---

@jjunge wrote:
@RogersDave - neither hardwired device was able to get an ip - port 1 is connected to a switch which is connected to an Xbox and a computer. Port two was connected to VoIP but I disconnected it so that my calls come to my cell. I'm at work right now but will test agin when I get home

---

Have you tried manually assigning an IP? I found that the DHCP server in the modem was very slow at times, and in some cases actually failed to give out an IP.  Manually assigning it fixed it for me at least.

[Jeffj]

---

@Telek wrote:

---

@Jeffj wrote:

So far so good for me here. Did a bunch of Streaming with Beam.pro last night. Their new FTL protocol allows for latency free streaming and my connection did not let me down. I was able to maintain a 60fps 1080p Stream with latencts sub second to my viewers.

---

What did you see before?

That protocol, IIRC, seems to be anywhere between 8-12mbit. As long as your connection is up, there shouldn't have ever been any issues?  At least what I've been seing before the upload was never affected, it was the download that dropped out.

---

I have no comparison on Beam for a before. But on twitch i would see Intermitant issues streaming where my stream quality would plummet and stop streaming on a regular basis.  This is more so due to the Actual speed degridation and channel loss issues I had(?) then latency. But on twitch my latency to streamer would start at 10 seconds and creep up to almost 30.

[RogersDave]

Feedback is still limited but I'm willing to push it to customers requesting it (part of the firmware trial program).

I've just pushed the firmware to @adadadadgw, @Mayoo, @timfolkins, @JohnBeaudin, @Bond007.

@toolcubed, I'm trying to push it to you but having a hard time reaching your modem. I'll try again shortly.

Dave

[JohnBeaudin]

@RogersDave

Got it, speed is good but I can't reach 192.168.0.1 , I will try to reboot and factory reset to see if it fix it, otherwise I will get back to you.

[Jeffj]

---

@RogersDave wrote:

Feedback is still limited but I'm willing to push it to customers requesting it (part of the firmware trial program).

I've just pushed the firmware to @adadadadgw, @Mayoo, @timfolkins, @JohnBeaudin, @Bond007.

@toolcubed, I'm trying to push it to you but having a hard time reaching your modem. I'll try again shortly.

Dave

---

I need to pull about 50 GB through my work VPN to my home server for backup.

I'll keep you posted if i murder it.  lol

[Bond007]

Many thanks - I shall keep everyone informed of my experience. 

Also, would like to thank everyone for working diligently on this issue to a swift resolution. Looking forward further updates. 

[Triple_Helix]

---

@RogersDave wrote:

Feedback is still limited but I'm willing to push it to customers requesting it (part of the firmware trial program).

I've just pushed the firmware to @adadadadgw, @Mayoo, @timfolkins, @JohnBeaudin, @Bond007.

@toolcubed, I'm trying to push it to you but having a hard time reaching your modem. I'll try again shortly.

Dave

---

@RogersDave You can add me as well please! 

[pacerdjl]

@RogersDave Almost 19 hours with the revised .23 firmware. Still maintaining up and down speeds!! Just tested - 332 down, 22 up, 13ms latency, 3ms jitter (Rogers Speed Check). We might have a winner (at least for the speed degradation issue)!!

[tonytoronto]

    @RogersDave  you can push it to my modem if you like.   thanks

[Mayoo]

---

@RogersDave wrote:

Feedback is still limited but I'm willing to push it to customers requesting it (part of the firmware trial program).

I've just pushed the firmware to @adadadadgw, @Mayoo, @timfolkins, @JohnBeaudin, @Bond007.

@toolcubed, I'm trying to push it to you but having a hard time reaching your modem. I'll try again shortly.

Dave

---

Happy camper here. Ping times came down alot 

My setup 

Bridge Mode to Asus RT-87U

[RogersDave]

---

@Triple_Helix wrote:

@RogersDave You can add me as well please! 

---

 Done.

@toolcubed, you should have it as well.

Dave

[JohnBeaudin]

@RogersDave

all is good now I can reach the modem.

I will run some tests and update you later today after I am done working.

[toolcubed]

Thanks!  I think I know why you were having a hard time reaching my modem the first time.  My modem froze completely and when I rebooted, I noticed the downstream light was cyan (it was blue before it froze)...so looks like your first attempt at the firmware push coincided with Docsis 3.1 getting enabled!  Modem rebooted on its own shortly after I rebooted it myself, so looks like the firmware push worked.  I'm happy...I now have the new firmware AND D3.1 🙂 🙂 🙂 🙂  Thanks again @RogersDave!

[lyricidal]

I too would gladly give it a try as well. Should have some time to mess around this evening. Thank you!

[kibosh]

Thanks @RogersDave, just got the revised .23.  It can't be coincidental that this enabled DOCSIS 3.1 for me either can it?!?!? Other people are reporting the same thing so did something else change in this version?

Thanks again! 

Kibosh

[Mayoo]

I dont know why my post is keep getting deleted .. 

I want to post that i am on .23 Revised FIrmware and getting good speeds with 4ms ping times .. 

Admin please at least DM if you delete my posts.. I am just trying to provide feedback to @RogersDave

[Jeffj]

---

@toolcubed wrote:

@Thanks!  I think I know why you were having a hard time reaching my modem the first time.  My modem froze completely and when I rebooted, I noticed the downstream light was cyan (it was blue before it froze)...so looks like your first attempt at the firmware push coincided with Docsis 3.1 getting enabled!  Modem rebooted on its own shortly after I rebooted it myself, so looks like the firmware push worked.  I'm happy...I now have the new firmware AND D3.1 🙂 🙂 🙂 🙂  Thanks again @RogersDave!

---

Jealous here

[Bond007]

@RogersDave - After the new .23 FW pushed the modem is not running on DOCSIS 3.1. Both upload and download light are blue and not purple.

Also, my ping time are high between 30 - 38ms and at time could be higher.

Any thoughts? 

[Triple_Helix]

@RogersDave one small bug to report and I'm not sure if others see this? .23 version 1 and .23 version 2 have the same issue for me? I don't make any changes but when I click on Device Reset it's always asking to save things?

[Hybrid_Noodle]

@RogersDave while I am not running into the slowdown issue I am willing to test the new firmware. If you are limiting it to the individuals who have seen slowdowns I can wait until it gets released to the standard Beta participants.