03-27-2018 10:10 PM
I am taking your issue back into our lab and asking the vendor to see if they can either replicate or provide additional information that may help us get to the bottom of this issue.
With all the consumer electronics out in the field it is extremely difficult to have access to it all let alone be able to test it all.
We may need your help to further troubleshoot this issue; I will reach out at that time
Regards,
RogersSergio
03-29-2018 12:12 AM
Thank you all for your ongoing feedback.
With your help we are continuing to identify and fix a number of issues that affect all our customers so I want to thank you all for your help.
As part of this ongoing improvement I want to let everyone know that I have new firmware for CODA (2.0.10.34T5) and AC (4.5.8.38T4) devices
We will be updating the notes at the top of the forum shortly.
In the meantime I will be working to roll out the new firmware to everyone over the next few days.
As always please let us know of any issues that are experienced.
Thank you,
RogersSergio
03-29-2018 02:53 AM - edited 03-29-2018 03:00 AM
Oof. Got the new firmware, but I'm getting a ton of packet loss, poor speeds, and some disconnects. Gonna restart modem to see if that helps, but here is my event log from the firmware update onward. Can anyone explain what the Unicast Maintenance requests etc. are??
Edit: speedtest is good after I made this post. It may have just been those maintenance requests giving me packet loss and disconnects, I'm not sure. But whatever was causing it, it seems to have gone away.
5 | 03/29/2018 04:39:42 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
6 | 03/29/2018 06:28:58 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
7 | 03/29/2018 06:28:59 | 82000300 | critical | Ranging Request Retries exhausted;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
8 | 03/29/2018 06:28:59 | 82000600 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
9 | 03/29/2018 06:29:05 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=xCM-QOS=1.1;CM-VER=3.1; |
10 | 03/29/2018 06:29:06 | 82000300 | critical | Ranging Request Retries exhausted;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
11 | 03/29/2018 06:29:06 | 82000600 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
12 | 03/29/2018 06:44:06 | 82000400 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
13 | 03/29/2018 06:44:27 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
14 | 03/29/2018 06:44:28 | 82000400 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
15 | 03/29/2018 06:44:31 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
16 | 03/29/2018 06:44:32 | 82000300 | critical | Ranging Request Retries exhausted;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
17 | 03/29/2018 06:44:32 | 82000600 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
18 | 03/29/2018 06:44:36 | 82000400 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
19 | 03/29/2018 06:45:01 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
20 | 03/29/2018 06:45:14 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
03-29-2018 11:26 AM
03-30-2018 09:14 AM
Thank you for quick implementation of the newest firmware 2.0.10.34T5. The download speeds on wired connections improved greatly from around 500Mbps to close to 1G - which is what I'm supposed to get. My wi-fi though is without the change and ranges from 50's Mbps to (rarely) 200's Mbps, even when few feet from the modem. The upload speed has always been good on wire 30+ Mps, and no change here.
The biggest problem I'm experiencing, and which has not changed from the 2.0.10.28T2, is the 2.4G wi-fi. It cuts out intermittently and when it does it does not broadcast so devices cannot find it. Sometimes it comes back on its own after few minutes, sometimes it does not and I need to reboot the modem. Unfortunately, not all of my devices support 5G. In my case they are printers, some older game consoles & raspberry pie. The 5G has been very stable.
03-30-2018 10:05 AM
03-30-2018 01:22 PM
I got the 2.0.10.34T5 firmware in my router. However, the Guest network still give out the "only allow DHCP client to use this wireless" message.
Just wonder if someone can share the setting in the guest network?
03-30-2018 01:58 PM
My Wi-Fi speeds are still pretty bad on both 2.4Ghz, 5Ghz. My connection also falls on it's face every time I try to do a speed test which is weird, but I think others here were having a similar issue.
03-30-2018 04:20 PM - edited 03-30-2018 04:25 PM
It looks like the latest 2.0.10.34T5 firmware has crippled the SMB external hard drive sharing.
It's been working fine for months but since the update yesterday, the SMB ports are no longer listed in the scanned services. Only port 111 (portmapper, rpcbind) is now presenting. The admin interface shows that the drive is still detected and sharing is enabled. Even disable/enable, reboot, eject/remove/replug make no difference.
It's dead Jim...
Anyone else seeing this?
03-31-2018 06:02 AM