*** 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*
Just a quick update on what I've seen
Gateway mode
| Hardware Version | 1A |
| Software Version | 2.0.10.19 |
First CODA Lan port (topmost) connects to my router at 1000 Half Duplex, all other ports proper at 1000 Full Duplex.
Second, I haven't reset the CODA in a few days:
| LAN Up Time | 002 days 20h:14m:11s |
| WAN Up Time | 002 days 20h:12m:23s |
But I am not seeing the speed degradation that others have posted, buffer bloat still telling the story, as the DSL Reports Test (second) nearly matched the SpeedTest report (first) until the buffer bloat started ramping up.
@reefermajic69 what firmware do you have loaded on the router? If its stock firmware or Merlin, check the LAN .... SWITCH CONTROL and ensure that the NAT Acceleration is enabled. That is Broadcom's Cut Through Forwarding and Flow Acceleration (modem dependant). If you want to run anything over 100 mb/s thru a Broadcom based router, that NAT Acceleration should be enabled and must be enabled for gigabit rates. It is not compatible with various functions such as Traffic Monitoring and traditional QOS among others. Those functions will kick off the NAT Acceleration, possibly without warning.
My advice in this situation has been to check the firmware for any updates that might be available. Update the modem if there is a newer firmware version available. Run a Factory reset, regardless of whether you have updated the firmware or not. After the update, run an ethernet speedtest using the www.speedtest.net Toronto Rogers or Montreal Rogers server just to obtain baseline results.
Then, go down the menu on the left hand side and disable any and all functions that you aren't currently using and that you know you will not be using. For those items that you decide to enable, enable it and then run a speedtest right away so that you know if you're going to take a hit on the throughput. Do this one item at a time when you enable something so that you know exactly which functions can cause a throughput drop. At that point its up to you to decide if you want to accept that throughput drop or not. At least this way you will know what is causing it.
On my RT-AC68U I run AI Protection .... Network Protection, firewall, DHCP, DOS protection and wifi. Just the basics. Everything else is turned off. Running a speedtest I'll see 900 Mb/s down, maybe 40 to 45 Mb/s up depending on the time of day. The max that I've seen when connected directly to the modem is 950 Mb/s down, 40 to 45 Mb/s up. Just to note, the AI protection won't cost you anything in terms of throughput for IPV4. It kills IPV6 transfer rates, most likely due to the packet scans. With your router you might see better results when IPV6 is enabled on the modem again. I don't remember the processor rate on that router, so I'm assuming its faster that the 68Us 800Mhz processor.
There is a thread here somewhere, fairly recent of the exact situation that you're in. One router factory reset later and all is well, so taking the time to go thru the router settings and ensuring that the throughput killing functions are disabled should resolve the issue.
@reefermajic69, you indicated that "when I run the Coda Black dot to my PC wired I'm getting about 700D 30U ping 10 but when I run it in Bridge to my ASUS RT87 the speed drops to like 350D15U with a ping of 15-30?"
I'm assuming that when you run with a direct connection to the modem that you're running via ethernet? Is that correct? And, when you run the speedtest via the RT-87U, is that via ethernet or wifi?
Can you try connecting the pc directly to the modem when the modem is in Bridge mode and disconnect the router. Reboot or restart the pc so that it picks up the correct IP address. Then after the reboot/restart, run a speedtest to see what the results are in Bridge mode. Remember that the pc is only protected by its own firewall at this point, so, after the test, disconnect the pc from the modem so that its not exposed to the outside world beyond the time required for the test. Can you let me know what the results are. If those results are as good as previously stated, ie: 700 Mb/s or higher, consider running a router reset and set the parameters from scratch, don't use a backup restore file.
-
482104 views
-
295 Likes
-
-
