Just chiming in with my current results/issues
I had the 250Mbps package hooked up yesterday (wednesday Jan 4th) and even up until this morning I had an average speedtest of 330Mbps, though as of tonight, I've been stuck at 5-10Mbps Down.
Not sure what I should provide here, but I'm currently running firmware 126.96.36.199
Hopefully this is resolved soon, as it leaves a really bad impression to be having issues like this on the second day of service.
Good luck Dave with finding the solution, if possible, I would like to participate in any advanced/beta programs for firmware, if that is related to the issue.
Thanks so much I will give it a shot.
If the ASUS 2400 is no good then can you suggest one that is good with AC?
Issues getting an IP in bridge mode
We have been able to reproduce this on D-Link routers. It is an bug in the D-Link firmware (DD-WRT doesn’t have the bug) but we are looking at ways to mitigate it from the modem side.
If this issue occurs routers other than D-Link, let me know as I’ll need to investigate further.
Please check also TP-Link router, all users with TP-Link C2600 have this issue. If it is due to router's firmware then why is there is no issue with the previous modem in bridge mode and no issue with CODA if not in bridge mode? It's like there is a conflict when CODA is set to bridge mode.
also does the internet speed only half the speed if router is flashed with OpenWRT?
The LAN .... SWITCH CONTROL .... NAT Acceleration must be on for Asus routers if you want to run anything over 100 Mb/s. Now, the one thing that you have to keep in mind is that there are functions that will kick off the NAT Acceleration, such as Traffic Monitoring, Port Forwarding and others. The suggestion to reset the router back to default settings as indicated by @Makaveli99 is spot on as that will kill any functions that disable the NAT Acceleration.
When that is done, run a speed test using the www.speedtest.net Toronto Rogers server, or Montreal Rogers Server. If and when that is complete, go thru the entire menu list on the left hand side, look at every sub-menu item and ask yourself if you're using it or not. If not, disable it. If you decide to enable something, follow that with an immediate speedtest so that you know whether or not you're crippling the throughput by enabling that function.
Just to note, the RT-AC87U has been nothing but trouble for a good number of its users. If you have avoided all of its problems, consider yourself very lucky. If you're having issues with it, as many others have had, strongly consider getting rid of it and moving on to something else with better stability.
As for the speedtests, and I say this to everyone, you need to do some research to determine what the speedtest is doing:
1. single thread or multi-thread; and
2. what protocol is used; and
3. what browswer is best suited for that particular site; and
4. whether or not its so far away that any results you see are questionable at best.
Add to that discussion any device that you might decide to use to test the top speed of the gigabit service. Can the device actually support gigabit rates?
That all sounds rather harsh, but, we've had many people come into the forum in the past complaining about data rates and when we look very closely at routers, cabling, end devices, etc, we find that they are old, not configured properly or that they won't support gigabit rates. So, moving users up above 100 Mb/s was the first challenge, the challenge now is to get them to gigabit rates, while at the same time dealing with new modem issues.
So, best advice, bite the bullet and reset the modem. Watch the NAT Acceleration very closely to ensure that it doesn't get kicked off. Run the speedtests at www.speedtest.net Toronto Rogers, Toronto Beanfield, or Montreal Rogers or Fibrenoire if you're closer to Montreal than Toronto. Those servers have enough horsepower to test the last mile to the modem and drive higher data rates.
One main issue I find with testmyspeed and speedofme when i do a net stat is they only do a single socket for the connection test. which hardly can saturate a connection and i think that combined with HTML5 testing which is very hardware and browser dependant, offers lower results. Speedtest.net and any affilliated servers really are not evil like some try to suggest, they do a good job taking advantage of the bandwidth and it shows.
I can take these HTML5 speed test sites line them up and test them and get fruty loops results from all of them across all browsers all drastically different. Sad thing is I have the hardware to kill a connection, Intel Quad port server adapter with its own Proc and ram, i7 4770k, and well more ram then people need.
I still insist the speed tests I trust are DSL reports and Digital Oceans Speetest.net servers and both of them always show me comparable results.
@reefermajic69, the first thing to do is to force a restart on the modem. Pull the power from it, wait 30 seconds and plug it back in. After it boots up, log into it and kick it into Bridge mode. Leave the pc connected and reboot the pc as well. When the reboot into Bridge mode is complete, run a test at ipv6-test.com. That should show 4/20 as a final score as IPV6 is currently turned off on the modem. Then run a speedtest at www.speedtest.net Toronto Rogers or Beanfield or Montreal Rogers or Fibrenoire. Remember that the pc is relying on its own firewall for protection, so keep this time as short as possible. When that is done, take note of the speedtest results. I'll be interested in what you find.
Then run a Factory Reset on the router. That might hurt as you will have to reset the various parameters and pay very close attention to the LAN .... SWITCH CONTROL .... NAT Acceleration setting to ensure that it remains enabled. When the Factory Reset is complete, remove the power from it, connect it to the modem, and then power it back up. It should acquire an IP address from the modem and you should be able to connect to the router to set some minimal parameters for now. Disable items that you will not be using, but, at this point, don't enable anything perhaps beyond the AI Protection and the wifi. At this point you should run a speedtest to see what the results are. Depending on your CMTS and the loading on that CMTS, you may not see 900+ Mb/s at this time of the night. It wouldn't surprise me. You should however see the same data rate that you saw with a direct connection to the modem. Thats what you want to prove at this point. When you are done those tests, then I would go back into the modem and set the various parameters, once again, keeping an eye on the NAT Acceleration setting.
For the router, consider this. If you haven't really pushed the router with high data rates to this point, you may not have come across the same issues that others have. Lets see if you can get the router up to speed and go from there. I'm not keen on telling people to spend money, but, in the case of gigabit rates, end users are going to have to consider moving up from the usual consumer routers to something that can handle the higher data rates and provide the protection that they are looking for. That might mean moving to something like a Pfsense or Opensense router with an additional wifi only router such as the RT-87U as an access point. It depends on the stability of your 87U. Running gigabit rates is not going to be cheap. I have no hesitation in recommending other Asus routers, but my concern is whether or not they will actually handle the higher speeds. I don' t think there is a consumer router on the market these days that can adequately handle gigabit rates. There is a router that Asus is working on, the BRT-AC828. That is aimed at the business crowd apparently and hasen't been released yet from what I understand. In terms of it handling gigabit rates, I'll believe it when I see more reviews and test results. Thats going to be an expensive router. So, first things first, get the modem and router running at the data rates they should be at.
It should be on Auto and stay on Auto for the entire time that you are changing any other setting. Note that there was a new firmware version released in Dec so it would be worth running a check for that. On my RT-AC68U, with the new firmware, there is a note beside it that showed that both Cut Through Forwarding and Flow Acceleration were enabled initially after the firmware update. The Flow Acceleration portion of that note is new for the 68U. The fact that I run the AiProtection results in the Flow Acceleration being disabled. But, thats ok. I know that the 68U is underpowered for gigabit service although I can see speedtest results up to 950 Mb/s as everything else except for the wifi is disabled. So, that is something to keep in mind when you look at the NAT Acceleration.
Ok So I did all you ask and again same situation.
High with a direct connect but via the ASUS2400 it drops significantly