01-05-2017 11:03 AM - edited 05-02-2017 07:09 AM
*** 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.
Dave
*Edited Labels*
02-28-2017 11:59 PM
@Datalink Thank you for your response. I'm still experiencing highly variable jitter and was hoping that there was an easily identifiable cause for it. The search continues...
03-01-2017 12:17 AM - edited 03-01-2017 12:22 AM
First thing to do is restart/reboot the modem. See if that resolves the issue. After an update, the modem does reboot as part of the update cycle, but, I've found that at a minimum, another restart/reboot is required so that the modem operates as it should. I usually run a factory reset after each update, up or down.
Just to note, the response time from the modem to the CMTS ramps up significantly in the evening, and, assuming that most residential CMTSs see the same type of ramping up, you will see a base response time around 10 to 12 ms with instantaneous ranges up into the 200 ms range, all variable and unpredictable, ping to ping. For my neighborhood, I'd say that there has been a major increase in evening response times from last summer.
What you might be seeing is the normal response time from the CMTS due to the CMTS loading.
03-01-2017 12:40 AM - edited 03-01-2017 12:47 AM
yup there is something going on for sure i am experiencing a fluxating speeds along with degraded performance and Rogers denies there isnt any signal issue.. come on numbers don't lie
03-01-2017 08:41 AM - edited 03-01-2017 08:52 AM
Hi there,
I recieved the email a few weeks back to go into a Rogers store to replace the modem. I did last night and now I am unable to make a connection. The @ light is not coming on, I have rebooted the router nearly two dozen times, plugged in different coax cables in different locations in my home and nothing I do seems to be working. I even went back to the store and got another CODA-4582 modem in case the one I recieved was faulty.
I called tech support last night - they informed me a "ticket" would be created and someone would get back to me in 1-3 days. In my experience with Rogers, this usually means nothing is going to be done and I will probably be ignored.
Does anyone have a solution to this?
If Rogers reps read here, can you confirmed this is actually being looked at?
I am honestly only willing to give this until Friday at most, and then I will be cancelling my internet/TV package and switching ISPs if it is still not resolved.
Edit: Thank god my thread was moved into this one. What a wonderful use of time.
03-01-2017 09:32 AM
Got D 3.1 lastnight in North Oshawa.
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 645000000 | 256QAM | 4.200 | 15 | 37.356 |
2 | 561000000 | 256QAM | 4.700 | 2 | 38.605 |
3 | 567000000 | 256QAM | 5.100 | 3 | 38.983 |
4 | 573000000 | 256QAM | 4.400 | 4 | 38.605 |
5 | 579000000 | 256QAM | 5.200 | 5 | 38.605 |
6 | 585000000 | 256QAM | 4.500 | 6 | 37.636 |
7 | 591000000 | 256QAM | 4.200 | 7 | 37.636 |
8 | 597000000 | 256QAM | 4.000 | 8 | 37.356 |
9 | 603000000 | 256QAM | 4.600 | 9 | 37.356 |
10 | 609000000 | 256QAM | 5.700 | 10 | 38.605 |
11 | 615000000 | 256QAM | 6.300 | 11 | 38.605 |
12 | 621000000 | 256QAM | 6.300 | 12 | 37.356 |
13 | 633000000 | 256QAM | 5.900 | 13 | 37.636 |
14 | 639000000 | 256QAM | 5.400 | 14 | 37.356 |
15 | 555000000 | 256QAM | 4.400 | 1 | 38.605 |
16 | 651000000 | 256QAM | 3.700 | 16 | 37.356 |
17 | 657000000 | 256QAM | 3.700 | 17 | 37.356 |
18 | 663000000 | 256QAM | 5.300 | 18 | 37.356 |
19 | 669000000 | 256QAM | 6.200 | 19 | 36.610 |
20 | 675000000 | 256QAM | 6.300 | 20 | 36.610 |
21 | 681000000 | 256QAM | 7.600 | 21 | 36.610 |
22 | 687000000 | 256QAM | 6.700 | 22 | 36.387 |
23 | 693000000 | 256QAM | 7.300 | 23 | 37.356 |
24 | 699000000 | 256QAM | 7.000 | 24 | 37.356 |
25 | 705000000 | 256QAM | 7.000 | 25 | 37.356 |
26 | 711000000 | 256QAM | 7.100 | 26 | 37.636 |
27 | 717000000 | 256QAM | 7.400 | 27 | 37.356 |
28 | 723000000 | 256QAM | 7.600 | 28 | 37.636 |
29 | 825000000 | 256QAM | 7.600 | 29 | 36.610 |
30 | 831000000 | 256QAM | 8.200 | 30 | 37.636 |
31 | 837000000 | 256QAM | 8.600 | 31 | 36.610 |
32 | 843000000 | 256QAM | 7.600 | 32 | 36.610 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | NA | NA | NO | NO | NO | NA |
1 | 4K | 275600000 | YES | YES | YES | 2.200001 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 30596000 | ATDMA - 64QAM | 39.750 | 1 | 6400000 |
2 | 38596000 | ATDMA - 64QAM | 43.000 | 3 | 3200000 |
3 | 23700000 | ATDMA - 64QAM | 39.750 | 2 | 6400000 |
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 |
03-01-2017 11:34 AM - last edited on 03-01-2017 11:42 AM by RogersPrasana
Hello All,
Since lot of issues for CODA have been resolved I finally decided to upgrade from 3552, and guess what; I am without internet now for about 24 hours.
I called in to check what the matter is and it looks like there is some issue with provisioning. I was told yesterday around 2pm that it would take 3 hours max to fix. I still didn’t have service at 8pm and I called back again and they said by morning the issue will be definitely fixed. I wake up to find out still no internet service. I did call support again and was told it may take around 8 more hours!!! I conformed if they had correct serial on their end.
I understand if service is down for an hour for maintenance, but 24 hours? c'mon it seems like this problem is at lowest priority. I saw some other users having a similar issue and thought it would be better to start a thread. Can anyone please help us get this problem sorted?
Thanks.
03-01-2017 11:52 AM
Yes I am planning on swapping modems.
I wasn't missing any channels at all until I got onto the .19 firmware and than I noticed I had a couple channels drop occasionally.
After the .24 firmware was rolled out is when I noticed the channels of 18-25 missing.
The reason I've kept the modem for so long is I have not had any issues with speed loss or modem disconnects, other than some nights in January when we had the brief thaw after all of that sub zero weather.
03-01-2017 02:42 PM
I have to keep restarting my modem to get full speeds on the 100u is that still a problem? i have the .24 firmware
03-01-2017 02:46 PM - edited 03-01-2017 02:46 PM
I believe Dave is working on other projects this week, I have not seen him yet.
We will need to wait upon his returns to get our questions answered.
03-01-2017 03:14 PM - last edited on 03-01-2017 03:16 PM by RogersCorey
Hi , I have an ignote 100U with Rogers and was given CODA 4582 modem / router with it . it was working fine for the forst month and i have been experienceing frequent disconnect often and i could not find a way to get that working . This happens often and my wireless signal goes off for almost a minute and it comes back again . Is someone else experiencing the same ? Is there something that we could do about it ? Like a firmware upgrade or something .
Thanks ,
Savio
03-01-2017 04:27 PM - edited 03-01-2017 04:28 PM
@Triple_Helix wrote:Got D 3.1 lastnight in North Oshawa.
Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB) 1 645000000 256QAM 4.200 15 37.356 2 561000000 256QAM 4.700 2 38.605 3 567000000 256QAM 5.100 3 38.983 4 573000000 256QAM 4.400 4 38.605 5 579000000 256QAM 5.200 5 38.605 6 585000000 256QAM 4.500 6 37.636 7 591000000 256QAM 4.200 7 37.636 8 597000000 256QAM 4.000 8 37.356 9 603000000 256QAM 4.600 9 37.356 10 609000000 256QAM 5.700 10 38.605 11 615000000 256QAM 6.300 11 38.605 12 621000000 256QAM 6.300 12 37.356 13 633000000 256QAM 5.900 13 37.636 14 639000000 256QAM 5.400 14 37.356 15 555000000 256QAM 4.400 1 38.605 16 651000000 256QAM 3.700 16 37.356 17 657000000 256QAM 3.700 17 37.356 18 663000000 256QAM 5.300 18 37.356 19 669000000 256QAM 6.200 19 36.610 20 675000000 256QAM 6.300 20 36.610 21 681000000 256QAM 7.600 21 36.610 22 687000000 256QAM 6.700 22 36.387 23 693000000 256QAM 7.300 23 37.356 24 699000000 256QAM 7.000 24 37.356 25 705000000 256QAM 7.000 25 37.356 26 711000000 256QAM 7.100 26 37.636 27 717000000 256QAM 7.400 27 37.356 28 723000000 256QAM 7.600 28 37.636 29 825000000 256QAM 7.600 29 36.610 30 831000000 256QAM 8.200 30 37.636 31 837000000 256QAM 8.600 31 36.610 32 843000000 256QAM 7.600 32 36.610 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 4K 275600000 YES YES YES 2.200001 Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth 1 30596000 ATDMA - 64QAM 39.750 1 6400000 2 38596000 ATDMA - 64QAM 43.000 3 3200000 3 23700000 ATDMA - 64QAM 39.750 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
I Might have D3.1 on the Download Channel but my Upload sucks.
03-01-2017 06:14 PM
Thank you @Datalink. I have had this issue for well over a month, and have gone through a number of different CODA-4582 modems, one dot, two dot, no dots, etc. If this truly is due to the response time from modem to CMTS, is there anything that I can do, or Rogers can do to mitigate this? This is going nearly 20 years of Rogers cable and only just recently experiencing this kind of problem, I'd hate to hear that it's simply something that happens and so I just have to live with terrible connections during the times that most people want to use the internet.
I would like to be able to come home from work to enjoy some gaming or Netflix streaming or be able to VPN into work without sudden hangs and disconnections. At this point in time, it is getting harder and harder to do any of those things.
03-02-2017 08:52 AM
Any updates for March, There's a UDP fix issue for the CGN3 series.. I was wondering if you guys working on the same fix but for the CODA as well?
03-02-2017 02:36 PM - edited 03-02-2017 02:37 PM
@RogersDave Any reason why my D 3.1 shows on line 1 and not on line 0 like the others I see in this thread?
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 645000000 | 256QAM | 3.500 | 15 | 37.356 |
2 | 561000000 | 256QAM | 4.300 | 2 | 38.605 |
3 | 567000000 | 256QAM | 4.800 | 3 | 38.983 |
4 | 573000000 | 256QAM | 4.200 | 4 | 38.605 |
5 | 579000000 | 256QAM | 4.900 | 5 | 38.605 |
6 | 585000000 | 256QAM | 4.100 | 6 | 37.636 |
7 | 591000000 | 256QAM | 3.700 | 7 | 38.605 |
8 | 597000000 | 256QAM | 3.600 | 8 | 37.636 |
9 | 603000000 | 256QAM | 4.000 | 9 | 37.636 |
10 | 609000000 | 256QAM | 5.100 | 10 | 38.605 |
11 | 615000000 | 256QAM | 5.600 | 11 | 38.605 |
12 | 621000000 | 256QAM | 5.500 | 12 | 37.356 |
13 | 633000000 | 256QAM | 5.100 | 13 | 37.636 |
14 | 639000000 | 256QAM | 4.600 | 14 | 37.356 |
15 | 555000000 | 256QAM | 4.000 | 1 | 38.605 |
16 | 651000000 | 256QAM | 3.200 | 16 | 36.610 |
17 | 657000000 | 256QAM | 3.100 | 17 | 36.610 |
18 | 663000000 | 256QAM | 4.500 | 18 | 37.356 |
19 | 669000000 | 256QAM | 5.300 | 19 | 36.610 |
20 | 675000000 | 256QAM | 5.400 | 20 | 36.610 |
21 | 681000000 | 256QAM | 6.600 | 21 | 36.387 |
22 | 687000000 | 256QAM | 5.700 | 22 | 36.387 |
23 | 693000000 | 256QAM | 6.400 | 23 | 36.610 |
24 | 699000000 | 256QAM | 6.100 | 24 | 35.780 |
25 | 705000000 | 256QAM | 6.400 | 25 | 35.780 |
26 | 711000000 | 256QAM | 6.500 | 26 | 35.595 |
27 | 717000000 | 256QAM | 6.800 | 27 | 36.387 |
28 | 723000000 | 256QAM | 6.900 | 28 | 36.387 |
29 | 825000000 | 256QAM | 6.800 | 29 | 37.356 |
30 | 831000000 | 256QAM | 7.300 | 30 | 37.636 |
31 | 837000000 | 256QAM | 7.700 | 31 | 37.356 |
32 | 843000000 | 256QAM | 6.700 | 32 | 36.610 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | NA | NA | NO | NO | NO | NA |
1 | 4K | 275600000 | YES | YES | YES | 2.200001 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 30596000 | ATDMA - 64QAM | 40.500 | 1 | 6400000 |
2 | 38596000 | ATDMA - 64QAM | 42.250 | 3 | 3200000 |
3 | 23700000 | ATDMA - 64QAM | 39.500 | 2 | 6400000 |
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 |
03-02-2017 02:42 PM - edited 03-02-2017 02:42 PM
@Triple_Helix wrote:@RogersDave Any reason why my D 3.1 shows on line 1 and not on line 0 like the others I see in this thread?
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 4K 275600000 YES YES YES 2.200001
Mine was the same way for a while, I dont remember if rebooting/resetting the device changes the position or firmware. Being in either position didnt affect my performance in anyway.
03-02-2017 04:58 PM
03-02-2017 05:01 PM
03-02-2017 05:53 PM
@markopas wrote:
@Triple_Helix wrote:@RogersDave Any reason why my D 3.1 shows on line 1 and not on line 0 like the others I see in this thread?
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 4K 275600000 YES YES YES 2.200001 Mine was the same way for a while, I dont remember if rebooting/resetting the device changes the position or firmware. Being in either position didnt affect my performance in anyway.
Was receiver "0' until Rogers improved signal strength.....then switched to "1"....but after a factory reset it returned to "0"......However PLC power is negative compared to yours. What hardware are you guys using to get speed of 938/21. Best I get using MS Surface Pro to nearest Rogers Server (24KM) is 875/33 with a ping of 8 in either Bridge or Gateway modes...with Cat 7. Still doing more tests to see if it's my equipment or Rogers infrastructure why I cannot get closer to 1Gbps. Otherwise CODA blk dot has been stable with occational Rogers reboots (2 - 3 day average).
Located at Meadowvale/Lawrence.
OFDM Downstream Overview
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | 4K | 275600000 | YES | YES | YES | -2.700001 |
1 | NA | NA | NO | NO | NO | NA |
03-02-2017 06:48 PM
I am in the far east midtown oshawa and see the same thing, it's on this I wonder why?
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 | 4K | 290600000 | YES | YES | YES | -5.500000 |
03-02-2017 07:11 PM
@jjunge wrote:
The gateway is now rebooting spontaneously multiple times per day with a ton of error messages in the log. Any idea what is going on @RogersDave???
can you post the DOCSIS logs and signal levels.
03-02-2017 07:42 PM