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*

[Datalink]

If you have .24 loaded, you should probably only need a modem restart/reboot.  Pull the power, wait for 30 seconds and plug it back in.  If you log into the modem after the restart, you should see both IPV4 and IPV6 addresses in the upper right hand corner which is the WAN Address.

If you have a previous firmware version loaded, the reboot should probably result in an immediate firmware update, after which you should restart/reboot the modem after its update has completed.

If you have less than 19/20, that most likely means that you have to add an IPV6 exemption to the Windows firewall rules, and possibly to the Antivirus Firewall as well.  

Note that a score of 20/20 is bogus as Rogers does not supply an IPV6 hostname.  The best score that you should see is 19/20.

[Jeffj]

---

@Datalink wrote:

If you have .24 loaded, you should probably only need a modem restart/reboot.  Pull the power, wait for 30 seconds and plug it back in.  If you log into the modem after the restart, you should see both IPV4 and IPV6 addresses in the upper right hand corner which is the WAN Address.

If you have a previous firmware version loaded, the reboot should probably result in an immediate firmware update, after which you should restart/reboot the modem after its update has completed.

If you have less than 19/20, that most likely means that you have to add an IPV6 exemption to the Windows firewall rules, and possibly to the Antivirus Firewall as well.  

Note that a score of 20/20 is bogus as Rogers does not supply an IPV6 hostname.  The best score that you should see is 19/20.

---

Tested again 19/20 oh well lol 

[prateeck7]

My ICMP is filtered...What do I do?

[MegnaGaming]

Hey @Datalink - I tried the factory reset and it is showing both IPV4 and 6 addresses in the upper right, however I still have ICMP as "filtered" under the IPV6 test. Any ideas?

[prateeck7]

@MegnaGaming@Datalink Same here

[MegnaGaming]

I should also note that my IPV6 Firewall settings are below:

https://i.gyazo.com/11746032e8728751ff0fd39235021bfc.png

As you can see - ICMP is allowed.

[Datalink]

@MegnaGaming, @prateeck7, go into your Windows Firewall rules and add an exemption for IPV6 ICMP only.  Don't do this for IPV4.  When the exemption has been added, reboot the pc. 

There is a previous post on this subject somewhere in the forum.  Just can't find it at the moment.

[Jeffj]

in an elevated command prompt or power shell:

 netsh advfirewall firewall add rule name="All ICMP V6" dir=in action=allow protocol=icmpv6

Should work to add the rule.

[RogersDave]

I guess at this point I don't need to announce it but yes we have re-enabled IPv6 on the CODA-4582 and at the same time enabled update on boot to firmware 2.0.10.24.

This means that any new modem coming online will automatically get the new firmware. If you are on an old firmware, all you need to do is reboot your modem and your modem will get the upgrade.

Dave

[MegnaGaming]

Should I allow all ICMP types? I'm using https://technet.microsoft.com/en-us/library/cc972926(v=ws.10).aspx as a guide for setting this up.

[prateeck7]

@Datalink@JeffjThank you. It helped.

For some reason, 'like' function is not working in Rogers Community for me.

[prateeck7]

@DatalinkSo I haven't usdg google DNS with this modem. What do you recommend? And what is should be?

[MegnaGaming]

Alright, now we're getting 19/20 - awesome.

@RogersDave @CommunityHelps

I have this crazy ongoing issue however that NO ONE seems to be able to solve it.

I was fighting with Rogers for months (since Sept) and between senior techs, T2 CSR and more, the only solution we found was to move from 100/10 to 250/20. I even ended up dealing with Natasha from The Office of the President.

After running some tests here, while I no longer notice the issue while hardwired, I still get it while connected via WiFi!

Essentially every 10 minutes (exactly) there is a major latency peak followed by a double-peak 10 minutes later. Ping Plotter image below.

https://i.gyazo.com/9932f1e48b0e2fc51a37cf5e0c8ae736.png

Is it possible this is something related to the firmware? It's SO very frustrating, especially when it causes buffering, latency issues, etc.

[lethalsniper]

@Datalink or @RogersDave I'm on the .24 trial version , now if I was to swapp the modem to another coda modem will I need to message rogersdave again or will I get .24 soon as I plug in? And is there a differ from the .24 firmware we got for testing ? Thanks

[timfolkins]

@RogersDave

Did the reboot. got ipv6 - amazing and thank you.

Should I be doing anything about these downstream signal levels? the ones at the bottom are out of spec.

Downstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	645000000	256QAM	-3.600	15	37.356
2	561000000	256QAM	-3.400	2	37.636
3	567000000	256QAM	-3.700	3	37.356
4	573000000	256QAM	-3.300	4	37.636
5	579000000	256QAM	-3.200	5	37.636
6	585000000	256QAM	-2.500	6	38.605
7	591000000	256QAM	-2.500	7	38.605
8	597000000	256QAM	-2.800	8	38.605
9	603000000	256QAM	-3.000	9	37.636
10	609000000	256QAM	-3.200	10	37.636
11	615000000	256QAM	-3.100	11	37.636
12	621000000	256QAM	-2.900	12	37.636
13	633000000	256QAM	-2.700	13	37.636
14	639000000	256QAM	-3.000	14	37.636
15	555000000	256QAM	-3.100	1	37.636
16	651000000	256QAM	-4.100	16	37.356
17	657000000	256QAM	-3.800	17	37.636
18	663000000	256QAM	-3.700	18	37.636
19	669000000	256QAM	-3.900	19	37.636
20	675000000	256QAM	-4.100	20	36.610
21	681000000	256QAM	-4.500	21	36.610
22	687000000	256QAM	-4.800	22	36.610
23	693000000	256QAM	-4.900	23	36.387
24	699000000	256QAM	-5.500	24	36.387
25	705000000	256QAM	-6.200	25	35.780
26	711000000	256QAM	-6.600	26	35.780
27	717000000	256QAM	-7.100	27	35.595
28	723000000	256QAM	-7.800	28	34.926
29	825000000	256QAM	-10.300	29	33.834
30	831000000	256QAM	-11.200	30	33.487
31	837000000	256QAM	-12.000	31	32.963
32	843000000	256QAM	-13.000	32	32.321

[JohnBeaudin]

Today is a great day for the CODA community, let's see what .25 will bring us now!

[RogersDave]

---

@lethalsniper wrote:
@Datalink or @RogersDave I'm on the .24 trial version , now if I was to swapp the modem to another coda modem will I need to message rogersdave again or will I get .24 soon as I plug in? And is there a differ from the .24 firmware we got for testing ? Thanks

---

As soon as you plug it in, your modem will download the latest firmware version 2.0.10.24. Also, there are no difference between the trial version distributed last week and the production version.

Dave

[Double_K]

---

@RogersDave wrote:

I guess at this point I don't need to announce it but yes we have re-enabled IPv6 on the CODA-4582 and at the same time enabled update on boot to firmware 2.0.10.24.

This means that any new modem coming online will automatically get the new firmware. If you are on an old firmware, all you need to do is reboot your modem and your modem will get the upgrade.

Dave

---

Thanks Dave!

[Aduly1998]

@RogersDave can you quickly reply to my private message. Thanks.

[Telek]

---

@prateeck7 wrote:

@Datalink@JeffjThank you. It helped.

For some reason, 'like' function is not working in Rogers Community for me.

---

It's because these forums have a strange timeout system where after some short period you're half logged out. You can't like, and if you try to reply it'll ask you to login again. After logging in you can like again. However it still shows you as logged in normally until you actually try to do something, and it remembers where you left off, etc.

[Telek]

---

@JohnBeaudin wrote:

Today is a great day for the CODA community, let's see what .25 will bring us now!

---

I'm so firmly in the "if it ain't broke don't fix it" camp right now ^_^