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.
Hmm, so, good idea (maybe, no cigar as of yet, grr). @asharahmed are you running stock firmware in your R7000? If so and you haven't heard about the security issues with Netgear routers, have a look at the following:
Same goes for anyone else running stock firmware.
I'm in the same boat. Not only are my speeds worse (3xx) /10 but are often quite erratic (speedtest might jump to 700 then fall down to 300). DSL reports says 23 of my 32 streams aren't doing anything and my Xbox says my network is 10/3. I disabled all ipv6 (wasn't on but I turned it on and them off) and still nothing.
Can we identify a pattern, e.g.
1) Bridge or gateway mode?
2) D3.1 in your area or not?
3) Gigabit plan?
FWIW, mine, in bridge mode, with no D3.1, on the 250 ignite plan, works great. Consistent 320ish/20 at speedtest.net. What am I doing differently from you guys?!
I am using the modem not in bridged mode and getting what I am subscribed for. Maybe you should try not in bridged mode and see what happens just to test
1) bridged as of current, havent really tested in gateway
2) how do i check
Re: D3.1, if you go to the status page that has all the information about the channels/signal strength, look under the OFDM sections. If you have D3.1 on your node there should be stuff there. Meanwhile, this is what I see:
|OFDM Downstream Overview|
|Receiver||FFT type||Subcarr 0 Frequency(MHz)||PLC locked||NCP locked||MDC1 locked||PLC power(dBmv)|
@Datalink It could be a bad manufacturing run due to these modems being new, but I also find that really hard to believe. When I got the modem yesterday and rebooted after I had everything set up, my speeds and ping were good. However, the speeds suddenly decrease. I'm thinking that it could be more of firmware issue than a hardware bug... More interesting however, yesterday I also ran into some in-game issues in LoL with the modem because there was high packet loss and it was noticeable in the gameplay. I was losing 7.6 packets/min as well as up to 10 packets/min on a second test. I gave rogers a call but they said everthing was fine b/c I was getting no packetloss from the node and had a 5ms ping.
I also called rogers today on my speed issues and I got a rogers tech rep to run some tests. The tests that they ran from the node to my modem weren't good. They said they'll have her peers look into it and try to solve this issue in the next 24-48 hours. I'll let you guys know of the progress.
Early morning test, can't possibly be node congestion before 6AM.. 357 / 11
Single client; direct connect to gateway in gateway mode (not bridge); IPv4 with IPv6 disabled; no DC3.1 binding; service provisioned at 1000/30; upload nerfed to around 8-12Mbps; download jumps between high 1XX and low 3XX; download test tends to started "faster" and then tail off slower.
Only custom settings I made to the modem are infinite DHCP LAN lease and custom DNS (22.214.171.124/etc.) 126.96.36.199 if any techies want to take a look while I'm at work 🙂
On a whim I ran more speedtests back to back to back to Rogers Toronto server after a modem reboot:
Test 1: 587/20 http://www.speedtest.net/result/5881326977.png
Test 2: 445/19 http://www.speedtest.net/result/5881331237.png
Test 3: socket-download01 error
Test 4: 427/18 http://www.speedtest.net/result/5881336531.png
Test 5: socket-download01 error
Test 6: 383/17 http://www.speedtest.net/result/5881343037.png
Test 7: socket-download01 error
Test 8: 433/17 http://www.speedtest.net/result/5881346335.png
Ran a speedtest this morning and it is back to a crawl:
No wifi internet access on either the 2.4 or 5ghz. I am on my second CODA in two days, not really confident in switching to a third. Can you help??
Good morning Community,
It has been a busy night and I couldn't follow all the messages being posted but I'll try to summarize the main issues that were reported here yesterday and overnight.
Modem rebooting automatically: in most cases, these are modems that were activated on Tuesday or Wednesday that had IPv6 enabled. The modem will reboot once to accept the new configuration file that disables IPv6. It should be a single occurrence, if it is more frequent, let me know.
5 GHz WiFi performance: There are some reports of poor performance of WiFi, especially on the 5GHz band. This is being addressed with some improvements coming in the next firmware, likely before Christmas (it wasn't ready to launch in time). I also expect further tuning in the upcoming releases. One important note is that the antennas in this modem are all located at the top of the unit. For best performance, the unit should be installed upright (when facing the modem, the Rogers logo should be at the top) with nothing siting on top of the modem.
Pixel and Pixel XL frequent disconnects: I have been tracking this one and collecting traces for Hitron and Google. I was asked yesterday for a set of traces to put a fixed IP (instead of DHCP) on the phone. Since then, I haven't experienced any disconnect. This may be a temporary workaround for some of you but still work in progress.
Speed issues: a few of you have reported horrible speeds. There are quite a lot of reports, too many for me to respond individually. We are trying to assess if it is a modem issue, an incompatibility issue or a core network or peering problem. In order to triage the results, would it be possible for customers affected to perform the following:
Report the following information:
I understand that speedcheck.rogers.com may not give you the best top speeds but it will help us determine where the issue lies. Also, step 1 and 2 above are quite important at this point of the investigation.
Thank you all for your assistance.
Trying to understand if I should be replacing the 3552 with the new CODA or wait?
3552 has been very stable, even if the latency isn't amazing.
Speed test shows ~860/40.
Speeds and ping have been alot better since I've upgraded to the CODA modem. I haven't experienced any of the issues mentioned here so far...