Rogers Rocket Wi-Fi Modem – Firmware Trial

[RogersMargaret]

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:

• IPv6 enabled by default
• Security enhancements
• Fix to preserve LAN connectivity in case of HFC outage or loss of signal
• Addition of Wi-Fi Survey functionality
• Improved stability of WPS function
• Improved Wi-Fi performance
• Various minor GUI changes and improvements

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.

[lethalsniper]

Yea I have disabled IPv6 on laptop and did all 3 flushes still getting server not found page. It works then I get that message.

[Datalink]

So with IPV6 disabled, your laptop won't connect to the modem??  Or, it connects to the modem and won't go anywhere on the internet?

[lethalsniper]

[lethalsniper]

It connects can browse the internet but after a few times searching the web I get just loading then I get the page saying server not found

[Datalink]

Ok, so it looks like you're using a TP-Link router for wifi, not the Hitron modem.  

Are you running the modem in Bridge mode, as in confirmed that the BASIC .... GATEWAY FUNCTION ..... Residential Gateway Function is disabled? If not you would have a double NAT situation going, which could cause a number of problems.  

Using the TP-LINK router would bypass the problem of the Hitron modem's Beacon transmission problem.  

With the modem in Bridge mode, that would seem to place the problem between the router and the laptop.

What model of TP-Link router are you using?

Do you have IPV6 disabled in the router?

If you look at your image, you can see an SSID titled Searching...   If you look at the next SSID below that it's a hidden SSID transmitting on the same channel.  The next SSID below that is Searching...-guest.   That appears to be a good example of the Hitron's hidden SSID beacon that is running now.  But, as I indicated above, using the TP-Link router would get rid of that problem. 

[lethalsniper]

I bridged rogers modem because I thought maybe it was the wireless function on the modem so I'm using the tplink router but it's also doing same thing on gateway mode on cgn3acmsr , no IPv6 is disabled, model tplink ac1750

[Datalink]

Is this the correct router?

http://www.tp-link.com/en/products/details/cat-9_Archer-C7.html

And is it a version  - V1, V2 or V3?

Have a look at the following thread to see how to determine which version it is:

http://www.tp-link.com/en/faq-46.html

[lethalsniper]

Yes

[lethalsniper]

V2

[Datalink]

Ok, just looking at the manual for the V2 at page 101 to 103.  To avoid getting into the intracacies of IPV6 DHCP versus SLAAC and the other settings (I'll have to do a little research here), disable IPV6 in the router altogether.  That is shown on page 103.  Disable the IPV6 selection in the WAN Setup, save the setting and then reboot the router.  When that reboot is underway, reboot the laptop as well.  You could in theory enable IPV6 in the laptop to allow local IPV6 addresses.  With IPV6 disabled in the router, you should be back at square one, as in prior to the day that IPV6 was available on the modem, either by enabling by Rogers across the network, or, due to the update to .22.

[lethalsniper]

IPv6 was already disabled on router settings. Can it be any chance that laptop wireless card is not capable with my rogers modem or tplink router since the new update 22 ? But just weird I have no issues at all on wireless connection when on my sisters connection which she is also with rogers but on the cgn3 modem with a firmware ending with .7 ? This is so annoying

[Datalink]

There shouldn't be any issues between the modem and the router, however, I've seen a couple of other posts indicate problems that have come up since .22 was released across the network.  I would think that with IPv6 already disabled in the router, you would avoid any problems with it.  The downside of that is the effect that has on XBox's.  Disabling IPV6 cuts off one possible gaming path for the XBox and forces it to use IPV4 or Toredo.  With IPV4 you run into NAT issues.  With IPV6 you avoid the NAT issues.  

The one thing that I would do is change the wifi 5Ghz channel to 149 or higher.  There is already another network in that upper range, so you would have to select a channel that wouldn't conflict with it.  The lower 5 Ghz channels are restricted to 50 milli-watts or 200 milli-watts depending on when that router was approved by Industry Canada, but, the upper channels are allowed to broadcast using 1 Watt.  So, there is a considerable difference in power levels, and therefore the signal to noise ratios and data rates.

Do you normally connect with the 5 Ghz or 2.4 Ghz?

On the laptop can you navigate to START .... CONTROL PANEL .... DEVICE MANAGE .... NETWORK ADAPTERS.  Expand the Network Adapter's so that you can see the specific adapter details.  Please copy the full wifi adapter title and paste it into a post.  With that I can look up the specs for the wifi card.

Can you also post the exact model of the laptop, once again to look up the specs.  

[lethalsniper]

we normally connect with 2.4 but trying with 5ghz still no luck,  Model  acer aspire  model# v3-551-x630

[Datalink]

Ok, just to recap,

Laptop: acer aspire model # v3-551-x630

Wifi Card: Qualcomm Atheros AR5WB222 with Driver 3.0.2.201

Looking around the net, that particular laptop is not supported by Acer for Windows 10, so, what you end up with in terms of drivers is anyone's guess. Looking at other older pc's it looks as it Microsoft has cooked Windows 10 to accept older Windows 7 and 8 drivers, so I'm guessing that the laptop possibly goes back as far as Windows 7.

The disconnects happen on when connected to the modem in Gateway mode and when connected to the router, so, that really takes the modem's version 4.5.8.22 out of the picture. I know that there have been MIcrosoft updates recently as well, so, which is the real culprit? My bet would be with the Windows updates.

That wifi card has a history of disconnects. This appears to be the best way to resolve it: navigate to START .... CONTROL PANEL .... DEVICE MANAGER .... NETWORK ADAPATERS. Right click on the wifi adapter to bring up the properties panel. Select Change Settings to bring up the Controller Properties panel. Select Power Management. Uncheck the selection for "Allow the computer to turn off this device to save power."

In addition to that, within that panel, navigate to the Advanced tab. Have a look for any selection titled Power Save, or Power Save Polling or PSP. If that is there, disable it. That function is designed to reduce the power requirements for the wifi card, but, Intel and everyone else appear to have a different view on how its supposed to function.

When that is done reboot the laptop.

You could before the reboot, also look at the power plan that is currently in operation. Navigate to START .... Pc Settings .... Power & Sleep .... Additional power settings. For the plan that is currently in effect, select "Change plan settings". Go through those power settings, item by item and disable any items you deem as being "not applicable" to your particular use of the laptop.

When that is done, reboot the laptop.

With regard to the Power Save Polling, from Intel, comes the following;

http://www.intel.com/content/www/us/en/support/network-and-i-o/wireless-networking/000005645.html

Symptom(s):

The following symptoms may be seen if a Wi-Fi access point (AP) or broadband Wi-Fi router does not properly support the Power Save Polling (PSP) feature:

Intermittent loss of Wi-Fi connection
Inability to initiate a Wi-Fi connection
Poor Wi-Fi connection data performance

These symptoms may be more pronounced when on battery power.

PSP mode is a feature that provides extended battery life for notebook computers. It requires coordination between the AP or router and the Wi-Fi adapter. Intel has discovered that some APs or routers may not implement the feature correctly or completely.

Looking at your wifi card driver, its pretty old. I'm surprised that Windows hasn't updated that driver on its own. In any event, although Acer doesn't support Windows 10 on that laptop, it appears that Atheros has a Windows 10 Driver available. Have a look at this page and scroll down to the AR5WB222 line. The two right hand selections are for the Windows 32 bit driver (left) and Windows 64 bit driver (right) You could try downloading the applicable driver and see if that improves the situation if the instructions listed above to turn off any power saving function do not work. Turning those off would be my first attempt to solve this.

https://www.atheros-drivers.com/atheros-wireless-drivers.html

If you do download and install an updated driver, have a look for any power saving function in the advanced functions tab of the wifi controller and disable it. Then reboot the laptop.

Fwiw, we have an Acer laptop that is similar. I chose not to update to Windows 10 as its also not supported for Windows 10 drivers. Its intesting that Acer offered to update several models of laptops including ours, but at the same time offer no support in terms of drivers. I think they should have made a hard cut off point. Before this model date, you're out of luck, stuck with Windows 7 or 8. After that date, no problem.....

[lethalsniper]

Okay just wanted to say thanks for all your help. curiosity how come the laptop works fine at my sisters house with no disconnection issues at all only at my place with the cgn3acsmr. Other thing if I was to restore computer back to factory will it remove window 10 and bring me back to 7

[jszentir]

Good afternoon.  I have been waiting to switch from the advanced CGN3ROG to the CGN3AC.  It took a long time to find a reliable CGN3ROG so I am being cautious before switching.  I'll probably have a tech come out and install one and test it thoroughly on my network to make sure the wifi range is as good on 2.4 and the lag problems are finally gone.  Can I expect that I will get the performance I'm looking for on 2.4 and that 5 will also have the lag issue fixed?

We are totally wi-fi and don't care about LAN port problems.  We are getting 4 to 5 bars and 90 to 100mbps two floors directly overhead the basement where the router is situated.  We have two range extenders for the far corners (one on each floor), numerous laptops, cell phones, xbox, playstation and a smart TV connecting all on wi-fi.  Performance is good except for the lag problem inherent in the original CGN3's.  I don't want to lose the range I'm getting now and I want the lag problem to get fixed.

Is the CGN3AC series finally ready or should I wait?  What about the CGN3AMR?  We don't need AC, just wireless-N.

Some internal modem lag (below) showing up occasionally on our relatively quiet network at this time (version 4.2.4.6).  Similar behaviour when testing one of the LAN ports.

C:\WINDOWS\system32>ping -t 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms 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=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms 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=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=12ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=106ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=125ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=17ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms 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=62ms 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=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms 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=14ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms 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=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms 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=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms 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=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=105ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=51ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms 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=7ms 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=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms 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=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 75, Received = 75, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 125ms, Average = 10ms

[masa17188]

how can i download

[Datalink]

@lethalsniper, I missed your question regarding last week regarding a downgrade to Windows 7.   I'm not exactly sure what you will be able to do.  If you only have Windows 10 loaded, it might be possible.  If you now have Windows 10 Anniversary Update loaded, that might not be possible.  You would also have to check on Microsoft's policy on reloading back to Windows 7 after the laptop has been updated to Windows 10.  I suspect that it shouldn't be an issue, but don't quote me on that. 

If you look at your Windows File directory, on C drive, you might see a Windows.old directory, and possibly a Windows.old.old directory, which I would think is the original Windows 7 files.  What I don't know is what would happen if you chose to restore Windows.  Would it present a menu that shows Windows 7 and the original Windows 10 install?  That's something you would have to check for. 

In any event, if the Windows 10 AU has wiped out the old Windows 7 files, if you have the original licence for Windows 7, and Microsoft allows users to downgrade, you should be able to download a Windows 7 ISO onto a USB stick and reload Windows 7.  You might have to totally wipe out anything that is currently residing on C Drive first.  I'm not sure if Windows 7 will wipe everything including the backup partitions that exist with Windows 10.  If it doesn't, you would have to do that first by using something like Gparted, which is a bootable operating system that allows you to delete items off of the hard drive. 

http://gparted.org/

Having said all of that, if the laptop works well at your sisters home, I would first check the Wifi environment in your home with inSSIDer to determine if there are so many other modems and routers nearby that the 2.4 Ghz band is totally unusable.  If that's the case, then its time to move up to the 5 Ghz band and leave the traffic jam behind you. 

So, fwiw.......

[Datalink]

@masa17188, at the present time, V4.5.8.22 which was the previous test version is now the current network wide version for the CGN3ACSMR.  Further test versions are probably on hold pending further development by Hitron. 

Firmware versions can't be downloaded by the end users.  They have to be pushed out to the modem thru the CMTS.

What modem do you have, as indicated by the product sticker at the back of the modem?

[Datalink]

@jszentir, I think the answer at the present time might be to stay where you are, with your current modem.

The latency to the modem that you see now was resolved last year for the CGN3ACSMR.  It has not been resolved for the CGN3, CGN3ACR or CGN3AMR as far as I know. Now for the complications:

The firmware development from what I can see has been aimed at the CGN3ACSMR and CGNM-3552 gigabit modem.  The current network wide version for the CGN3ACSMR is V4.5.8.22.  That resolves a number of issues, the latest of which is a Chromecast problem.

The drawback to recent updates is:

1. The appearance of a hidden SSID beacon for a secondary 2.4 Ghz network which appears to drop the wifi performance of the users 2.4 Ghz network.  Removal of this beacon is on the "to do" list.

So, upgrading to a CGN3ACSMR would also come with an update to V4.5.8.22 shortly after it goes live on the network, dropping your 2.4 Ghz wifi performance.

The CGN3ACR and CGN3AMR can be loaded with 4.5.8.22 if requested, however, as far as I am aware, they, and the CGN3 are on their own update schedule.  You can choose to operate those with their current firmware versions as far as I know and avoid the problem of the hidden SSID 2.4 Ghz beacon.

One of the problems that was resolved for the CGN3ACSMR was dead LAN ports that occurred with the modem was connected to the Casa CMTS which has replaced the Cisco CMTS equipment.  I don't know if either the CGN3ACR or CGN3AMR suffered from that problem with its current firmware load. If not, then upgrading to either one of those might make some sense.  But, with respect to the latency to the modem, you wouldn't be any further ahead.

At the present time, the latency to the modem is the least of the worries with these modems.  The bigger problem is the latency thru the modem, which is much larger and which is common to all Puma 6/6MG modems. Rogers and Hitron are working pretty diligently to resolve this.  If you look at the top two to three rows of my image library you will see the high time pings back from the CMTS.  These were taken with the CGNM-3552 gigabit modem, but the other 24 channel modems aren't too far behind in terms of their latency. So, thats the current focus, to get rid of the latency thru the modem.

http://communityforums.rogers.com/t5/media/gallerypage/user-id/829158

So, I hope that makes some sense. There are issues on the go which are being addressed.  Their not resolved just yet.  What I'm hoping to see over the next few short weeks is a resolution for the latency thru the modem.  Then that occurs, then it would make sense to upgrade to the CGNM3ACSMR as the latency to and thru the modem would be resolved and hopefully the hidden SSID beacon will be taken care of as well.

Fwiw, the latency to and thru the modem isn't a Rogers or Hitron problem.  Those are issues caused by the Puma 6/6MG chipset.  That chipset is used by other manufacturers to build modems and by ISPs in the form of the finished modem products.  We're talking about numerous ISPs across North America and Europe.  Rogers however is actively working to resolve these issues and very much ahead of the game, whereas other ISPs are still in the denial stage "Nothing wrong with our equipment, its all the customers fault."  Please keep that in mind.

[jszentir]

@Datalink
Thanks for the advice. I'll leave well enough alone until things improve with the rocket modems.