*** 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 184.108.40.206 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).
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 220.127.116.11 but more likely in 18.104.22.168 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 22.214.171.124
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 126.96.36.199
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 188.8.131.52T2
List of connected device does not get fully populated
This is a known issue that has been tracked since firmware 184.108.40.206. 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 220.127.116.11T2 (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 18.104.22.168T2
Missing SC-QAM Channels
After a reboot, some modems are missing SC-QAM channels. A fix has been implemented in 22.214.171.124T2 to address this behavior but it has not corrected all scenarios.
Investigation continues with Hitron.
The WiFi Survey functionality in firmware 126.96.36.199T2 (and possibly before) reports incorrect SSID names.
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 188.8.131.52T2.
Update April 22: This issue has been resolved in firmware 184.108.40.206
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.
I have 220.127.116.11
Okay, so the fix I was thinking about is in .20 (I just checked @RogersDave's revision history). So I guess the solution is to contact @CommunityHelps to join the trial program (which will get you .23)?
Alternately, you could consider upgrading to a gigabit switch. I'm not sure which Rogers plan you're on and what devices are connected to this 10/100 switch, so it's hard to say whether you would benefit, but 5-8 port gigabit switches are very cheap these days...
What is the difference between a black dot or non black dot 4582. A roger Live Chat rep asked me, but never mentioned why. I do not have the back dot version.
The black dot versions are supposed to have improved shielding to address an interference issue with 2.4GHz wifi. Some people are affected more than others by that interference issue...
According to the rep at the Rogers store, there were 3 updates of the CODA modem:
First one was the new modem itself
Second one was one that had a black dot which indicated additional shielding on the tuner against interference
The third (current) one is the same as the second and these ones have been TESTED by Rogers techs.
I am not sure how accurate the rep was as there must be TONS of these modem going about and getting @RogersDave and others to test each one seems unlikely.
I have jus upgraded my modem to the coda 4582 I have noticed that when I log into the interface and try to bring up my connected devices only the devices connected to the ethernet ports will show up and none of the wifi connected devices ever do. I require the list to fully populate so that I may choice certain devices to have restricted access at a givin time. Please help.
Hi @v_claro81, what you are experiencing when you don't see any of your WiFi devices is definitely a bug. To have this bug fixed, you're going to need to join the firmware trial for the CODA-4582. Or, you can choose to wait untill March which is when the bug will be fixed in a major update that will be deployed in early March. This update will be deployed to all non-firmware trial customers.
If you don't want to wait, please send a private message to @CommunityHelps with the title "Rogers Rocket Wi-Fi Modem Firmware Trial" Please let them know that you want to join the firmware trial with your CODA-4582 and include the MAC address of the modem which is located behind the modem on the product sticker.
Interesting weekend on the network as multiple reports of reboots on Saturday, Sunday and Monday night around midnight. (Mine went Saturday and Monday). People I spoke with did not have DOCSIS upgrades completed and there were no other changes that appeard on the devices. Will make the assumption that they were doing upgrades on the rest of the environment but who knows.
Sadly looks like I lost channel 18 again this morning for my modem but otherwise things appear to be fine here.
I wasnt home all weekend, cam home modem was fine speeds werefine, but then this morning again lost channel 13. So it appears when the modem is put under load whne people areu sing it i lose channels and get poor speed. Still thinking this is fimrware, but with no feedback from @RogersDave yet I'm desperate enough to have my modem swapped out before he has a chance to investigat because this is getting silly lol
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 639000000 256QAM -3.900 38 33.487
2 657000000 256QAM -3.800 41 33.063
3 663000000 256QAM -3.800 42 32.963
4 669000000 256QAM -3.700 43 33.487
5 675000000 256QAM -3.900 44 33.487
6 681000000 256QAM -4.000 45 32.963
7 687000000 256QAM -4.100 46 33.377
8 693000000 256QAM -4.300 47 32.963
9 699000000 256QAM -4.800 48 32.963
10 705000000 256QAM -4.700 49 32.963
11 711000000 256QAM -5.200 50 32.676
12 717000000 256QAM -5.000 51 32.865
14 825000000 256QAM -6.400 53 32.321
15 831000000 256QAM -6.300 54 32.676
16 837000000 256QAM -6.700 55 32.237
17 843000000 256QAM -7.100 56 31.994
18 849000000 256QAM -7.100 57 31.994
19 567000000 256QAM -3.900 27 33.377
20 573000000 256QAM -3.800 28 33.377
21 579000000 256QAM -4.000 29 33.377
22 585000000 256QAM -4.100 30 33.063
23 591000000 256QAM -3.900 31 33.487
24 855000000 256QAM -7.800 58 31.689
25 603000000 256QAM -4.300 33 33.377
26 609000000 256QAM -4.400 34 33.377
27 615000000 256QAM -4.100 35 33.377
28 621000000 256QAM -3.900 36 33.487
29 633000000 256QAM -3.700 37 33.377
30 861000000 256QAM -7.300 59 31.915
31 645000000 256QAM -3.700 39 33.487
32 651000000 256QAM -3.700 40 33.377
OFDM Downstream Overview
Receiver FFT type Subcarr 0 Frequency(MHz) PLC locked NCP locked MDC1 locked PLC power(dBmv)
0 NA NA NO NO NO NA
1 NA NA NO NO NO NA
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth
1 30596000 ATDMA - 64QAM 31.250 1 6400000
2 38595766 ATDMA - 64QAM 33.000 3 3200000
3 23700000 ATDMA - 64QAM 30.250 2 6400000
Does the CODA-4582 have any issues with load balancing? I was speaking to a Rogers rep and he said this may be why I experience latency spikes on League of legends. Everytime I power cycle my modem my ping is solid but after a while it starts spiking again until I restart the modem.
I've seen my internet speeds slow to a crawl on this modem lately. I got this device ad the beginning of January. Last week or two, seen speeds decrease at time randomly down to 1Mbps on my gigabit connection. A modem reset solves this but its a little ridiculous that i would have to do a modem reset every coule of days. Is there a solution to this?
My issue from before has returned. The black dot CODA only seems to have fixed the problem for a day or so before things went down hill again.
TODAY, after getting increasingly bad for around 7 minutes, the connection just fizzled out completely around 3:55 for maybe 75-80 minutes. (see attached)
I've had two techs over, neither found fault with anything inside the house after switching all of the connectors and the splitter. Neither actually tested the connection on their laptop though.
This is beyond frustrating, and I'm growing very tired of paying for a connection that I can't use. I need some reassurance that these problems will be resolved at some point very soon.
Lastly, my most recent problems seem to coincide w/ DOCSIS 3.1 going (partially?) live in my neighbourhood. I had 0 issued w/ the non-dot modem before the cyan light showed up and the management panel stating that I now had an OFDM downstream.