@lulwt, @RogersIan this is the same problem that @Hucklebury is experiencing. Modem in Gateway mode, full download rates, modem in Bridge mode with a router behind it, half speeds. The router in question is an Asus RT-AC86U, same router that I have. This is with the modem running DOCSIS 3.1. If the modem runs DOCSIS 3.0 for any reason, then it runs at full rates, 900+ Mb/s on the download side.
I'm not seeing this problem where I am (West Ottawa), but, I do see lower download rates from the www.speedtest.net Rogers Toronto, Ottawa, and Montreal servers, anywhere from 600 to 700 Mb/s. This has been going on for at least a month. The Toronto Vmedia and Montreal Ebox servers show 930 Mb/s down, ~32/33 Mb/s up. I'm running 36T6 at the present time.
Fwiw, watching the Ebox speedtests with Wireshark, you can see a switch(?) to Web Sockets occur at the beginning of the test, followed by switch back to HTTP/1.1. The speedtest commences after the switch back to HTTP. This runs at full rates. The Rogers test runs HTTP/1.1 with no switch to Web Sockets. This test runs slower than normal. All of my tests are run with Firefox at the present time as Firefox currently produces the highest download rates on a speedtest.
Mixed up in this is a switch to HTTPS by the speedtest servers. Don't know how that currently affects the Rogers servers.
Fwiw, looks like you have to keep an eye on the Rogers server results and test with other ISP servers, including Toronto Vmedia and Montreal Ebox.
Tonight we plan to push 126.96.36.199T6 to our AC device community members.
This build includes:
Hello. I have Adv Wi-Fi Mdm on Ignite 250U.
Hardware Version 1A
Software Version 188.8.131.52T5
Got it a couple months ago, 2.4GHZ and 5GHZ worked fine until I changed the 2.4 band to N only. All my N devices could not connect to the 2.4 band after a couple of days. Cellphones, TV, laptops, PC's... none would connect, not even after rebooting or trying to manually connect them. The 5GHZ band continued to work nice and smooth. Only the 2.4 band was affected given that the change in setting is localized to 2.4 only. Rebooting the router or changing any 2.4 setting fixed it for a a day or two. Problem came back and continued to recur almost daily until some form of reset or reboot is performed. I've proved it by going back to default mixed mode g/n for two weeks without any problems. Changed back to N earlier this week and now the problem is back. Switching back to mixed mode g/n to make this problem go away. This has to be a bug with the firmware, possibly in combination with my hardware version. Level II does not want to listen. Good luck with this problem.
My up time is 14 days and i'm in bridge mode so I do not see this.
on Hardware 1A
Good uptime in gateway mode for me
LAN Up Time 028 days 15h:05m:54s
Speed in Bridged mode still sucks. On 36T6 for 29 days.....average speed around 400 Down and far from 1GB. Have not reached near 1000 since April. Problems either with local street Amps or Rogers servers. As you can see from the graph over last 30 days.....it's pathetic. When you're paying for 1Gb speed....the average should be 1000 not 400 regardless whether you're Gateway or Bridge mode. And yes, in Gateway mode using direct connect...I am also getting same results. Rogers, please get your act together or lose more customers.