cancel
Showing results for 
Search instead for 
Did you mean: 

CODA-4582 - Open Issues for Investigation

RogersDave
Retired Support
Retired Support

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

2,620 REPLIES 2,620

Re: CODA-4582 - Open Issues for Investigation

RyzenFX
I'm a reliable contributor

I've noticed this same trend after the modem is pushed a new firmware version. At first, the modem performs really well (notably in gaming scenarios where ping and packet loss is very low), however after some time there seems to be a buildup of packet loss and ping. 

Re: CODA-4582 - Open Issues for Investigation

bhaskarp
I plan to stick around
also experiencing the same issue on my end

Re: CODA-4582 - Open Issues for Investigation

JohnBeaudin
I'm a senior contributor

@RyzenFX

 

Yup it happenned to me with previous firmwares as well.. then as soon as the it build latency even if I reboot or do what I want it will stay laggy now, so I guess only the UDP fix will save us.

Re: CODA-4582 - Open Issues for Investigation

JohnBeaudin
I'm a senior contributor

LAN Up time 10h, looks like my modem rebooted on it's own even on the new beta .26 firmware.

Re: CODA-4582 - Open Issues for Investigation

Triple_Helix
I plan to stick around

@JohnBeaudin wrote:

LAN Up time 10h, looks like my modem rebooted on it's own even on the new beta .26 firmware.


No problem here.

 

System Information

This menu displays general information of the device

Hardware Version1A
Software Version2.0.10.26T1
Gateway Serial Number 
HFC MAC Address 
System TimeSat, 18 Mar 2017 15:23:18
Time ZoneUTC-05:00 Colombia, Eastern Time, Indiana(East)
LAN Up Time001 days 03h:15m:16s

 

Re: CODA-4582 - Open Issues for Investigation

RyzenFX
I'm a reliable contributor

@Triple_Helix How many devices do you have connected to the modem?

Re: CODA-4582 - Open Issues for Investigation

Triple_Helix
I plan to stick around

@RyzenFX wrote:

@Triple_Helix How many devices do you have connected to the modem?


8 but not all on at the same time. I would say 5 connected all the time when we are home. At least my Moto Z Phone doesn't drop it's 5G connection anymore!

Re: CODA-4582 - Open Issues for Investigation

RyzenFX
I'm a reliable contributor

@JohnBeaudin How many devices do you have connected to the modem?

Re: CODA-4582 - Open Issues for Investigation

JohnBeaudin
I'm a senior contributor

@RyzenFX

 

10-11 devices.

Re: CODA-4582 - Open Issues for Investigation

RyzenFX
I'm a reliable contributor

@JohnBeaudin Dave said that reboot issue affects people with 10 or more devices connected to the modem, however @Triple_Helix is not affected by the problem and only has 8 devices connected to the modem.

 

@RogersDave Could the reboot issue still be present despite the fix that was implemented?

 

Re: CODA-4582 - Open Issues for Investigation

JohnBeaudin
I'm a senior contributor

I can live with the reboots.. what I can't live with is the high ping!, so my hope is in the next UDP firmware fix.

 

Also I am still on D.30 but I think I should get 3.1 next week, It should not have impact on reboots bot some people said that 3.1 reduced their latency so I can't wait to test it.

Re: CODA-4582 - Open Issues for Investigation

Not true j had 3.1 and still had latency

Re: CODA-4582 - Open Issues for Investigation

RyzenFX
I'm a reliable contributor

@lethalsniper You're affected by serious upstream node congestion which, as a result increases your latency in general. 

 

When I was on the CODA-4582 with D3.1, my latency decreased a good amount. You can notice this latency drop when you compare speedtests of D3.0 results to D3.1 results. Once D3.1 upstream is enabled, we can see latency decrease a tad bit more.

Re: CODA-4582 - Open Issues for Investigation

Bond007
I plan to stick around
My modem is not getting .26 update. I have rebooted the modem 2 twice yesterday.

Please advise

Re: CODA-4582 - Open Issues for Investigation

Vikentieff
I plan to stick around

I had noticed that my modem got .26T1 and went to do the regular factory reset via the admin panel, and when the modem finally rebooted it reversed back to .24

 

What is going on?!

Re: CODA-4582 - Open Issues for Investigation

MegnaGaming
I plan to stick around

@Vikentieff wrote:

I had noticed that my modem got .26T1 and went to do the regular factory reset via the admin panel, and when the modem finally rebooted it reversed back to .24

 

What is going on?!


@Vikentieff - you missed a post earlier where @RogersDave said that a factory reset removes the block for firmware updates and you'll end up reverting back to .24

 

You may need to wait on a manual fix now.

Re: CODA-4582 - Open Issues for Investigation

Triple_Helix
I plan to stick around

Still no auto reboot!

 

System Information

This menu displays general information of the device

Hardware Version1A
Software Version2.0.10.26T1
Gateway Serial Number 
HFC MAC Address 
System TimeSun, 19 Mar 2017 08:03:08
Time ZoneUTC-05:00 Colombia, Eastern Time, Indiana(East)
LAN Up Time001 days 19h:55m:05s

 

 

 

Image and video hosting by TinyPic

Re: CODA-4582 - Open Issues for Investigation


@Bond007 wrote:
My modem is not getting .26 update. I have rebooted the modem 2 twice yesterday.

Please advise

I just pushed it to your modem.

 


@Vikentieff wrote:

I had noticed that my modem got .26T1 and went to do the regular factory reset via the admin panel, and when the modem finally rebooted it reversed back to .24

 

What is going on?!


Just repushed it to your modem. As stated, if you factory reset, your modem will revert to .24.

 

 Dave

Re: CODA-4582 - Open Issues for Investigation

JohnBeaudin
I'm a senior contributor

Feelsgood to have the forum back.

 

The reboot seems to be gone now on .26, my modem is no longer rebooting on it's own for the past few days.

Re: CODA-4582 - Open Issues for Investigation

Mike2011
I plan to stick around

@RogersDave

 

I checked this morning and I'm still on .24 firmware.

 

Is there something special that needs to be done to obtain the .26 ?

Re: CODA-4582 - Open Issues for Investigation

JohnBeaudin
I'm a senior contributor

For those of you who got D3.1 enabled, do you remember what time it got enabled (late at night perhaps?)?