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*
03-02-2017 07:57 PM - edited 03-02-2017 08:00 PM
@rjmaxim wrote:
@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
I did another Factory Reset and now it's on line 0. I still feel that my Upload sucks.
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 591000000 | 256QAM | 3.800 | 7 | 38.605 |
2 | 567000000 | 256QAM | 4.600 | 3 | 38.605 |
3 | 573000000 | 256QAM | 4.000 | 4 | 38.605 |
4 | 579000000 | 256QAM | 4.800 | 5 | 38.605 |
5 | 585000000 | 256QAM | 4.000 | 6 | 38.605 |
6 | 561000000 | 256QAM | 4.300 | 2 | 38.605 |
7 | 597000000 | 256QAM | 3.500 | 8 | 37.636 |
8 | 603000000 | 256QAM | 4.000 | 9 | 37.636 |
9 | 609000000 | 256QAM | 5.000 | 10 | 38.605 |
10 | 615000000 | 256QAM | 5.500 | 11 | 38.983 |
11 | 621000000 | 256QAM | 5.400 | 12 | 37.356 |
12 | 633000000 | 256QAM | 5.300 | 13 | 37.636 |
13 | 639000000 | 256QAM | 4.700 | 14 | 37.356 |
14 | 645000000 | 256QAM | 3.500 | 15 | 37.356 |
15 | 651000000 | 256QAM | 2.900 | 16 | 36.610 |
16 | 657000000 | 256QAM | 2.800 | 17 | 36.610 |
17 | 663000000 | 256QAM | 4.200 | 18 | 36.387 |
18 | 669000000 | 256QAM | 4.900 | 19 | 36.387 |
19 | 675000000 | 256QAM | 4.900 | 20 | 36.610 |
20 | 681000000 | 256QAM | 6.300 | 21 | 36.610 |
21 | 687000000 | 256QAM | 5.500 | 22 | 36.387 |
22 | 693000000 | 256QAM | 6.200 | 23 | 37.356 |
23 | 699000000 | 256QAM | 6.000 | 24 | 37.356 |
24 | 705000000 | 256QAM | 6.100 | 25 | 37.356 |
25 | 711000000 | 256QAM | 6.200 | 26 | 37.356 |
26 | 717000000 | 256QAM | 6.500 | 27 | 37.356 |
27 | 723000000 | 256QAM | 6.600 | 28 | 37.636 |
28 | 825000000 | 256QAM | 6.300 | 29 | 37.356 |
29 | 831000000 | 256QAM | 6.800 | 30 | 37.356 |
30 | 837000000 | 256QAM | 7.200 | 31 | 36.610 |
31 | 843000000 | 256QAM | 6.400 | 32 | 36.387 |
32 | 555000000 | 256QAM | 4.100 | 1 | 38.605 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | 4K | 275600000 | YES | YES | YES | 2.200001 |
1 | NA | NA | NO | NO | NO | NA |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 30596000 | ATDMA - 64QAM | 39.500 | 1 | 6400000 |
2 | 38596000 | ATDMA - 64QAM | 41.500 | 3 | 3200000 |
3 | 23700000 | ATDMA - 64QAM | 39.500 | 2 | 6400000 |
03-02-2017 08:11 PM
Triple_Helix wrote:
I did another Factory Reset and now it's on line 0. I still feel that my Upload sucks.
Upload is still DOCSIS 3.0, so the OFDM switching from 1 to 0 has no effect on it.
03-02-2017 09:18 PM
03-03-2017 08:46 AM
@Triple_Helix wrote:
@rjmaxim wrote:
@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 I did another Factory Reset and now it's on line 0. I still feel that my Upload sucks.
Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB) 1 591000000 256QAM 3.800 7 38.605 2 567000000 256QAM 4.600 3 38.605 3 573000000 256QAM 4.000 4 38.605 4 579000000 256QAM 4.800 5 38.605 5 585000000 256QAM 4.000 6 38.605 6 561000000 256QAM 4.300 2 38.605 7 597000000 256QAM 3.500 8 37.636 8 603000000 256QAM 4.000 9 37.636 9 609000000 256QAM 5.000 10 38.605 10 615000000 256QAM 5.500 11 38.983 11 621000000 256QAM 5.400 12 37.356 12 633000000 256QAM 5.300 13 37.636 13 639000000 256QAM 4.700 14 37.356 14 645000000 256QAM 3.500 15 37.356 15 651000000 256QAM 2.900 16 36.610 16 657000000 256QAM 2.800 17 36.610 17 663000000 256QAM 4.200 18 36.387 18 669000000 256QAM 4.900 19 36.387 19 675000000 256QAM 4.900 20 36.610 20 681000000 256QAM 6.300 21 36.610 21 687000000 256QAM 5.500 22 36.387 22 693000000 256QAM 6.200 23 37.356 23 699000000 256QAM 6.000 24 37.356 24 705000000 256QAM 6.100 25 37.356 25 711000000 256QAM 6.200 26 37.356 26 717000000 256QAM 6.500 27 37.356 27 723000000 256QAM 6.600 28 37.636 28 825000000 256QAM 6.300 29 37.356 29 831000000 256QAM 6.800 30 37.356 30 837000000 256QAM 7.200 31 36.610 31 843000000 256QAM 6.400 32 36.387 32 555000000 256QAM 4.100 1 38.605 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.200001 1 NA NA NO NO NO NA Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth 1 30596000 ATDMA - 64QAM 39.500 1 6400000 2 38596000 ATDMA - 64QAM 41.500 3 3200000 3 23700000 ATDMA - 64QAM 39.500 2 6400000
WoW What a change this morning, why can't it be this way all the time.
03-03-2017 09:19 AM
@Triple_Helix wrote:
WoW What a change this morning, why can't it be this way all the time.
Now you're really making me jealous 😞
03-03-2017 09:38 AM
@markopas wrote:
@Triple_Helix wrote:
WoW What a change this morning, why can't it be this way all the time.
Now you're really making me jealous 😞
But the Upload is all over the place.
03-03-2017 09:42 AM - edited 03-03-2017 09:43 AM
UPNP doesn't work. Probably like two firmwares ago it was working but i've came to the conclusion it doesn't work after endless troubleshooting. Xbox one doesn't port map and various computer software as well.
03-03-2017 10:58 AM
I would disable UPNP, its the first thing I do whenever configuring router /gateway / firewall.
I have never understood how manufacturers ever accepted to include such a horrible thing on a device with the main mandate to protect your internal network. How is it that anyone thought this would be a good idea? allowing just about anything inside your network to open ports on your firewal? UPNP is ust a disaster waiting to happen...
Just imagine getting some virus on your PC while cheking your email at Starbucks, then going home and that virus opening your network to the whole world, ports like SMB and suddenly anyone has access to your files, etc.
Not good..
03-03-2017 11:03 AM
03-03-2017 11:41 AM
03-03-2017 01:23 PM
03-03-2017 01:50 PM - edited 03-03-2017 01:51 PM
03-03-2017 01:58 PM
@toolcubed wrote:
Bridge the darn thing and use a much better 3rd party router. Mine is bridged with an Asus RT-AC68U and I don't have any problems - WiFi, IPv6, etc...all working well.
Completely agree - at best the HITRON is a good cable modem but that's about it. I would be more than happy if I could go back to .19 firmware if you can make my DLINK work on that version since everything worked well except for my router 😞
03-03-2017 02:08 PM - edited 03-03-2017 02:11 PM
@Lumute wrote:I would disable UPNP, its the first thing I do whenever configuring router /gateway / firewall.
I have never understood how manufacturers ever accepted to include such a horrible thing on a device with the main mandate to protect your internal network. How is it that anyone thought this would be a good idea? allowing just about anything inside your network to open ports on your firewal? UPNP is ust a disaster waiting to happen...
Just imagine getting some virus on your PC while cheking your email at Starbucks, then going home and that virus opening your network to the whole world, ports like SMB and suddenly anyone has access to your files, etc.
Not good..
UPnP is absolutly fine as long as the router firmware is current and done well. You example is a pretty fringe case, and viruses liek that just dont do that type of stuff any more in the wild. Its 99% malware that uses commonly opend ports anyways (port 80, 25 and such) and use it to either join you to a bot net or to send out spam.
Ive been working in IT as a tech for the last 13 years, you know how many examples i have seen of what you suggested in the last 5 years? zero. Know how many examples i have seen of what I mentioned above. Hundreds.
UPnP is also required and the only options for many services such as Xbox Live when you have more then one Xbox live client on the network. UPnP is the ONLY option for proper NAT if you are not wanting to use or cannot use IPV6 public addresses on the Xboxes for example. Taht why "manufacturers ever accepted to include such a horrible thing" on routing. Even corporate class routers have UPnP still. Proper network setup and proper security measures make UPnP a safe, viable tool to help map ports to comon services.
03-03-2017 04:57 PM - edited 03-03-2017 05:10 PM
UPNP is a horrible thing, should be taken behind the barn and shot down after a glass of good red wine (ala Mr Wonderful). Many security experts compare it to putting a fancy lock on your door and leaving the key in the keyhole and all of them agree it should be disabled.
Not only I have seen UPNP exploited by malware, I have exploited it myself to gain access to other peoples resources (with their permission of course) while remotely troubleshooting problems, quite easy...
For example: some versions of flash allow a website to gain control of UPnP on your router/firewall by just visiting such site. Has Flash been found extremely unsecure and crapy and everyone tells you to run from it? absolutelly! yet an insane amount of websites and people still relly on flash...
The main problem? people do not really understand what UPNP does or the security implications of it, of course with proper security measures you culd run a lan without a firewall but would you recommend it?
All that said, I just wanted to give a word of advise based on my experience as I have seem too many people rellying on this without having a clue of what it does. You understand what the protocl and feel you have secured your network enough and still want to use it, go for it...
03-03-2017 09:29 PM - edited 03-03-2017 10:04 PM
You can just do a test at https://www.grc.com/default.htm to see how solid the UPNP is. I didn't come across any issues running it on mine. That is not to say that it is bulletproof, but a no issue result from the scan is a good thing.
That being said, this is an interesting link as well: https://www.grc.com/unpnp/unpnp.htm
03-04-2017 12:52 AM - last edited on 03-04-2017 08:13 AM by RogersPrasana
I just signed up for the gigabit plan and my modem is Hitron CODA-4582.
I get great speed when connected wired but the wireless is really really weak.
I get about 25 mbps dowload wireless beside the modem. With wired I get about 900+ mbps download.
Does the modem have a bad wifi? Do I need a second router?.
03-04-2017 10:29 AM
It was UPnP which allowed the IoT devices to bring down Dyn. UPnP is a pretty big security risk.
03-04-2017 10:33 AM - edited 03-04-2017 12:40 PM
So I got a text message last week from rogers stating that in order to continue to get the best from my sevice, I'll need a modem upgrade. At the time I was using the the Hitron CGN3ACR (The one that has AC on the front side panel) it came with it's issues but surely enough after updating to the latest trial firmware most issues have been resolved, that being said I couldn't resist knowing there's a more "advanced" modem out there without trying it in hopes it's everything I currently have and more (better, more predictable/reliable speeds and ping etc) everything was looking great at first. I was getting better download speeds but still not close to what I pay for, upload speeds have gotten worse. less than half what it should be, not sure if this is due to the modem or just plain rogers buffoonery. Pings were improved but sadly the wifi signal is weak compared to my last modem. I can't get any connection to the rooms furthest from the modem on the second floor and this wasn't a problem with my last modem... Does the trial firmware adjust this issue? I was told this new modem (CODA-4582) was suppose to be superior to the last, is there a setting I could change to improve this or is the predecessor really better in terms of wifi signal strength.
03-04-2017 10:54 AM - edited 03-04-2017 11:07 AM
Ever since switching to CODA-4582 (and maybe after .24), I noticed that while browsing the internet (I usually use Chrome), sometimes a new tab will open (not sure if it is by itself or in response to a link click) with the URL of go.microsoft.com/login.html, but it will instead show the CODA modem login page. Anyone know why this happens?
It doesn't seem to be occurring in relation to anything in the Event Log because the UTC times in the log don't seem to match up with the occurrences. So on a side note, I've also been getting these errors and critical events:
Error: DHCP RENEW WARNING - Field invalid in response v4 option;
Critical: No Ranging Response received - T3 time-out;
They both end with CM-QOS=1.1;CM-VER=3.1;
Thanks
03-04-2017 07:27 PM
@rogrs_da_best wrote:
Ever since switching to CODA-4582 (and maybe after .24), I noticed that while browsing the internet (I usually use Chrome), sometimes a new tab will open (not sure if it is by itself or in response to a link click) with the URL of go.microsoft.com/login.html, but it will instead show the CODA modem login page. Anyone know why this happens?
It doesn't seem to be occurring in relation to anything in the Event Log because the UTC times in the log don't seem to match up with the occurrences. So on a side note, I've also been getting these errors and critical events:
Error: DHCP RENEW WARNING - Field invalid in response v4 option;
Critical: No Ranging Response received - T3 time-out;
They both end with CM-QOS=1.1;CM-VER=3.1;
Thanks
that login page is the setup page for the CODA. I would suggest performing a factory reset on the modem. Use a Pen tip or to press and hold the reset button on the back of the modem for 20 seconds then let go.
After 2 minutes the modem should be booted up, then open a web browser on your computer and it should automatically take you to that login page. setup the modem through that page and you should be good.