FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

[RogersMargaret]

Hello Community,

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.

[noziel]

Thanks Dave

In my case, that am in bridge mode on ignite 100. Do you recommend I hold off from resetting the modem until you have more info in two weeks time? Also those that are not experiencing the issues would be nice to know there modem hardware version. I believe there is A1 and B1 for the ACSMR.

[Eleonore]

Hi,

How do I get this firmware upgrade. A Sr Technician was at my place yesterday and suggested I need it very badly. The ticket he opened is: C116978679. I am on CGNM-3552, version 4.5.8.19 still.

Thanks,

Eleonore.

[Datalink]

Hi @Eleonore  have a look at message # 471 (top post) on the following page for instructions on requesting the trial version, 4.5.8.22.

http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/message-id/348...

When you are sending the private message as indicated in that post, also log into your modem and copy the HFC MAC address and modem Serial number and paste that into the message.  The HFC MAC Address and modem Serial Number can be found on the STATUS page that is displayed when you log into the modem.  The Cable Modem MAC Address and S/N can also be found on the back of the modem.

[RogersDave]

@jramsay7269, @Eleonore

To request the update, have a look at message # 471 (top post) on the following page for instructions on requesting the trial version, 4.5.8.22T3 or 4.5.8.27 depending on your modem model.
 
http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/message-id/348...
 
When you are sending the private message as indicated in that post, also log into your modem and copy the HFC MAC address and modem Serial number and paste that into the message. The HFC MAC Address and modem Serial Number can be found on the STATUS page that is displayed when you log into the modem. The Cable Modem MAC Address and S/N can also be found on the back of the modem.

Dave

[Eleonore]

Thanks. Private message sent.

[bcharters]

Thanks blues_clues - brilliant advice about avoiding the cursed 192.168.0.2 IP address - My server address was set to static IP 192.168.0.2 and I have been getting flakely connection since the summer - sometimes it works, sometimes it doesn't.   I took your advice and changed it's static IP to 192.168.0.3 on Wednesday and connectivity has been perfect ever since.    It's a real shame that Rogers can have a serious issue like having some hidden impact on a single IP address like 192.168.0.2 and not disclose it in a very public way.  Is there any active investigation about the 1192.168.0.2 Ghost Network Issue?

I'd estimate that I've wasted more than 10 hours over the past couple of months trying to figure out why the connection was intermittent - if Rogers had just been forthright with known issues like whatever the heck they are doing with 192.168.0.2 then they could save their users from many many wasted hours - very frustrating.  Rogers - communicate better please.

Thanks blues_clues for solving a major issue.   Having said that, the server still doesn't show up in the Connected Devices table on the Hitron, even through it is clearly on-line and every other IP scanner I have can see it just fine.   There is something wrong with Roger/Hotron connected devices summary. 

[noziel]

Am in bridge mode with my own router and I don't always get my full upload speed. It fluctuates since the .27. In short, this issue is not just for those in gateway.

[Eleonore]

How do I know if the upgrade have been completed and when I need to reset the modem? Will the version number change automatically? I am not  clos eto the modem and wouldn't be able to notice through lights.

[Datalink]

You would have to log into the modem and check the Software Version (firmware) that is shown on the STATUS page.  That page comes up automatically when you log into the modem.  Type in 192.168.0.1 in a web browser address bar to get to the login page, no http, or www, just the numbers. 

If you are around when it updates, the front LEDs will go out.  Don't panic.  Just let it run so that it completes the update.  It will eventually reboot back into Gateway or Bridge mode, as it is at the moment.  

[user12343543]

Is there any reason to limit things to 3 upstream channels? It was 4 a few years ago.

I think I'm being hit by connection in my area as I NEVER go about 35 mbps (often times it's ~25-30)

[Makaveli99]

---

@noziel wrote:
Thanks Dave

In my case, that am in bridge mode on ignite 100. Do you recommend I hold off from resetting the modem until you have more info in two weeks time? Also those that are not experiencing the issues would be nice to know there modem hardware version. I believe there is A1 and B1 for the ACSMR.

---

I'm not experiencing slow uploads and that is my hardware version above.

[noziel]

Thanks for the info, my hardware version is 1A.  Now it's best for Dave to determine what is the major differences between 1A and 2A.  Also determine if the other trail users that are experiencing the upload issues are those on the 1A version. If so, perhaps this can explain why some and not others experience this problem with .27.     

[lethalsniper]

I have the 1a and 27 with upload issue

[gp-se]

I've been on Gigabit for about two months now, uploads are usually around 30-35mb/s. However the past two weeks it has been very slow (9-20mb/s) but this weekend I noticed it back up to 30-35mb/s. Nothing has changed on my end, so maybe they fixed something with the Node I connect to. I just hope it stays fast and is not some intermittent issue in my neighbourhood.
Download speeds haven't been an issue, my modem is in Gateway Mode.

[azar1]

Got updated to .22 and having some problems with random high pings (was having these issues before and was hoping it would be fixed, but it didnt)

When playing a game such as Rocket League, the ball/vehicle is suddenly in a completely different area of the map, as if the connection dropped, and quickly reconnected.

I did a ping to the router and this is the result.

C:\Users\Irfan>ping 192.168.0.1 -n 50

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=20ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time=16ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=316ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=23ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=266ms TTL=64
Reply from 192.168.0.1: bytes=32 time=15ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=19ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=255ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=15ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=16ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=12ms TTL=64
Reply from 192.168.0.1: bytes=32 time=204ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=12ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=16ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=17ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=177ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 316ms, Average = 30ms

I assume this is the issue why I can't game properly, this is on a 5ghz channel and it is the only 5ghz channel near me. 

Any suggestions?

[Datalink]

Run that again via ethernet and ensure that there's no one else in the house running a download, as that will skew the results no matter what modem or router you might be using.

I would also run a factory reset if the modem was updated to .22, unless of course you have already done that.

Edit :  The results below are what I would expect to see via ethernet.  This is on a CGNM-3552 with 4.5.8.21 loaded.  The ping results that you see (via wifi) are what the ethernet ping times used to be on a CGN3ACSMR prior to 4.5.8.16, so, after that version, I would expect a modem that has been updated and had a factory reset done to look like the results shown below.  Its not perfect, but its considerably better than it used to be.  As the packet processing thru the modem is switched from the CPU to the Hardware Processor/Accelerator, I wonder if the ping times to the modem will improve as the processing load on the CPU decreases.  It will be interesting to see.

In terms of an effect on your gaming, the ping time to the modem is small in comparison to the ping time thru the modem.  V4.5.8.27 will fix the ping, but, that for IP4 ICMP ping only.  Please read my post regarding this upcoming update as well:

http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/message-id/369...

ping 192.168.100.1 -n 100

Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time=11ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=8ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=120ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63

Ping statistics for 192.168.100.1:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 120ms, Average = 2ms

[islyfox]

Hi, I have a CGN3ACSMR modem with the firmware ending in .21. I am unable to use my chromecast. Do I need my firmware to be upgraded to be able to use it?

[Datalink]

@islyfox if this is a new installation, the modem should update to 4.5.8.22 within 48 to 72 hours of it going active on the network.  If you have had the modem for longer than that, then its time to request the update.  

Have a look at message # 471 (top post) on the following page for instructions on requesting the trial version, 4.5.8.22.

http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/message-id/348...

When you are sending the private message as indicated in that post, also log into your modem and copy the HFC MAC address and modem Serial number and paste that into the message. The HFC MAC Address and modem Serial Number can be found on the STATUS page that is displayed when you log into the modem. The Cable Modem MAC Address and S/N can also be found on the back of the modem.

4.5.8.22 resolves connection problems with Chromecast devices.

[usamaa]

Hello,

I recently requested and got the trial update to the 4.5.8.22 on the CGNM-3552 on a Gigabit service. Unfortunately it made no differences to my ICMP latency issues, which had promted the trial firmware. Not sure how to request an upgrade to the 4.5.8.26 firmware since that is supposed to have some fix for it.

Thank You

[JohnBeaudin]

@usamaa

The new firmware is .27 

Send a private message to @RogersDave 

[Mythen]

Don't believe the .27 firmware is ready for the 3552 yet?