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.
@Gabandara can you log into the modem and check the Software Version (Firmware) version that is shown on the STATUS page that is displayed when you log into the modem. Or, do you know already that you are running V18.104.22.168? If you have requested that version and it is loaded, please have a look at the following post for my post update instructions. Hopefully that will help if you have V22.214.171.124 loaded now:
@New_Man, since I just typed this, it seems appropriate for you as well:
1. Confirm what model of modem you have as seen by the product sticker at the back of the modem. I would think that its a CGN3XXX variation or possibly a CGNM-3552.
2. Log into the modem and navigate to the STATUS .... DOCSIS WAN page, copy the downstream and upstream tables and paste those into a post. The copy and paste process will copy the text components of the tables and paste them into a post, so using a screen capture won't be necessary.
3. Please read my post regarding the use of Pingplotter to monitor the modem to CMTS cable path to look for anomalies in the performance of that path. My personal opinion is that along with the modem, this is the most critical part of the cable internet system. Get this part right, along with the modem, and your internet performance should be rock solid. Easy for me to say as an armchair quarterback, but, with a little persistence it can be done. If you can post an image from pingplotter as is indicated in that post, between the signal levels and the image, hopefully we can start tracking down the cause of the problem with the internet service:
Please send me a pm, or to @RogersDave a copy of the line from your Docsis Events page that contains the CMTS-MAC=XX.XX.XX.XX.XX.XX and CM-MAC=XX.XX.XX.XX.XX.XX addresses. Its possible that IPV6 is not enabled for your CMTS. @RogersDave would be able to determine that. To send a pm, click or select my name or Dave's name in the link to go to the public page. On the right hand side a a link titled "Send this user a private message". Select that to go to the message composition page, fill in the title, details and hit send. Watch for a number overlaying your personal icon at the upper right hand corner when you're logged into the forum. Select the icon to bring up the next menu, then the envelope to drill down to the inbox.
The rest of my earlier post is located here:
If you're interested in looking at your wifi and house structured wiring, have a look to see if that post can help.
Thanks for the new firmware. It's been more than a week now and no reset has been required in bridge mode. It has only lost the WAN connection once, but recovered it by itself in a few minutes.
I just have one question: the original firmware version was 126.96.36.199 and in a previous post you said that a "factory reset" would be required for the upgrade; I haven't done any and things seem to work fine with 188.8.131.52 ... should I still do one, or not?
@Vlad_D I would still recommend a factory reset as that jump from .14 to .22 is a pretty big. Running the factory reset will ensure that IPV6 works properly on the modem and that your modem throughput is consistent. I've seen some interesting results where the reset had not taken place. There was an IPV6 address on the modem but IPV6 did not work properly and the speedtest results were inconsistent. For those reasons I recommend a factory reset. Moving from something like .21 to .22, not a big move, but from .14 to .22, yup, thats a big move.
@Mythen we have underground cables and our Rogers cable has been replaced twice in the last three or four years. Previous to that, the cable that was in place had been there for a number of years before dying one day. Replace the cable and we were back in business. Not a big deal to replace an underground cable. A bit of a hassle, but not a big deal.
I did the factory reset, as suggested, and reconfigured the modem in bridge mode. The internet speed definitely improved: Rogers speed test went from ~50Mbps to a bit over 100Mbps (I'm on a 100u plan).
On a different note, the "Self-Install" greeting page is annoying and buggy:
1. If the modem is not connected to Rogers, you are stuck to this page, without any way to get to the admin pages!!!
2. Why should the user be forced to set up WiFi just to disable it afterwards ...
3. It makes the user fill in a "WiFi pasword" with just a few charactes and it uses it as admin password as well, without giving you any hint for this (it took me a while to figure that one out) ... because it is short (as an admin password), the user would/should have to change the WiFi password(s) again (if WiFi is desired).
1. Put on those "Welcome" pages a button/link going directly to the admin pages ("Advanced setup", or similar), wether the modem is connected to Rogers or not !!!
2. Do not mix the admin and WiFi passwords! Leave the WiFi password field for WiFi (long password, including spaces) and leave the admin password to "password", as documented (or put a separate page/field for the admin password setup)
3. I might miss something, but this is the first time I find a WiFi password setting field (now I'm talking about the admin pages) that doesn't allow spaces! If this isn't some standards specs I'm not familiar with, please fix those password entry fields.
Thanks Rogers Dave, a man of his word let it be known.
Chiming in after almost a week of getting Dot 22.
Didnt see any improvment until two days later, did 3 factory resets to no avail.
Snippet from Docsis event log showed
SW Download INIT - Via NMS
SW download Successful - Via NMS
Then sometime after 1115 PM Sept 16 the packet gods lined up and said the man has suffered enough give him his 250 down and be done with it.
Tech was scheduled on the 17th at 10am tried to cancel but never happened, heard them banging on the wall outside and long story short.:A VOIP AMP was installed inside to tune the gain numbers to spec despite performance improvement already evident.
Now have a new ganglia that doesn fit inside the wiring cabinet anymore.
Getting the occassional drop and you can still set you atomic clock to the cycle of spikes in latency in ICMP V6Packets to the CMTS.
I'm connected to a Casa CMTS with a CGNM-3552 running the 184.108.40.206 firmware and have Gigabit internet.
This morning around 9am I got the fastest test speeds for me of 924 down and 34 up. I've never gotten a faster upload though and have an open ticket for that (but it was in the 9 range before recent maintenance).
In my test config, I'm directly connected to my PC with no router and with the modem running in bridge mode.
I tested my VPN performance right after the above test result was obtained. My issue is that the VPN performance is horrible with between 9-11 down and ~32 up. As the CTMS gets loaded throughout the day, the VPN peformance gets even worse especially on the download side.
I also tried connecting the VPN via TCP instead of UDP but it had horrible latency and jitter although download improved about 30% while upload was reduced by about 90%.
But in both instances, the VPN connection seemed slow and laggy.
Q1) Is anyone else experiencing such unsatisfactory VPN performance with this hardware?
Q2) Is there anyway to configure around the VPN performance issue?
@Datalink thanks for the reference but I have already read that thread and nothing in there really helps since I don't even get 25 down.
Also the thread is 3 months old and I was hoping for a resolution or at least a progress report about the issue.
One other thing, I also have a much slower connection through a different provider and even running the VPN through my (old) router, I get more consistent speeds that are 88-94% of the rated speed both down and up and it is more responsive.
@RogersDave anything new coming or is this beta becoming final?
Firmware 220.127.116.11T3 is schedule for deployment on CGN3ACSMR in the coming days. A test pool of subscribers were upgraded last week and if everything went well, the decision will be made today to proceed with large scale deployment.
The decision will be made after this deployment for other models.
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||BandWidth|
|1||23700000||ATDMA - 64QAM||48.750||3||6400000|
|2||30596000||ATDMA - 64QAM||48.750||2||6400000|
|3||38596000||ATDMA - 64QAM||48.750||1||3200000|
Anything newer then this? You say Firmware 18.104.22.168T3?
Does 22T3 address the issue of IPv6 not working on this site.
This has been up and down for me ever since I got the on .22 trial firmware.
i'm still getting 4/20 when I was getting 19/20 previously.
My router shows that its pulling all the IPv6 DHCP info from rogers but IPv6 seems to be down for me.
@Makaveli99, run a factory reset on the modem. I've seen an example where a CGN3ACSMR was updated but a factory reset wasn't run. The end results were just as you are seeing now. You have an IPV6 address but IPV6 testing fails. So, run the reset and confirm if that cures the situation. I've also seen flaky results from ipv6-test.com. So, I usually refresh that page a few times to ensure that I get consistent results from test to test.
I am curently on 22.214.171.124
126.96.36.199 (September 15, 2016) - Issues identified, firmware on hold
any idea when the issues will be solved ?
and should we expect that after the resolution of these issues, it will be available to all beta testers in the forum?