cancel
Showing results for 
Search instead for 
Did you mean: 

Rogers Rocket Wi-Fi Modem – Firmware Trial

RogersMargaret
Community Manager (Retired)
Community Manager (Retired)

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.

625 REPLIES 625

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

Mayoo
I plan to stick around

 

Modem also got the latest .23 pushed. 
 
I have Factory Reset the Modem
Hard Rebooted
Connected Directly to Modem even though its set in Bridge. 
 
My download speed for some reason is not passing 400mbps ( I was constantly getting ~800 with old CODA on pre .19 FW. Issue started happening from .20 on wards .. 
 
Whats going on .. missing my CGN now Smiley Sad 
 
Downstream Overview
Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	645000000	256QAM	0.100	39	38.983
2	363000000	256QAM	0.600	10	38.983
3	369000000	256QAM	0.600	11	38.983
4	375000000	256QAM	0.400	12	38.983
5	381000000	256QAM	0.700	13	38.983
6	387000000	256QAM	0.300	14	38.983
7	393000000	256QAM	-0.400	15	38.983
8	399000000	256QAM	-2.900	16	37.636
9	405000000	256QAM	-2.500	17	37.636
10	411000000	256QAM	-0.400	18	38.983
11	417000000	256QAM	0.300	19	38.605
12	423000000	256QAM	0.800	20	38.605
13	429000000	256QAM	0.600	21	38.605
14	435000000	256QAM	1.200	22	38.983
15	441000000	256QAM	1.500	23	38.983
16	447000000	256QAM	1.500	24	38.983
17	555000000	256QAM	-0.200	25	38.605
18	561000000	256QAM	0.000	26	38.605
19	567000000	256QAM	0.000	27	38.983
20	573000000	256QAM	0.000	28	38.605
21	579000000	256QAM	0.500	29	38.983
22	585000000	256QAM	0.500	30	38.983
23	591000000	256QAM	0.400	31	38.983
24	597000000	256QAM	0.100	32	38.983
25	603000000	256QAM	0.100	33	38.983
26	609000000	256QAM	-0.500	34	38.605
27	615000000	256QAM	0.000	35	38.983
28	621000000	256QAM	-0.200	36	38.983
29	633000000	256QAM	0.000	37	38.983
30	639000000	256QAM	-0.100	38	38.983
31	357000000	256QAM	0.900	9	38.983
32	651000000	256QAM	0.000	40	38.983
OFDM Downstream Overview
Receiver	FFT type	Subcarr 0 Frequency(MHz)	PLC locked	NCP locked	MDC1 locked	PLC power(dBmv)
0	NA	NA	NO	NO	NO	NA
1	NA	NA	NO	NO	NO	NA
Upstream Overview
Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Bandwidth
1	30596000	ATDMA - 64QAM	36.000	1	6400000
2	38595824	ATDMA - 64QAM	39.250	3	3200000
3	23700000	ATDMA - 64QAM	36.000	2	6400000
OFDM/OFDMA Overview
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

Ok.. So i have narrowed down the issue and found out my speeds are back to 900Mbps down / 40mbps UP between 1.30AM - 8.30AM everyday !!! 

 

So when i run Speed test at 1.30AM - 8.30AM every day, my speeds are back to 900mbps/40mbps up while rest of the hours its stuck at 400Mbps .. 

 

Is this due to Network Congestion ? My area is still  on DOCSIS 3.0 

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

dawningofwar3
I'm here a lot

had a tech come out and install new lines due to frustration of lag in games continuing and had to essentially force him outside to check the signals since he kept saying nothing was wrong problem still persists and I don't think switch the modem for another one of the same modem is the problem 😕

 

Downstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1615000000256QAM-0.4001138.605
2561000000256QAM0.300238.983
3567000000256QAM-0.100338.983
4573000000256QAM-0.200438.983
5579000000256QAM-0.400538.983
6585000000256QAM-0.400629.227
7591000000256QAM-0.200732.963
8597000000256QAM-0.400838.605
9603000000256QAM-0.500938.983
10609000000256QAM-0.7001038.983
11555000000256QAM0.600138.983
12621000000256QAM-0.4001238.983
13633000000256QAM-0.2001338.983
14639000000256QAM-0.3001438.605
15645000000256QAM-0.4001538.605
16651000000256QAM-0.4001638.983
17657000000256QAM-0.2001738.605
18663000000256QAM-0.3001838.605
19669000000256QAM-0.3001938.983
20675000000256QAM0.0002038.983
21681000000256QAM0.0002138.605
22687000000256QAM0.4002238.983
23693000000256QAM0.3002338.983
24699000000256QAM0.2002438.605
25705000000256QAM0.1002538.983
26711000000256QAM0.1002638.983
27717000000256QAM-0.1002738.983
28723000000256QAM-0.5002838.605
29825000000256QAM-2.7002937.936
30831000000256QAM-3.0003037.636
31837000000256QAM-3.1003137.356
32843000000256QAM-3.5003237.356
OFDM Downstream Overview
ReceiverFFT typeSubcarr 0 Frequency(MHz)PLC lockedNCP lockedMDC1 lockedPLC power(dBmv)
0NANANONONONA
14K275600000YESYESYES0.700001
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandwidth
123700000ATDMA - 64QAM37.75026400000
238595726ATDMA - 64QAM43.00033200000
330596000ATDMA - 64QAM39.25016400000
OFDM/OFDMA Overview
Channel IndexStatelin Digital AttDigital AttBW (sc's*fft)Report PowerReport Power1_6FFT Size
0DISABLED0.50000.00000.0000-inf-1.00004K
1DISABLED0.50000.00000.0000-inf-1.00004K

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

Which games. Your levels look really good

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

any games I literally lag in every game i play that requires online mainly league of legends and diablo 3 its usually only 2-4 seconds but its consistent not just once every couple of hours

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

jjdunn10
I plan to stick around
Since the coda is new and all, I would try going to get the cgn modem and see if that works better now. I seen your signal was low but now they look fine, so maybe the last modem was affected by the signals.

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

AOD999
I plan to stick around
In my case the coda improved my upstream signal issue that I was having.

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

@dawningofwar3 can you try the following, which is to ping the CMTS that your modem is connected to:

 

1.  Bring up a command prompt and enter:  tracert www.google.ca

2.  If the modem is running in Gateway mode and the pc is directly connected, the first IP address should be 192.168.0.1.  The next address will be the CMTS IP address.

3.  Using that 2nd line IP address, enter the following command:  ping xxx.xxx.xxx.xxx -n 100

4.  When that is done, right click at the top title bar of the command box, select Edit ...... Select All

5.  Right click in the top title bar of the command box again and select Edit .... Copy to copy the contents of the command box to the clipboard

6.  Then paste that into a post using Ctrl V

 

Please post those results.  I'm curious at this point what the time to the CMTS looks like as your modem is running Docsis 3.1, so, the ping time to the CMTS should be pretty good.  I don't have 3.1 running yet so I have to do this by looking at other users results.  I might come back and ask for a longer ping time.  If so, I'll let you know.

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

here is mine pinging CMTS

 

with 32 bytes of data:
Reply from 174.115.36.1: bytes=32 time=21ms TTL=63
Reply from 174.115.36.1: bytes=32 time=14ms TTL=63
Reply from 174.115.36.1: bytes=32 time=11ms TTL=63
Reply from 174.115.36.1: bytes=32 time=7ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=15ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=17ms TTL=63
Reply from 174.115.36.1: bytes=32 time=8ms TTL=63
Reply from 174.115.36.1: bytes=32 time=21ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=8ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=8ms TTL=63
Reply from 174.115.36.1: bytes=32 time=11ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=7ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=7ms TTL=63
Reply from 174.115.36.1: bytes=32 time=13ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=7ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=12ms TTL=63
Reply from 174.115.36.1: bytes=32 time=51ms TTL=63
Reply from 174.115.36.1: bytes=32 time=11ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=26ms TTL=63
Reply from 174.115.36.1: bytes=32 time=12ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=33ms TTL=63
Reply from 174.115.36.1: bytes=32 time=13ms TTL=63
Reply from 174.115.36.1: bytes=32 time=76ms TTL=63
Reply from 174.115.36.1: bytes=32 time=12ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=11ms TTL=63
Reply from 174.115.36.1: bytes=32 time=8ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=32ms TTL=63
Reply from 174.115.36.1: bytes=32 time=7ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=22ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=8ms TTL=63
Reply from 174.115.36.1: bytes=32 time=15ms TTL=63
Reply from 174.115.36.1: bytes=32 time=12ms TTL=63
Reply from 174.115.36.1: bytes=32 time=8ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=15ms TTL=63
Reply from 174.115.36.1: bytes=32 time=5ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=8ms TTL=63
Reply from 174.115.36.1: bytes=32 time=8ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=13ms TTL=63
Reply from 174.115.36.1: bytes=32 time=11ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=13ms TTL=63
Reply from 174.115.36.1: bytes=32 time=30ms TTL=63
Reply from 174.115.36.1: bytes=32 time=15ms TTL=63
Reply from 174.115.36.1: bytes=32 time=7ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=8ms TTL=63
Reply from 174.115.36.1: bytes=32 time=8ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=18ms TTL=63
Reply from 174.115.36.1: bytes=32 time=13ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=10ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=11ms TTL=63
Reply from 174.115.36.1: bytes=32 time=11ms TTL=63
Reply from 174.115.36.1: bytes=32 time=8ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=18ms TTL=63
Reply from 174.115.36.1: bytes=32 time=13ms TTL=63
Reply from 174.115.36.1: bytes=32 time=8ms TTL=63
Reply from 174.115.36.1: bytes=32 time=17ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63
Reply from 174.115.36.1: bytes=32 time=9ms TTL=63

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

 

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

here are the results:

 

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\derek>tracert www.google.ca

Tracing route to www.google.ca [172.217.0.163]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 35 ms 11 ms 10 ms 99.254.232.1
3 41 ms 15 ms 23 ms 67.231.222.185
4 55 ms 15 ms 15 ms 209.148.230.117
5 44 ms 17 ms 28 ms 209.148.230.10
6 10 ms 12 ms 17 ms 72.14.222.87
7 14 ms 10 ms 12 ms 209.85.255.232
8 12 ms 11 ms 14 ms 72.14.239.73
9 9 ms 11 ms 11 ms yyz08s10-in-f163.1e100.net [172.217.0.163]

Trace complete.

C:\Users\derek>ping 99.254.232.1 -n 100

Pinging 99.254.232.1 with 32 bytes of data:
Reply from 99.254.232.1: bytes=32 time=30ms TTL=63
Reply from 99.254.232.1: bytes=32 time=11ms TTL=63
Reply from 99.254.232.1: bytes=32 time=10ms TTL=63
Reply from 99.254.232.1: bytes=32 time=14ms TTL=63
Reply from 99.254.232.1: bytes=32 time=25ms TTL=63
Reply from 99.254.232.1: bytes=32 time=50ms TTL=63
Reply from 99.254.232.1: bytes=32 time=18ms TTL=63
Reply from 99.254.232.1: bytes=32 time=11ms TTL=63
Reply from 99.254.232.1: bytes=32 time=20ms TTL=63
Reply from 99.254.232.1: bytes=32 time=13ms TTL=63
Reply from 99.254.232.1: bytes=32 time=42ms TTL=63
Reply from 99.254.232.1: bytes=32 time=11ms TTL=63
Reply from 99.254.232.1: bytes=32 time=60ms TTL=63
Reply from 99.254.232.1: bytes=32 time=12ms TTL=63
Reply from 99.254.232.1: bytes=32 time=17ms TTL=63
Reply from 99.254.232.1: bytes=32 time=11ms TTL=63
Reply from 99.254.232.1: bytes=32 time=11ms TTL=63
Reply from 99.254.232.1: bytes=32 time=16ms TTL=63
Reply from 99.254.232.1: bytes=32 time=28ms TTL=63
Reply from 99.254.232.1: bytes=32 time=14ms TTL=63
Reply from 99.254.232.1: bytes=32 time=23ms TTL=63
Reply from 99.254.232.1: bytes=32 time=10ms TTL=63
Reply from 99.254.232.1: bytes=32 time=34ms TTL=63
Reply from 99.254.232.1: bytes=32 time=58ms TTL=63
Reply from 99.254.232.1: bytes=32 time=68ms TTL=63
Request timed out.
Reply from 99.254.232.1: bytes=32 time=50ms TTL=63
Reply from 99.254.232.1: bytes=32 time=10ms TTL=63
Reply from 99.254.232.1: bytes=32 time=25ms TTL=63
Reply from 99.254.232.1: bytes=32 time=16ms TTL=63
Reply from 99.254.232.1: bytes=32 time=97ms TTL=63
Reply from 99.254.232.1: bytes=32 time=29ms TTL=63
Reply from 99.254.232.1: bytes=32 time=63ms TTL=63
Reply from 99.254.232.1: bytes=32 time=13ms TTL=63
Reply from 99.254.232.1: bytes=32 time=56ms TTL=63
Reply from 99.254.232.1: bytes=32 time=42ms TTL=63
Reply from 99.254.232.1: bytes=32 time=18ms TTL=63
Reply from 99.254.232.1: bytes=32 time=106ms TTL=63
Reply from 99.254.232.1: bytes=32 time=48ms TTL=63
Reply from 99.254.232.1: bytes=32 time=149ms TTL=63
Reply from 99.254.232.1: bytes=32 time=19ms TTL=63
Reply from 99.254.232.1: bytes=32 time=25ms TTL=63
Reply from 99.254.232.1: bytes=32 time=13ms TTL=63
Reply from 99.254.232.1: bytes=32 time=12ms TTL=63
Reply from 99.254.232.1: bytes=32 time=49ms TTL=63
Reply from 99.254.232.1: bytes=32 time=9ms TTL=63
Reply from 99.254.232.1: bytes=32 time=37ms TTL=63
Reply from 99.254.232.1: bytes=32 time=12ms TTL=63
Reply from 99.254.232.1: bytes=32 time=13ms TTL=63
Reply from 99.254.232.1: bytes=32 time=19ms TTL=63
Reply from 99.254.232.1: bytes=32 time=17ms TTL=63
Reply from 99.254.232.1: bytes=32 time=27ms TTL=63
Reply from 99.254.232.1: bytes=32 time=12ms TTL=63
Reply from 99.254.232.1: bytes=32 time=13ms TTL=63
Reply from 99.254.232.1: bytes=32 time=18ms TTL=63
Reply from 99.254.232.1: bytes=32 time=22ms TTL=63
Reply from 99.254.232.1: bytes=32 time=31ms TTL=63
Reply from 99.254.232.1: bytes=32 time=17ms TTL=63
Reply from 99.254.232.1: bytes=32 time=10ms TTL=63
Reply from 99.254.232.1: bytes=32 time=44ms TTL=63
Reply from 99.254.232.1: bytes=32 time=11ms TTL=63
Reply from 99.254.232.1: bytes=32 time=26ms TTL=63
Reply from 99.254.232.1: bytes=32 time=14ms TTL=63
Reply from 99.254.232.1: bytes=32 time=38ms TTL=63
Reply from 99.254.232.1: bytes=32 time=20ms TTL=63
Reply from 99.254.232.1: bytes=32 time=9ms TTL=63
Reply from 99.254.232.1: bytes=32 time=18ms TTL=63
Reply from 99.254.232.1: bytes=32 time=66ms TTL=63
Reply from 99.254.232.1: bytes=32 time=42ms TTL=63
Reply from 99.254.232.1: bytes=32 time=16ms TTL=63
Reply from 99.254.232.1: bytes=32 time=8ms TTL=63
Reply from 99.254.232.1: bytes=32 time=35ms TTL=63
Reply from 99.254.232.1: bytes=32 time=23ms TTL=63
Reply from 99.254.232.1: bytes=32 time=22ms TTL=63
Reply from 99.254.232.1: bytes=32 time=43ms TTL=63
Reply from 99.254.232.1: bytes=32 time=36ms TTL=63
Reply from 99.254.232.1: bytes=32 time=9ms TTL=63
Reply from 99.254.232.1: bytes=32 time=11ms TTL=63
Reply from 99.254.232.1: bytes=32 time=11ms TTL=63
Reply from 99.254.232.1: bytes=32 time=47ms TTL=63
Reply from 99.254.232.1: bytes=32 time=35ms TTL=63
Reply from 99.254.232.1: bytes=32 time=15ms TTL=63
Reply from 99.254.232.1: bytes=32 time=49ms TTL=63
Reply from 99.254.232.1: bytes=32 time=45ms TTL=63
Reply from 99.254.232.1: bytes=32 time=40ms TTL=63
Reply from 99.254.232.1: bytes=32 time=10ms TTL=63
Reply from 99.254.232.1: bytes=32 time=22ms TTL=63
Reply from 99.254.232.1: bytes=32 time=10ms TTL=63
Reply from 99.254.232.1: bytes=32 time=9ms TTL=63
Reply from 99.254.232.1: bytes=32 time=21ms TTL=63
Reply from 99.254.232.1: bytes=32 time=13ms TTL=63
Reply from 99.254.232.1: bytes=32 time=16ms TTL=63
Reply from 99.254.232.1: bytes=32 time=10ms TTL=63
Reply from 99.254.232.1: bytes=32 time=11ms TTL=63
Reply from 99.254.232.1: bytes=32 time=12ms TTL=63
Reply from 99.254.232.1: bytes=32 time=11ms TTL=63
Reply from 99.254.232.1: bytes=32 time=16ms TTL=63
Reply from 99.254.232.1: bytes=32 time=18ms TTL=63
Reply from 99.254.232.1: bytes=32 time=9ms TTL=63
Reply from 99.254.232.1: bytes=32 time=8ms TTL=63

Ping statistics for 99.254.232.1:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 149ms, Average = 26ms

 

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

@lethalsniper thats not bad at all.  You're running Docsis 3.1?  Can you change the command to 1000 pings,  -n 1000.  When that is complete can you post just the bottom results section, like this:

 

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

 

Edit:  here are the instuctions for pingplotter, which will allow to you monitor the pc to CMTS path.

 

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

 

Set pingplotter to run at 1 second intervals. Are you on an unlimited internet plan?

 

That instruction uses Pingplotter, however, Pingplotter averages the data when you step up to higher time periods for the display, wiping out the higher time pings.  You could essentially do the same thing with Multiping, which is a point to point ping instead of a total path ping.  The advantage is that Multiping apparently has a selectable display to show the averaged data or the Min/Max data, which is useful when it comes to observing the high time ping data.

 

https://www.multiping.com/

 

The one differerence is that you would have to run the trace to find the CMTS address by using a command line instead of Multiping. 

 

So, that is food for thought. 

 

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

@dawningofwar3, ok, packet loss and a couple of higher time pings.  If you're on an unlimited internet plan, I would suggest running pingplotter with 1 second intervals.  Here are the instructions to do that:

 

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

 

That instruction uses Pingplotter, however, Pingplotter averages the data when you step up to higher time periods for the display, wiping out the higher time pings.  You could essentially do the same thing with Multiping, which is a point to point ping instead of a total path ping.  The advantage is that Multiping apparently has a selectable display to show the averaged data or the Min/Max data, which is useful when it comes to observing the high time ping data.

 

https://www.multiping.com/

 

The one differerence is that you would have to run the trace to find the CMTS address by using a command line instead of Multiping. 

 

So, that is food for thought. 

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

@Datalink yes im on 3.1 i ran another but only 500

 

Packets: Sent = 550, Received = 550, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 48ms, Average = 12ms

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

Thats not a bad result for this time of day.

 

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

@Datalink here are said results from pingplotter following the steps

 

pingplotter.png

 

 

pingplotter 2.png

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

@dawningofwar3 if you're on an unlimited plan keep that running and keep an eye out for times when you are seeing more packet loss events.  When that happens, and if its ongoing, call tech support and advise the CSR that your seeing packet loss occur.  Ask him or her to ping the modem, or ping the CMTS from the modem, looking specifically for packet loss events.  When you see packet loss occur, the CSR should see it at the same time.  The next question is, is this an issue for your modem only, or are your neighbours, who are connected to the same tap also affected.  Ask the CSR to check those modems as well.  That will hopefully narrow down the possible cause and get the right tech assigned to investigate the problem.  If you don't want to run pingplotter on a continuous basis for a day or two, run it during times when you know that the packet loss normally occurs.  Fwiw, running pingplotter for a week will tell you what the response times are during the week.  Each day is a little different from the rest.  Typically you will see a quiet overnight period after 1 am, running up to around 8 am, slightly higher during the day with some peaks possible and then after school lets out the ping times rise.  Into the evening the ping times can rise throughout the night, tapering off after the 12 to 1 am period.  Seeing the results will give you some idea of whats normal and what isn't. 

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

SickBeast
I plan to stick around

I'm finding that there is some kind of peak hours congestion or something.  During the week every evening I was only getting 100-300mbps down, however this morning (Saturday) I'm getting over 800mbps down.  Is there some type of congestion issue or throttling going on during peak hours?

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial


@SickBeast wrote:

I'm finding that there is some kind of peak hours congestion or something.  During the week every evening I was only getting 100-300mbps down, however this morning (Saturday) I'm getting over 800mbps down.  Is there some type of congestion issue or throttling going on during peak hours?


Rogers does not throttle the network, what you are seeing is indeed congestion. We're hoping that in the next month or two that all areas will be upgrade to DOCSIS 3.1 which offers more bandwith. 

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

dgelman
I plan to stick around

@RogersMargaret

 

Hello, I have a new CGNM-3552-ROG with software version 4.5.8.21. Upon recieving this new modem, my Chromecast refuses to connect the modem and requests that I disable AP isolation. Rogers Chat was unable to help me with this problem. It looks like this trial firmware may help.

 

Can you please add me to the trial or assist me in my problem.

 

Regards,

 

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

dgelman
I plan to stick around

Hello,

 

I recently recieved a Hitron CGNM-3552-ROG (ver. 4.5.8.21).

 

Once I got the modem and set it up, I realized my Chromecast (Gen. 1), which I have had for years cannot connect to WiFi and requests that I disable AP Isolation. I do not know where this option is on my modem settings.

 

This problem is not new, I have tried many solutions online. This didn't work and this solution destroyed my internet acces via LAN requiring a factory reset on the modem.

 

If anyone has some input, please let me know, this is frustrating.

 

Regards,

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

gp-se
I'm an advisor

@dgelman wrote:

@RogersMargaret

 

Hello, I have a new CGNM-3552-ROG with software version 4.5.8.21. Upon recieving this new modem, my Chromecast refuses to connect the modem and requests that I disable AP isolation. Rogers Chat was unable to help me with this problem. It looks like this trial firmware may help.

 

Can you please add me to the trial or assist me in my problem.

 

Regards,

 


The modem will update itself in 24-48 hours to the latest network release, which should be version .22

This includes the Chromecast fix.

 

If you want to be apart of the beta program you need to send a PM to @CommunityHelps

They will give you instructions on how to sign up.

 

Re: Rogers Rocket Wi-Fi Modem – Firmware Trial

@dgelman if the modem does not update to .22 within 48 to 72 hours, have a look at message # 471 (top post) on the following page for instructions on requesting 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.