*** 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*
@Triple_Helix wrote:Okay just upgraded to the Gigabit sevice so here are my first results!
Wired results!
Now this is Wireless 5g via the Hitron Modem and Killer Wireless-n/a/ac 1525 Wireless Network Adapter!
Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB) 1 591000000 256QAM 4.100 31 38.605 2 363000000 256QAM 2.100 10 40.366 3 369000000 256QAM 2.800 11 38.983 4 375000000 256QAM 2.300 12 38.983 5 381000000 256QAM 1.500 13 38.983 6 387000000 256QAM 2.000 14 38.605 7 393000000 256QAM 2.300 15 40.366 8 399000000 256QAM 2.800 16 38.983 9 405000000 256QAM 2.700 17 38.983 10 411000000 256QAM 2.700 18 40.366 11 417000000 256QAM 3.400 19 40.366 12 423000000 256QAM 3.800 20 38.983 13 429000000 256QAM 3.600 21 38.983 14 435000000 256QAM 3.000 22 40.366 15 441000000 256QAM 3.200 23 38.983 16 447000000 256QAM 3.100 24 38.605 17 555000000 256QAM 4.600 25 38.983 18 561000000 256QAM 4.800 26 38.605 19 567000000 256QAM 5.100 27 38.983 20 573000000 256QAM 4.500 28 38.983 21 579000000 256QAM 4.900 29 38.983 22 585000000 256QAM 4.400 30 38.605 23 357000000 256QAM 2.100 9 38.983 24 597000000 256QAM 3.800 32 38.605 25 603000000 256QAM 4.500 33 38.605 26 609000000 256QAM 5.600 34 38.983 27 615000000 256QAM 5.900 35 38.983 28 621000000 256QAM 6.100 36 38.983 29 633000000 256QAM 5.600 37 38.605 30 639000000 256QAM 4.900 38 38.605 31 645000000 256QAM 4.100 39 37.636 32 651000000 256QAM 3.900 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 39.750 2 6400000 2 38596000 ATDMA - 64QAM 42.750 3 3200000 3 30596000 ATDMA - 64QAM 40.750 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
@RogersDave I called Rogers tech support and they tweeked things on there end and things look much better since going to the Gigabit! Any Idea when DOCSIS 3.1 will be released in North Oshawa? This is wired of course.
This is the Max I can get Wireless via the CODA Modem/Router. Killer Wireless-n/a/ac 1525 Wireless Network Adapter! Maybe I can do better with a more advanced Router? Suggestions anyone?
Downstream Overview
| Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
| 1 | 591000000 | 256QAM | 4.200 | 31 | 38.605 |
| 2 | 363000000 | 256QAM | 1.800 | 10 | 38.983 |
| 3 | 369000000 | 256QAM | 2.500 | 11 | 38.605 |
| 4 | 375000000 | 256QAM | 2.000 | 12 | 38.605 |
| 5 | 381000000 | 256QAM | 1.300 | 13 | 38.983 |
| 6 | 387000000 | 256QAM | 1.800 | 14 | 38.605 |
| 7 | 393000000 | 256QAM | 2.100 | 15 | 40.366 |
| 8 | 399000000 | 256QAM | 2.900 | 16 | 38.983 |
| 9 | 405000000 | 256QAM | 2.900 | 17 | 40.366 |
| 10 | 411000000 | 256QAM | 2.800 | 18 | 40.366 |
| 11 | 417000000 | 256QAM | 3.200 | 19 | 38.983 |
| 12 | 423000000 | 256QAM | 3.300 | 20 | 38.605 |
| 13 | 429000000 | 256QAM | 2.900 | 21 | 38.605 |
| 14 | 435000000 | 256QAM | 2.300 | 22 | 38.983 |
| 15 | 441000000 | 256QAM | 2.600 | 23 | 38.983 |
| 16 | 447000000 | 256QAM | 2.700 | 24 | 38.983 |
| 17 | 555000000 | 256QAM | 4.600 | 25 | 38.983 |
| 18 | 561000000 | 256QAM | 4.800 | 26 | 38.983 |
| 19 | 567000000 | 256QAM | 5.200 | 27 | 38.983 |
| 20 | 573000000 | 256QAM | 4.500 | 28 | 38.983 |
| 21 | 579000000 | 256QAM | 4.900 | 29 | 38.983 |
| 22 | 585000000 | 256QAM | 4.500 | 30 | 38.983 |
| 23 | 357000000 | 256QAM | 1.800 | 9 | 38.983 |
| 24 | 597000000 | 256QAM | 4.000 | 32 | 38.605 |
| 25 | 603000000 | 256QAM | 4.700 | 33 | 38.983 |
| 26 | 609000000 | 256QAM | 5.800 | 34 | 38.983 |
| 27 | 615000000 | 256QAM | 6.000 | 35 | 38.983 |
| 28 | 621000000 | 256QAM | 6.300 | 36 | 38.605 |
| 29 | 633000000 | 256QAM | 5.800 | 37 | 38.605 |
| 30 | 639000000 | 256QAM | 4.900 | 38 | 37.636 |
| 31 | 645000000 | 256QAM | 4.200 | 39 | 37.636 |
| 32 | 651000000 | 256QAM | 4.000 | 40 | 37.636 |
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 | 39.500 | 2 | 6400000 |
| 2 | 38596000 | ATDMA - 64QAM | 42.750 | 3 | 3200000 |
| 3 | 30596000 | ATDMA - 64QAM | 40.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 |
- last edited on by
RogersPrasana
@Triple_Helix wrote:
@Triple_Helix wrote:
Okay just upgraded to the Gigabit sevice so here are my first results!
Wired results!
@RogersDave I called Rogers tech support and they tweeked things on there end and things look much better since going to the Gigabit! Any Idea when DOCSIS 3.1 will be released in North Oshawa? This is wired of course.
if that's DOCSIS3.0 then stay there for as long as you can, haha! That's about the fastest that you'll see no matter what.
What did Rogers Tech support tweak to improve your speeds? Any idea?
@Telek wrote:
@Triple_Helix wrote:
@Triple_Helix wrote:Okay just upgraded to the Gigabit sevice so here are my first results!
Wired results!
@RogersDave I called Rogers tech support and they tweeked things on there end and things look much better since going to the Gigabit! Any Idea when DOCSIS 3.1 will be released in North Oshawa? This is wired of course.
da mn, if that's DOCSIS3.0 then stay there for as long as you can, haha! That's about the fastest that you'll see no matter what.
What did Rogers Tech support tweak to improve your speeds? Any idea?
EDIT: lol ... "da mn" is apparently a swear word and is filtered by this forum.
LOL We Always want more and faster and faster! It would be nice if they would increase the upload to Gigabit speed as well. 
hi everyone, I have gigabit in the east york area
here is my speed test
I never get above 300 even in offpeak hours, not the biggest deal I'm sure they oversold it in my area.
but what I'm really concerned about is my upload stats here
notice it is modulated at 16QAM where everyone else in here gets 64QAM. should I complain to Rogers about this?
Try a couple of tests just to make sure that IPV6 is up and running:
1. Go to ipv6-test.com to check both IPV4 and IPV6 addressing and connectivity;
2. Run an IPV6 to some target like google: tracert -6 www.google.com
See if the trace runs properly past the CMTS all the way to the end target
20/20 weeee happy!
-
479020 views
-
295 Likes
-
-
