Rogers IPv6 Status

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

Re: Rogers IPv6 Status

The CGN3ACR requires a firmware update to operate IPV6 in Gateway mode.  At the present time its not scheduled to receive an update, however, testing underway now to resolve the Puma 6 chipset high ping issue will trickle down to modems other than the CGN3ACSMR and CGNM-3552.  That will include IPV6 cabability in Gateway mode.  

 

It will run IPV6 in Bridge mode.  In that mode you would have an IPV6 capable router behind the modem, running your network.

 

You can request the latest trial version which will resolve the IPV6 problem for you.  

 

Have a look at message # 471 (top post) on the following page for instructions on requesting the trial 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.

 

This will put your modem on the trials modem list which will receive future trial updates without further requests.

 

Or... you could probably swap the modem for a CGN3ACSMR.  That will do the same after its update is loaded.  



Highlighted
I Plan to Stick Around
Posts: 9

Re: Rogers IPv6 Status

Thanks!!!  I went and switched my CGN3ACR for the CGNM-3552, and voila, native IPv6 right out of the box!!!  Scored 19/20 at ipv6-test.com and 10/10 at test-ipv6.com.  Couldn't be more pleased!

 

Thanks all, especially RE-Datalink for the thorough responses!!!

Resident Expert
Resident Expert
Posts: 6,015

Re: Rogers IPv6 Status

@fishon, have a look at the Software Version (Firmware) that is listed on the STATUS page when you log into the modem.  Most likely its 4.5.8.19.  If so, you should request V4.5.8.22 as it will resolve the problem of dead LAN ports that can occur when the modem is connected to a Casa Systems CMTS, and it will resolve connections problems with Chromecast devices as well.  At some point in the near future I expect to see 4.5.8.22 distributed to the CGNM-3552s across the network.  In the mean time, to avoid the dead LAN port issue, you should request the update.  



Network Architect
Network Architect
Posts: 611

Re: Rogers IPv6 Status

Community,

 

I wanted to provide a quick update on Rogers' IPv6 status. We have made a lot of progress in the last 2 weeks and are still working on more.

 

Some updates on the milestones I previously provided:

  1. Dual-Stack on cellular: Enabled on 3G/LTE network from BC to Manitoba. Ontario, Québec and Atlantic coming soon.
  2. IPv6 enablement on all supported cable modems (currently a one-time factory reset is needed, this would enable all remaining devices): CGN3ACSMR modems are now enabled by default and doesn't require a factory reset anymore. Other modems will follow suit by the end of the year.
  3. IPv6-only (using 464XLAT translation for IPv4 service) on certain mobile devices: More to come on this once dual-stack is fully deployed across the country.
  4. Larger prefix delegation for cable modems (up to /56): Currently testing solution in lab.

 

As per the statistics published by APNIC, our IPv6 deployment now reaches about 45% of our Rogers Ignite subscribers. This number increased significantly in the last two weeks with the enablement of IPv6 on CGN3ACSMR modem.

 

Full APNIC statistics are available at IPv6 Per-Country Deployment for AS812: ROGERS-CABLE

 

 

 

I Plan to Stick Around
Posts: 9

Re: Rogers IPv6 Status


@RogersDave wrote:

Community,

 

I wanted to provide a quick update on Rogers' IPv6 status. We have made a lot of progress in the last 2 weeks and are still working on more.

 

Some updates on the milestones I previously provided:

  1. Dual-Stack on cellular: Enabled on 3G/LTE network from BC to Manitoba. Ontario, Québec and Atlantic coming soon.
  2. IPv6 enablement on all supported cable modems (currently a one-time factory reset is needed, this would enable all remaining devices): CGN3ACSMR modems are now enabled by default and doesn't require a factory reset anymore. Other modems will follow suit by the end of the year.
  3. IPv6-only (using 464XLAT translation for IPv4 service) on certain mobile devices: More to come on this once dual-stack is fully deployed across the country.
  4. Larger prefix delegation for cable modems (up to /56): Currently testing solution in lab.

 

As per the statistics published by APNIC, our IPv6 deployment now reaches about 45% of our Rogers Ignite subscribers. This number increased significantly in the last two weeks with the enablement of IPv6 on CGN3ACSMR modem.

 

Full APNIC statistics are available at IPv6 Per-Country Deployment for AS812: ROGERS-CABLE

 

 

 


I'm glad to see the wireless (3G/LTE) network being v6 enabled and the SMR gateways being v6 enabled by default (sans factory reset). The /56 allocation for PD was a big omission from the rollout of v6 and needs to be rushed, that's a requirement for a good chunk of the userbase to use the service. Are the CGN3AC gateways going to be v6 enabled by default? That should be possible at some point. Thank you for the work so far.

Network Architect
Network Architect
Posts: 611

Re: Rogers IPv6 Status


@busterb wrote:
I'm glad to see the wireless (3G/LTE) network being v6 enabled and the SMR gateways being v6 enabled by default (sans factory reset). The /56 allocation for PD was a big omission from the rollout of v6 and needs to be rushed, that's a requirement for a good chunk of the userbase to use the service. Are the CGN3AC gateways going to be v6 enabled by default? That should be possible at some point. Thank you for the work so far.

Before deploying a /56, we had to ensure that our IPv6 deployment was complete and stable. We have to ensure that it won't break anything in production and therefore are required to perform some testing in lab first.

 

In order to release /56 initially, we would have had to delay the launch of IPv6 by a few months. Most of our users are happy with a /64 which is why this decision was made. Rest assured however that we are working on deploying /56. In the meantime, although this is not officially supported, our DHCPv6 server allows for multiple /64 to be delegated.

 

With regards to enabling more gateways by default, it requires to gateways to be at a minimum firmware level of 4.5.8.21. We need to have most gateways for a particular model to be at that level before we enable by default. As firmwares are upgraded, more models will be added. In most cases however, a factory reset is sufficient for a user to enable IPv6 on their own gateway.

I Plan to Stick Around
Posts: 9

Re: Rogers IPv6 Status


@RogersDave wrote:

@busterb wrote:
I'm glad to see the wireless (3G/LTE) network being v6 enabled and the SMR gateways being v6 enabled by default (sans factory reset). The /56 allocation for PD was a big omission from the rollout of v6 and needs to be rushed, that's a requirement for a good chunk of the userbase to use the service. Are the CGN3AC gateways going to be v6 enabled by default? That should be possible at some point. Thank you for the work so far.

Before deploying a /56, we had to ensure that our IPv6 deployment was complete and stable. We have to ensure that it won't break anything in production and therefore are required to perform some testing in lab first.

 

In order to release /56 initially, we would have had to delay the launch of IPv6 by a few months. Most of our users are happy with a /64 which is why this decision was made. Rest assured however that we are working on deploying /56. In the meantime, although this is not officially supported, our DHCPv6 server allows for multiple /64 to be delegated.

 

With regards to enabling more gateways by default, it requires to gateways to be at a minimum firmware level of 4.5.8.21. We need to have most gateways for a particular model to be at that level before we enable by default. As firmwares are upgraded, more models will be added. In most cases however, a factory reset is sufficient for a user to enable IPv6 on their own gateway.


The testing should have already happened by now. It shows a lack of foresight. Its common sense this would be necessary.

 

I would surely hope so as this is a requirement. I'm aware of that as has been pointed out a in a few different places. I'm not really interested in going the hack route. I'll wait for things to be done properly.

 

As seen elsewhere in the forum I see the CGN3AC's are undergoing some level of firmware testing though it doesn't seem to be the same level as the SMR's and the -3552. I take it the AC's haven't been updated to .21 yet? I don't care about the factory reset. It's sans reset enabled by default that is more important for end users.

I Plan to Stick Around
Posts: 264

Re: Rogers IPv6 Status

It appears I'm now getting IPv6 on my phone, but not yet with tethering.

Resident Expert
Resident Expert
Posts: 1,066

Re: Rogers IPv6 Status

Where are you located?

 



I Plan to Stick Around
Posts: 264

Re: Rogers IPv6 Status

I'm in Mississauga.  I've had IPv6 on my cable modem for a few months as well.