*** 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*
@toolcubed wrote:
By the way, what's the hardware version of the CODAs with the black dot?
There is no difference in the hardware revision number. It is strictly a printed mark on the modem.
@RogersDave Just installed my new CODA-4582 Black Dot version with the default firmware. I sent you a PM with my info so when you have time can you send me the .20 firmware or newer please.
© 2017 Hitron Technologies Inc.. All rights reserved.
My speeds are low once again. 250/20
| Hardware Version | 1A |
| Software Version | 2.0.10.13 |
Downstream Overview
| Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
| 1 | 591000000 | 256QAM | 7.800 | 31 | 38.983 |
| 2 | 363000000 | 256QAM | 4.900 | 10 | 40.946 |
| 3 | 369000000 | 256QAM | 5.400 | 11 | 40.366 |
| 4 | 375000000 | 256QAM | 5.200 | 12 | 40.366 |
| 5 | 381000000 | 256QAM | 4.400 | 13 | 40.366 |
| 6 | 387000000 | 256QAM | 5.000 | 14 | 38.983 |
| 7 | 393000000 | 256QAM | 5.300 | 15 | 40.366 |
| 8 | 399000000 | 256QAM | 6.000 | 16 | 40.366 |
| 9 | 405000000 | 256QAM | 6.100 | 17 | 40.366 |
| 10 | 411000000 | 256QAM | 6.300 | 18 | 40.366 |
| 11 | 417000000 | 256QAM | 6.700 | 19 | 40.946 |
| 12 | 423000000 | 256QAM | 7.000 | 20 | 40.366 |
| 13 | 429000000 | 256QAM | 6.700 | 21 | 40.366 |
| 14 | 435000000 | 256QAM | 6.300 | 22 | 40.366 |
| 15 | 441000000 | 256QAM | 6.000 | 23 | 38.983 |
| 16 | 447000000 | 256QAM | 6.200 | 24 | 40.366 |
| 17 | 555000000 | 256QAM | 8.000 | 25 | 40.366 |
| 18 | 561000000 | 256QAM | 8.500 | 26 | 40.946 |
| 19 | 567000000 | 256QAM | 8.300 | 27 | 40.366 |
| 20 | 573000000 | 256QAM | 8.500 | 28 | 40.946 |
| 21 | 579000000 | 256QAM | 8.300 | 29 | 40.366 |
| 22 | 585000000 | 256QAM | 8.300 | 30 | 40.366 |
| 23 | 357000000 | 256QAM | 4.800 | 9 | 40.946 |
| 24 | 597000000 | 256QAM | 7.500 | 32 | 38.983 |
| 25 | 603000000 | 256QAM | 8.200 | 33 | 38.983 |
| 26 | 609000000 | 256QAM | 8.900 | 34 | 38.983 |
| 27 | 615000000 | 256QAM | 9.300 | 35 | 40.366 |
| 28 | 621000000 | 256QAM | 9.500 | 36 | 40.366 |
| 29 | 633000000 | 256QAM | 9.200 | 37 | 38.983 |
| 30 | 639000000 | 256QAM | 8.100 | 38 | 38.605 |
| 31 | 645000000 | 256QAM | 7.300 | 39 | 38.605 |
| 32 | 651000000 | 256QAM | 6.800 | 40 | 38.605 |
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 |
Upstream Overview
| Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
| 1 | 23700000 | ATDMA - 64QAM | 40.250 | 2 | 6400000 |
| 2 | 38596000 | ATDMA - 64QAM | 43.500 | 3 | 3200000 |
| 3 | 30596000 | ATDMA - 64QAM | 41.500 | 1 | 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 |
Thanks,
Daniel
Getting bad latency to the second hop when pinging google. If you could please look into this that would be great. Currently on the CODA with firmware version 2.0.10.20. Below are my signal levels and pingplotter showing the latency spikes.
Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 591000000 256QAM 4.300 31 40.946
2 363000000 256QAM 0.500 10 37.356
3 369000000 256QAM 0.600 11 37.636
4 375000000 256QAM 0.500 12 37.636
5 381000000 256QAM 0.200 13 37.636
6 387000000 256QAM 0.400 14 37.356
7 393000000 256QAM 1.500 15 37.636
8 399000000 256QAM 1.700 16 37.636
9 405000000 256QAM 1.700 17 38.983
10 411000000 256QAM 1.700 18 38.605
11 417000000 256QAM 1.900 19 38.605
12 423000000 256QAM 2.100 20 38.605
13 429000000 256QAM 2.200 21 38.605
14 435000000 256QAM 2.400 22 38.983
15 441000000 256QAM 2.900 23 38.983
16 447000000 256QAM 2.600 24 38.605
17 555000000 256QAM 3.700 25 38.605
18 561000000 256QAM 2.800 26 38.983
19 567000000 256QAM 2.700 27 38.983
20 573000000 256QAM 2.800 28 38.605
21 579000000 256QAM 3.200 29 38.983
22 585000000 256QAM 3.600 30 38.983
23 357000000 256QAM 0.100 9 37.636
24 597000000 256QAM 3.900 32 40.366
25 603000000 256QAM 3.400 33 38.983
26 609000000 256QAM 3.000 34 38.983
27 615000000 256QAM 3.400 35 38.983
28 621000000 256QAM 3.900 36 40.366
29 633000000 256QAM 4.600 37 40.366
30 639000000 256QAM 4.600 38 40.366
31 645000000 256QAM 4.700 39 40.366
32 651000000 256QAM 5.200 40 40.366
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
Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth
1 30596000 ATDMA - 64QAM 30.250 1 6400000
2 38595727 ATDMA - 64QAM 33.500 3 3200000
3 23700000 ATDMA - 64QAM 30.000 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
@VivienM wrote:
@StephKitty wrote:@RogersDave Will upgrading to 2.0.10.20 enable ipv6?
On a similar note, you mention that you are working on enabling ipv6 in the next 2 weeks, will this be tunneled or native IPV6?
I would really like to get that working on my network.It's presumably the same native IPv6 that's working for users of the CGN2/CGN3-family gateways right now.
@RogersDave hasn't been too specific on the details, but it seems there's a big IPv6-related bug in the earlier firmware versions, and so, to avoid triggering that bug, they've disabled IPv6 for the 4582 for now. Even though the newer firmware versions fix it... they're still worried that someone who picks up a 4582 with .13 would encounter the bug for a day or two until the modem is automagically updated to the fixed firmware. I don't think you're the only one who misses the IPv6 that they had with their CGN3-family modems...
Spot on! What we are trying to do now is make the automagic happen as soon as the modem gets registers on the network.
Dave
@Eniex wrote:Getting bad latency to the second hop when pinging google. If you could please look into this that would be great. Currently on the CODA with firmware version 2.0.10.20. Below are my signal levels and pingplotter showing the latency spikes.
Packet loss to modem and bad latency to second hop are closely related to the ICMP with short TTL issues. This is being addressed in 2.0.10.21 or 2.0.10.22.
It doesn't line up however with your overall latency to the last hop that is much shorter so it's more a cosmetic issue in that case than a real problem but it will get fixed.
Dave
-
504185 views
-
295 Likes
-
-
