Rogers Rocket Wi-Fi Modem – Firmware Trial

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
lethalsniper
I'm an Enthusiast
Posts: 1,009

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

Yes
lethalsniper
I'm an Enthusiast
Posts: 1,009

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

V2
Datalink
Resident Expert
Resident Expert
Posts: 7,132

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

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
I'm an Enthusiast
Posts: 1,009

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

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
Resident Expert
Resident Expert
Posts: 7,132

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

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
I'm an Enthusiast
Posts: 1,009

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

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

 

NETWORKKK.png

 

network driver.png

Datalink
Resident Expert
Resident Expert
Posts: 7,132

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

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
I'm an Enthusiast
Posts: 1,009

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

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
I'm a Regular
Posts: 272

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

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
I've Been Around
Posts: 1

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

how can i download