05-31-2016 08:39 AM - last edited on 01-27-2017 01:23 PM by RogersRoland
Hello Community,
The Rogers Community Forums has always played an important role in providing important feedback regarding our products and services. We are excited to offer our users an opportunity to participate in a trial of the new firmware for our Rocket Wi-Fi Modem (CGN3ACSMR, CGN3ACR and CGN3AMR) and Rocket Gigabit Wi-Fi Modem (CGN3552 and CODA-4582). This program is exclusive to registered users of the Rogers Community Forums (space is limited).
The new firmware includes the following features and enhancements:
If you are interested in participating, please send a private message to @CommunityHelps with the subject line “Rogers Rocket Wi-Fi Modem Firmware Trial”. A member of our team will be in contact with you and provide you with further instructions.
We’re keen to receive feedback on this new firmware. Once you've received the new firmware, please provide your feedback directly in the FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial thread.
Questions regarding this program can be posted below.
***Please note - you must be a registered user of the Rogers Community Forums in order to participate. To register, please follow these steps.***
Thank you for your continued feedback and support.
02-17-2017 01:58 PM
I just noticed that my Coda modem was updated to the new .24 firmware. Is there any type of a changelog? Have any of the issues been fixed? My speeds look good but I got a "socket error" when running one of my speed tests. I have seen this before. Also my pings are a bit higher. So far it looks like they have sacrificed some latency in exchange for more speed. I will need to test this further to understand it better though.
02-18-2017 01:10 PM
@SickBeast You can check post 2 for details from this thread:
02-18-2017 07:12 PM - last edited on 02-18-2017 09:50 PM by RogersZia
CGN3ROG Port Forward & Firmware
Hi there,
I had contacted the CommunityHelps account over a week ago regarding my Fireware issue on my CGN3ROC.
This is still yet to be resolved, but my question pertains to port forwarding and whether the lack of an updated firmware is the cause of me being unable to open ports.
Note that I have tried all solutions I could find on the forums including a router reset, static IP, DHCP Reservation, disable/uninstall my antivirus, disable windows defender.
Anything that I have missed? Or am I just going to have to wait for this firmware to be updated from 4.2.4.6 to 4.2.4.7?
02-18-2017 07:35 PM - last edited on 02-18-2017 09:51 PM by RogersZia
@naztheeternal Have you sent a request to @CommunityHelps for the firmware to be updated?
02-18-2017 07:37 PM - last edited on 02-18-2017 09:51 PM by RogersZia
Yes I did, this was done 2 Mondays ago.
I am currently on Live Chat with a Rogers representative to see if they can assist with this.
02-18-2017 07:49 PM - last edited on 02-18-2017 09:51 PM by RogersZia
Alright, so the Rogers rep. stated that they were going to push the updated to my router and that I should hold the reset button for 30 seconds on the back.
Did that, no luck, still on 4.2.4.6
02-18-2017 07:58 PM - last edited on 02-18-2017 09:51 PM by RogersZia
@naztheeternal wrote:
Alright, so the Rogers rep. stated that they were going to push the updated to my router and that I should hold the reset button for 30 seconds on the back.
Did that, no luck, still on 4.2.4.6
Don't reset the modem, just leave the modem powered on and it should download the firmware without you having to reset anything. When the modem downloads/updates the firmware the lights on the front will flash and it will reset itself. After it resets I would then suggest holding the reset button on the back for about 10 seconds, then set everything back up.
If after an hour it still hasn't updated then call back and ask them to push it again, but don't reset, because as you reset it that could be when the modem was trying to download the update, and you just interrupted it. I dunno why they told you to reset when they're trying to push an update. But once the modem is updated and resets on its own, then you can factory reset by holding the reset button for 10 seconds.
02-18-2017 08:02 PM - last edited on 02-18-2017 09:52 PM by RogersZia
Will do, thanks!
I'll provide an update in a few hours.
02-18-2017 09:56 PM
Updated was pushed sucessfully.
However, port forwarding issue persists, is there a known issue with this modem? The ports were forwarded correctly until about October 2016, at which point it suddenly stopped.
02-19-2017 02:04 PM
02-19-2017 05:18 PM - edited 02-19-2017 05:29 PM
@jjdunn10Thanks, I'll have a go at that and let you know if it worked!
02-19-2017 05:33 PM - edited 02-19-2017 05:34 PM
@jjdunn10Well no luck with that, set up the port forwarding (3659~3659 on UDP/TCP for the correct LAN IP), turned UPNP off, DMZ off and DHCP reservation on.
Still getting the error from the servers I try to join "Check your network connection and make sure that port 3659 (UDP) is open."
02-20-2017 11:17 AM
02-20-2017 11:35 AM - edited 02-20-2017 11:35 AM
Are you sure you port forwarded it correctly to the LAN IP? It's common to have your LAN IP change every once in a while, which could be why it isn't opening the port for your device.
I'm assuming you did the command prompt method (ipconfig) to find your IPv4 address?
One more thing, that port you're opening sounds really familiar to me- for what game are you opening this port for?
02-20-2017 06:41 PM
@jjdunn10 How would I go about requesting a different router? I presume I'd have to go through Rogers Support and argue my case?
@RyzenFX Yep, looked up my IPv4 address and have set a DHCP reservation so this machine is always on that LAN IP. It a port for Battlefield 4, worked perfectly until one random moment in October, haven't been able to play since.
Asked in the BF4 reddit for support as well, all the things I've tried below:
02-20-2017 06:53 PM
It could just be an issue with the modem itself. What plan are you on? In order to upgrade to a CODA-4582 you must be on the Ignite 100u plan and above.
02-20-2017 07:25 PM
02-20-2017 07:44 PM - edited 02-20-2017 07:45 PM
@naztheeternal all you have to do is swap the modem at the nearest Rogers store. Be aware that with an unlimited plan you should be eligible for the new CODA-4582, but, also be aware that its a work in progress. Firmware version 2.0.10.24 for that modem seems to be producing good results and there is a good chance that it will be distributed network wide later this week. The CGN3ACSMR with V4.5.8.27 is stable but suffers from the Puma 6 / 6MG latency problem. The 4582 does not have that problem, so, in terms of gaming, the 4582 should be a better choice.
In both cases the modem suffer from UDP throughput issues. This is important due to the use of UDP in gaming and in DNS lookups. The 4582 does much better in the GRC DNS performance check despite the UDP throughput issue.
So, a little confusing perhaps, but in both cases, Intel, Hitron and Rogers are working towards solutions to resolve latency for the CNG3xxx series modems and UDP losses for both modems. My bet for now is with the 4582.
02-21-2017 06:21 PM
@Datalink Thanks for the great info, much appreciated.
I will attend my local Rogers store and get this swapped out, at which point I'll return with the results.
02-22-2017 03:35 PM
@Datalink @CommunityHelps @RogersDave
Hi,
I just updated to .24 and performed a full reboot afterwards and regret to inform that it is just as slow as it was previously on .19 I had 500Mbps for about 5 minutes before it dropped back to 2MBps consistently:
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 615000000 | 256QAM | -0.800 | 11 | 38.983 |
2 | 561000000 | 256QAM | -0.600 | 2 | 38.983 |
3 | 567000000 | 256QAM | -1.000 | 3 | 38.605 |
4 | 573000000 | 256QAM | -0.800 | 4 | 38.605 |
5 | 579000000 | 256QAM | -1.000 | 5 | 38.983 |
6 | 585000000 | 256QAM | -0.900 | 6 | 38.983 |
7 | 591000000 | 256QAM | -0.800 | 7 | 38.605 |
8 | 597000000 | 256QAM | -0.900 | 8 | 38.983 |
9 | 603000000 | 256QAM | -1.200 | 9 | 38.605 |
10 | 609000000 | 256QAM | -1.100 | 10 | 38.983 |
11 | 555000000 | 256QAM | -0.900 | 1 | 38.605 |
12 | 621000000 | 256QAM | -1.200 | 12 | 38.983 |
13 | 633000000 | 256QAM | -0.900 | 13 | 38.983 |
14 | 639000000 | 256QAM | -1.000 | 14 | 38.605 |
15 | 645000000 | 256QAM | -0.400 | 15 | 38.605 |
16 | 651000000 | 256QAM | -0.800 | 16 | 38.605 |
17 | 657000000 | 256QAM | -0.400 | 17 | 38.983 |
18 | 663000000 | 256QAM | -0.100 | 18 | 38.983 |
19 | 669000000 | 256QAM | -0.100 | 19 | 40.366 |
20 | 675000000 | 256QAM | -0.600 | 20 | 38.983 |
21 | 681000000 | 256QAM | -0.900 | 21 | 38.983 |
22 | 687000000 | 256QAM | -0.900 | 22 | 38.605 |
23 | 693000000 | 256QAM | -0.700 | 23 | 38.983 |
24 | 699000000 | 256QAM | -0.800 | 24 | 38.605 |
25 | 705000000 | 256QAM | -1.400 | 25 | 38.605 |
26 | 711000000 | 256QAM | -1.100 | 26 | 38.983 |
27 | 717000000 | 256QAM | -1.200 | 27 | 38.605 |
28 | 723000000 | 256QAM | -1.100 | 28 | 38.605 |
29 | 825000000 | 256QAM | -2.000 | 29 | 38.983 |
30 | 831000000 | 256QAM | -2.000 | 30 | 38.983 |
31 | 837000000 | 256QAM | -2.500 | 31 | 38.605 |
32 | 843000000 | 256QAM | -2.600 | 32 | 38.605 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | NA | NA | NO | NO | NO | NA |
1 | 4K | 275600000 | YES | YES | YES | -0.599998 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 38595805 | ATDMA - 64QAM | 37.500 | 3 | 3200000 |
2 | 30596000 | ATDMA - 64QAM | 35.500 | 1 | 6400000 |
3 | 23700000 | ATDMA - 64QAM | 34.250 | 2 | 6400000 |
Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
0 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
1 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
02-22-2017 06:34 PM
Great news! The CODA-4582 switch resulted in success!
Port forwading works and I can access all the game servers.
Thank you all for your help!