We are currently offering our users an exclusive opportunity to participate in an upcoming trial of the new firmware for our Rocket Wi-Fi Modem (CGN3ACR, CGN3AMR and CGN3ACSMR) and Rocket Gigabit Wi-Fi Modem (CGN3552 and CODA-4582). For details of this program, please see this thread.
This thread will be used for feedback regarding the firmware. We've invited @RogersSergio, @RogersSyd & @RogersBob from our Networking team to participate in this thread. Your feedback is very valuable and will be used to enhance the firmware before it is released publicly.
Thank you for your continued feedback and support.
I had my upload issue, but only running the MAC based Speedtest.net app to the Rogers server using IPv6. This behaviour only started a few days ago. Switching to Telus or Innsys gave me my expected upload speed. Did you try servers other than Rogers using IPv6?
By the way, even with IPv6 enabled when you run the speedtest.net app to a Bell server, it will use IPv4. You can see that in the speedtest.net results history.
Also I assume your Asus IPv6 settings follow https://communityforums.rogers.com/t5/Internet/Rogers-IPv6-Status/m-p/373238#M36710
Not sure you can enable/disable Nat Accelaration from the user interface. Is AI Protection and QOS disabled?
I just did my Speedtest again. Using IPv6 to the Rogers server I get 10 mbps upload. Using Telus 30. I wonder if there's some funky IPv6 routing issue going on? By the way, I'm still on .32 firmware, not .33 .
You know, that's a rather interesting observation. Maybe, for any situation where there's either slow speeds, inconsistent speeds, or micro-disconnects, a temporary test recommendation should be to run a ping test to the CMTS, using two test cases, one with IPV6 running and one with IPV4 only where IPV6 is disabled. Maybe that test should be run for every modem, just to see what turns up. You never know until you start looking at the data.
Are we discussing the white Hitron CODA-4582 exclusively, no other modem? If so, wonder if this has anything to do with the update to firmware version 7x, currently at 22.214.171.124? That uses an updated kernel which is supposed to support OFDMA (DOCSIS 3.1 upstream).
Have you tried google fibre's speedtest: http://speedtest.googlefiber.net/
Ok, fwiw, I'm running a 4582 U 2A with version 126.96.36.199 loaded, in bridge mode with an Asus RT-AC86U behind it. With IPV6 disabled, and using the speedtest.net Rogers Ottawa or Montreal server, I usually hit 940 Mb/s (or slightly higher) down, ~32.88 Mb/s up. I'll usually run three or four speedtests looking for consistency just to be sure, so within that group, I'll hit the above numbers at least one or more times. If I don't, the end numbers won't be far from that target. I've also hit those numbers using Google Fibre's speedtest as well.
Guess I'll have to fire up the 68U, run an update and then run some tests with IPV6 enabled. That's on my list of things to do now.
Edit: oops, corrected the disabled statement above to read: "With IPV6 disabled"
Apologies for any confusion.
Just checked with my better half who uses Teams as well for her work. She hasn't had any problems using Teams. I'm guessing that's due to the fact that IPV6 isn't enabled in the router.
So, the question is, is this a modem issue or a CMTS issue? That's something that @RogersIan should look into.
That would be the traffic shaping that Rogers isn't supposed to be doing? I think this is more a case of an error in the modem's new firmware, or, someone has changed the CMTS configurations, once again, and mucked things up. Wouldn't be the first time that's happened and it won't be the last.
If one was to run a passive tap between the modem and router to capture the data traffic, for both IPV6 enabled and IPV6 disabled in the router, something should show up in the data log. Question is, who's at fault, the modem or CMTS.
Don't know. That would require a passive tap between the modem and the neighbourhood node. That's something that Rogers engineering staff should be able to easily accomplish. I'd say that @RogersIan and company will have to look at this.