@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.
I am running the current firmware for the ASUS RT87. I also don't have QOS on as well all optional functions are set to off. The only thing I would be running is the CODA bridge into router and using the router for gateway function for my home network as well WIFI. I had called ASUS before and we were trying to troubleshoot but nothing worked to the point the ASUS tech support told me to reset the CODA. My luck when I reset it the CODA was pushing 10mbps on download???????????? Needless to say I felt like a fool and told the ASUS rep I better go deal with Rogers and get a consistent speed worthy of Gig before I even bother them. This was on the prior to black dot CODA as well firmware 19. Nat is set to on. I can provide screen prints of my settings and maybe you can suggest something. End of day the CODA is garbage as a router hence the need for a 3rd party.
@RogersDave (Or anyone else) couple of questions that I am seeing in my logs and was wondering if anyone has seen this before.
CODA (Non Blackdot) in bridge mode with .20 firmware runs fine and normal for about 1 week and has been online for 015 days 17h:20m:51s (Since Jan 11th) and about after 1 week additional errors and warnings have popped into the log.
3 01/18/2017 08:23:03 68010300 error DHCP RENEW WARNING - Field invalid in response v4 option
4 01/18/2017 20:15:19 84020200 warning Lost MDD Timeout
5 01/19/2017 08:23:03 68010300 error DHCP RENEW WARNING - Field invalid in response v4 option
6 01/19/2017 12:19:37 84020200 warning Lost MDD Timeout
7 01/22/2017 14:19:19 82000200 critical No Ranging Response received - T3 time-out
8 01/22/2017 21:53:01 68010100 error DHCP RENEW sent - No response for IPv4
9 01/23/2017 21:07:13 82000200 critical No Ranging Response received - T3 time-out
10 01/24/2017 04:38:01 68010100 error DHCP RENEW sent - No response for IPv4
11 01/24/2017 18:03:30 82000200 critical No Ranging Response received - T3 time-out
12 01/25/2017 11:22:07 68010100 error DHCP RENEW sent - No response for IPv4
13 01/25/2017 21:53:02 68010200 error DHCP REBIND sent - No response for IPv4
14 01/26/2017 02:25:27 82000200 critical No Ranging Response received - T3 time-out
15 01/26/2017 08:21:50 68010200 error DHCP REBIND sent - No response for IPv4
16 01/26/2017 08:23:03 82000200 critical No Ranging Response received - T3 time-out
17 01/26/2017 08:25:43 90000000 warning MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1
18 01/26/2017 08:25:47 84000700 warning RCS Partial Service
19 01/26/2017 08:55:40 68010300 error DHCP RENEW WARNING - Field invalid in response v4 option
20 01/26/2017 12:19:25 84020200 warning Lost MDD Timeout
The DHCP and MDD I have seen before and was not too concerned about but last night (Log times are UTC) there seems to be some additional errors along the line. I am wondering if the longer the device remains online the more frequent these errors are going to occur as you can see the errors are becoming more often.
Other question is that on the DOCSIS WAN page it states that the modem has an IP address with a lease time of 7 days which never changes/counts down (This timeline matches up with the DHCP errors seen above as they only popped up after 7 days in which it would be expecting to have another DHCP request). The IP that it gets is a 7.36.X.X/22 which is not a typical Rogers IP address and a quick ARIN Whois shows that the 220.127.116.11/8 address block belongs to "DoD Network Information Center" in Colombus, Oh. This doesn't seem right and was wondering if anyone else is seeing this same address block on a modem in bridge mode.
@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.
For comparisons sake, here's mine (bridge mode);
|9||01/17/2017 07:26:04||68010300||error||DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=a8:4e:3f:xx:yy:zz;CMTS-MAC=00:17:10:xx:yy:zz;CM-QOS=1.1;CM-VER=3.1;|
|10||01/18/2017 01:39:54||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=a8:4e:3f:xx:yy:zz;CMTS-MAC=00:17:10:xx:yy:zz;CM-QOS=1.1;CM-VER=3.1;|
|11||01/18/2017 07:26:04||68010300||error||DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=a8:4e:3f:xx:yy:zz;CMTS-MAC=00:17:10:xx:yy:zz;CM-QOS=1.1;CM-VER=3.1;|
|12||01/19/2017 01:40:27||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=a8:4e:3f:xx:yy:zz;CMTS-MAC=00:17:10:xx:yy:zz;CM-QOS=1.1;CM-VER=3.1;|
|13||01/19/2017 07:26:04||68010300||error||DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=a8:4e:3f:xx:yy:zz;CMTS-MAC=00:17:10:xx:yy:zz;CM-QOS=1.1;CM-VER=3.1;|
|14||01/20/2017 04:18:47||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=a8:4e:3f:xx:yy:zz;CMTS-MAC=00:17:10:xx:yy:zz;CM-QOS=1.1;CM-VER=3.1;|
|16||01/22/2017 13:32:26||69010100||notice||SW Download INIT - Via NMS|
|17||01/22/2017 13:40:09||69011100||notice||SW download Successful - Via NMS|
|18||01/22/2017 13:44:21||90000000||warning||MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=a8:4e:3f:xx:yy:zz;CMTS-MAC=00:17:10:xx:yy:zz;CM-QOS=1.1;CM-VER=3.1;|
From a modem behaviour perspective, critical T3 time-outs on my old Cisco DPC3825 would be the indication for loss of upstream channels (where the upstream signal levels would spike above +55dBmV and then disappear), and once it got down to 1 channel up and a T3 timeout occured, the modem would reset (loss of connectivity for a brief period), and all 3 channels would return.
It appears the CODA modem is much more tolerant to T3 timeouts, as I still have 3 upstream channels. Unless I'm not understanding T3 timeouts properly in terms of what causes them, and what their impact is.
And here's the info on the 7.x.y.z network;
Essentially, it's how the agents at the Customer Care desk connect to the modem on Rogers internal IP network.
T3 Timeout ( Ranging Request Retries Exhausted )
Explanation: The cable modem has sent 16 Ranging Request (RNG-REQ) messages without receiving a Ranging Response (RNG-RSP) message in reply from the CMTS. The cable modem is therefore resetting its cable interface and restarting the registration process. This typically is caused by noise on the upstream that causes the loss of MAC-layer messages. Noise could also raise the signal-to-noise ratio (SNR) on the upstream to a point where the cable modem’s power level is insufficient to transmit any messages. If the cable modem cannot raise its upstream transmit power level to a level that allows successful communication within the maximum timeout period, it resets its cable interface and restarts the registration process. This error message is DOCSIS event message is R03.0, Ranging Request.
Thanks @Double_K for sharing your logs and the tidbit about the Rogers IP workaround (I figured there was a reasoning for it somewhere).
Was not even thinking this morning at looking at my signal levels as after a tech visit things have been pretty solid and safe. However that was wrong thinking as looking at the levels now I have a few channels showing some issues. Some downstream signal noise ratio have fallen way down and some channels have reverted to 64QAM. Upstream still look normal though.
1 609000000 256QAM 1.400 34 40.366
2 363000000 256QAM 0.500 10 40.946
3 369000000 256QAM 0.500 11 40.946
4 375000000 256QAM 0.600 12 40.946
5 381000000 256QAM 0.500 13 40.946
6 387000000 256QAM 1.000 14 40.946
7 393000000 256QAM 1.100 15 40.946
8 399000000 256QAM 1.200 16 40.946
9 405000000 256QAM 1.300 17 40.366
10 411000000 256QAM 1.700 18 40.946
11 417000000 256QAM 1.700 19 40.946
12 423000000 256QAM 1.600 20 40.946
13 429000000 256QAM 1.700 21 40.946
14 435000000 256QAM 1.900 22 40.946
15 441000000 256QAM 2.200 23 43.377
16 447000000 256QAM 2.300 24 40.946
17 555000000 256QAM 2.300 25 4.243
18 561000000 256QAM 2.300 26 39.855
19 567000000 256QAM 2.000 27 4.243
20 573000000 64QAM 2.100 28 4.191
21 579000000 256QAM 1.800 29 4.243
22 585000000 256QAM 1.800 30 4.243
23 591000000 64QAM 1.700 31 4.191
24 597000000 64QAM 1.400 32 4.191
25 603000000 256QAM 1.200 33 40.366
26 357000000 256QAM 0.100 9 40.946
27 615000000 256QAM 1.300 35 40.946
28 621000000 256QAM 1.500 36 40.946
29 633000000 256QAM 1.700 37 40.946
30 639000000 256QAM 2.000 38 40.946
31 645000000 256QAM 2.100 39 40.366
32 651000000 256QAM 2.500 40 40.946
1 38595648 ATDMA - 64QAM 43.500 3 3200000
2 30596000 ATDMA - 64QAM 41.500 1 6400000
3 23700000 ATDMA - 64QAM 41.500 2 6400000
I don't really want to reboot it right now to see if things go back to what they are supposed to but it may be another modem signal issue. Still getting about 500/50 on 1G over Wifi so thats not awful.
Still waiting for the new Firmware .23! http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/message-id/331...
*IPv6 remains disabled on this modem until all modems are upgraded