FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

[RogersMargaret]

Hello Community,

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.

[alback]

I saw that, thanks for the firmware update and for the reply.

cheers,

[RogersDave]

---

@JohnBeaudin wrote:

 Now my question is, will DOCSIS 3.1 be as good as cablelabs describe it? in terms of ping for us online gamers?

John

---

That is a complicated question and only time (and testers like you) will tell. Sorry for the below, this gets technical...

In DOCSIS 3.1, there are a few positive things. First, the gateway itself has to be more powerful and is not based on Intel Puma 6 which is known to exhibit latency issues. That will be the first major win.

DOCSIS 3.1 capable gateways are all backward compatible to DOCSIS 3.0. Before the introduction of the Broadcom BCM3390 and Intel Puma 7 chipsets (both DOCSIS 3.1 capable), the only gateways capable of operating at 32 channels were all based on the Intel Puma 6 chipset. By using D3.1 chipsets, even operating in DOCSIS 3.0 mode, it means that there will be far more modems capable of operating with 32 channels on the downlink.

Aside from that, DOCSIS 3.1 makes AQM mandatory. It is available in some DOCSIS 3.0 gateways but it is mandatory in 3.1 and that can also potentially help.

Final point is regarding modulation. DOCSIS 3.1 uses OFDM which is more resilient to noise. Also, given the higher modulation schemes, there is better efficiency in bit/Hz which leads to more capacity. This will therefore alleviate congestion, where it exists, and help with the latency as well.

DOCSIS3.1 operation mode allows to operate in hybrid mode with D3.1 on the downlink and D3.0 on the uplink and this is what most operators will deploy first. The technology for D3.1 on the uplink is not 100% mature and will be ready sometimes in 2017.

Congestion on the uplink is far more prevalent than on the downstream. Once D3.1 is available on the uplink, that will increase capacity significantly both by increasing efficiency but also allowing cable operators to use lower spectrum, typically noisier, and that D3.0 couldn’t use. This will also help with improving the latency.

Hope this provides some answers to your question.

Dave

[JohnBeaudin]

That's exactly what I was looking for, it answers all my questions.

Thanks!

[Double_K]

---

@RogersDave wrote:

In DOCSIS 3.1, there are a few positive things. First, the gateway itself has to be more powerful and is not based on Intel Puma 6 which is known to exhibit latency issues. That will be the first major win.

DOCSIS 3.1 capable gateways are all backward compatible to DOCSIS 3.0. Before the introduction of the Broadcom BCM3390 and Intel Puma 7 chipsets (both DOCSIS 3.1 capable), the only gateways capable of operating at 32 channels were all based on the Intel Puma 6 chipset. By using D3.1 chipsets, even operating in DOCSIS 3.0 mode, it means that there will be far more modems capable of operating with 32 channels on the downlink........

Dave

---

@RogersDave I think this answers my question from an earlier post: M37398 - it appears that the next modem may be a Broadcom BCM3390-based unit.  Yeah!

If you're looking for pre-deployment early field testers of the new D3.1 modem (with Rogers IPTV ) in a concurrent operation setup, please add me to the list!

[JohnBeaudin]

Also more than willing to be a Beta Tester for new modem ,  250u plan but I don't have Rogers TV.

[RogersDave]

---

@Double_K wrote:

@RogersDave I think this answers my question from an earlier post: M37398 - it appears that the next modem may be a Broadcom BCM3390-based unit.  Yeah!

If you're looking for pre-deployment early field testers of the new D3.1 modem (with Rogers IPTV ) in a concurrent operation setup, please add me to the list!

---

 "May" is the correct word here. There are now 3 chipsets capable of supporting 32 channels on the downlink, 2 of which happens to be DOCSIS 3.1 compliant:

• Intel Puma 6 (DOCSIS 3.0)
• Intel Puma 7 (DOCSIS 3.0+3.1)
• Broadcom BCM3390 (DOCSIS 3.0+3.1)

All I did was answer the question of @JohnBeaudin "what improvement to latency would DOCSIS 3.1 bring".

Unfortunately, there are no plans for a hardware beta tester program at this point.... Sorry.

[blues_clues]

Please delete this post.

[JohnBeaudin]

We will know within a few weeks I am sure.

To the person that had the idea to start this thread -> you're a genius

To the person thought about  having Dave work with us and answering your questions ect -> you're a genius

and if it's the same person, give that guy promotion please.

John,

[Double_K]

Thanks Dave, Yes "May"=Standard NDA clause to CYA  

[BS]

Very clearly put @RogersDave  Probably overly technical for some, but surprisingly I understood it all.

Thanks for all you do.

Bruce

[Hwaiting]

I recently had the .27 firmware installed on my CGN3ACR.

It was my understanding that after a reset that IPv6 should be enabled by default.  I did the reset.

I currently have the CGN3ACR in bridge mode, connected to a Netgear R7000.

Within the R7000, I had set the IPv6 setting to Autodetect and IPv6 was shown as reachable (via http://ipv6-test.com) but not anymore after waking my computer back from sleep.

Any suggestions?  Thanks.

[JohnBeaudin]

I hope Puma7 won't have the latencies issues we are experiencing with Puma6.

[Hwaiting]

---

@Hwaiting wrote:

I recently had the .27 firmware installed on my CGN3ACR.

It was my understanding that after a reset that IPv6 should be enabled by default.  I did the reset.

I currently have the CGN3ACR in bridge mode, connected to a Netgear R7000.

Within the R7000, I had set the IPv6 setting to Autodetect and IPv6 was shown as reachable (via http://ipv6-test.com) but not anymore after waking my computer back from sleep.

Any suggestions?  Thanks.

---

I think I answered my own Q.  I realized that IPv6 is not fully deployed everywhere.

While I don't see an option in my CGN3ACR menu to turn ON/OFF IPv6 (in either bridge or gateway mode, but I'm assuming it would be ON), it doesn't look like I've been assigned a WAN IPv6 address, hence the IPv6 tests failing.  It was just weird how it was working that one time.

[RogersDave]

---

@Hwaiting wrote:

---

@Hwaiting wrote:

I recently had the .27 firmware installed on my CGN3ACR.

It was my understanding that after a reset that IPv6 should be enabled by default.  I did the reset.

I currently have the CGN3ACR in bridge mode, connected to a Netgear R7000.

Within the R7000, I had set the IPv6 setting to Autodetect and IPv6 was shown as reachable (via http://ipv6-test.com) but not anymore after waking my computer back from sleep.

Any suggestions?  Thanks.

---

I think I answered my own Q.  I realized that IPv6 is not fully deployed everywhere.

While I don't see an option in my CGN3ACR menu to turn ON/OFF IPv6 (in either bridge or gateway mode, but I'm assuming it would be ON), it doesn't look like I've been assigned a WAN IPv6 address, hence the IPv6 tests failing.  It was just weird how it was working that one time.

---

Actually, IPv6 is fully deployed on the entire Rogers High-Speed Internet and Rogers Wireless footpring.

If you are using the CGN3ACR in bridge mode, it won't report any IPv6 address as you modem doesn't have an address but your router has it.

You say that ipv6-test.com was working and then not after your computer went to sleep. Are you using Windows 10 by any chance?

[Triple_Helix]

Upload Channels have gone back to 2 so I will do a Modem Reboot to see if it helps.

Downstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	615000000	256QAM	8.600	35	40.366
2	609000000	256QAM	8.500	34	40.366
3	603000000	256QAM	8.000	33	38.983
4	621000000	256QAM	8.700	36	38.983
5	633000000	256QAM	8.300	37	38.983
6	639000000	256QAM	7.500	38	38.605
7	645000000	256QAM	6.700	39	38.605
8	651000000	256QAM	6.500	40	38.605
9	657000000	256QAM	7.000	41	38.605
10	663000000	256QAM	8.100	42	38.605
11	669000000	256QAM	8.800	43	38.983
12	675000000	256QAM	9.200	44	38.605
13	681000000	256QAM	9.400	45	38.605
14	687000000	256QAM	9.400	46	38.983
15	693000000	256QAM	9.600	47	38.605
16	699000000	256QAM	8.700	48	38.605
17	705000000	256QAM	9.200	49	38.983
18	711000000	256QAM	9.400	50	38.983
19	717000000	256QAM	10.000	51	38.605
20	723000000	256QAM	10.400	52	38.983
21	825000000	256QAM	9.100	53	37.356
22	831000000	256QAM	9.900	54	37.636
23	837000000	256QAM	9.500	55	38.605
24	843000000	256QAM	8.700	56	37.636

Upstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Bandwidth
1	23700000	ATDMA - 64QAM	46.500	2	6400000
2	30596000	ATDMA - 64QAM	46.500	1	6400000

[Triple_Helix]

Yes a Reboot of the Modem brought back the 3 Upload channels. 

Downstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	615000000	256QAM	8.700	35	40.366
2	609000000	256QAM	8.500	34	40.366
3	603000000	256QAM	8.100	33	38.983
4	621000000	256QAM	8.700	36	38.983
5	633000000	256QAM	8.400	37	39.397
6	639000000	256QAM	7.500	38	38.983
7	645000000	256QAM	6.800	39	38.983
8	651000000	256QAM	6.600	40	38.605
9	657000000	256QAM	7.100	41	38.983
10	663000000	256QAM	8.100	42	38.605
11	669000000	256QAM	8.900	43	38.983
12	675000000	256QAM	9.300	44	38.983
13	681000000	256QAM	9.500	45	38.983
14	687000000	256QAM	9.500	46	38.983
15	693000000	256QAM	9.700	47	38.605
16	699000000	256QAM	8.800	48	38.605
17	705000000	256QAM	9.300	49	38.983
18	711000000	256QAM	9.500	50	38.605
19	717000000	256QAM	10.100	51	38.983
20	723000000	256QAM	10.600	52	38.983
21	825000000	256QAM	9.200	53	37.356
22	831000000	256QAM	10.000	54	37.636
23	837000000	256QAM	9.600	55	38.605
24	843000000	256QAM	8.800	56	37.356

Upstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Bandwidth
1	23700000	ATDMA - 64QAM	46.750	2	6400000
2	38596000	ATDMA - 64QAM	46.750	3	3200000
3	30596000	ATDMA - 64QAM	46.750	1	6400000

[Hwaiting]

---

@RogersDave wrote:

---

---

Actually, IPv6 is fully deployed on the entire Rogers High-Speed Internet and Rogers Wireless footpring.

If you are using the CGN3ACR in bridge mode, it won't report any IPv6 address as you modem doesn't have an address but your router has it.

You say that ipv6-test.com was working and then not after your computer went to sleep. Are you using Windows 10 by any chance?

---

I was using the CGN3ACR in bridge mode but just in case, I factory reset my modem and tried in gateway mode and I got the same unsuccessful results.

I'm back in bridge mode and after tinkering with my Router's IPv6 settings, it looks like it's working now though.  I get 19/20 through Chrome on Android and 17/20 through Chrome on Windows 10.

[Datalink]

That 17/20 is probably the result of a couple of items:

1.  Missing IPV6 host name which rogers does not supply; and

2.  Missing IPV6 ICMP.

Point one will remain as is.  Point two requires that you add an IPV6 ICMP exemption to the Windows firewall and possibly to your antivirus firewall as well.  Here's a Microsoft Technet reference.  Follow that to add an IPV6 rule.  Do that for IPV6 only, not IPV4.

https://technet.microsoft.com/en-ca/itpro/windows/keep-secure/create-an-inbound-icmp-rule

[Hwaiting]

Thanks.  I added to rule to allow IPv6 ICMP and now get 19/20.

[Hwaiting]

Upon further review, it looks like I am losing IPv6 connectivity after a short period of time (perhaps a couple of hours? - I'm in bridge mode, on .27 firmware, 1A hardware).

Rebooting the Hitron alone doesn't seem to work.  What does seem to bring it back is switching it to Gateway and then back to Bridge Mode.  I've been able to bring it back 3 times this way (once last night and twice this morning).

PS. Are there specific settings I should be using?  Right now I have my router (R7000) to Autoconfig IPv6.

[alback]

Had 2nd dropout since router updated to 4.5.8.27 yesterday.   The dropout did affect the the AC68U as my first check was to view our network.  All devices, wired and wireless were disconnected.  So I rebooted the Asus router first.  Still no Internet connection.  After I rebooted the Hitron.  (bridge mode), the internet was fine.  

Following the update, speed has remained the same as 5.4.8.16, where I am able to test download around 130 Mbps and upload at 11 Mbps using LAN connections.  Strange but my cell phone is able to achive much higher download speed tests using the 5Ghz AC bandwidth.  Even from the far end of the house.