Looks that way, at least until the CGN3 undergoes another update.
Benefits, others can chime in here. No Network Address Translation by the router. So, should see some speed benefit I would think. Other benifits, have a look at the following link, although I think that most will be transparent to the average user:
Sometimes the delays would be caused by the PC getting a AAAA ( IPV6) result from a DNS call and then timing out for some seconds before trying again and getting an AA record which is the standard IPV4 which of course works.
Looks like progress is being made, slowly...... Users on the DSLReports forum are reporting Native IPV6 available and working in some areas of Toronto.
Checked in Stittsville (West Ottawa) this morning. No IPV6 available.
I am living ok with Rogers 6RD. in Guelph. I could try to plug my spare router ( which can do V6) into the cable moden ( I have a CGN3 in bridge mode )and see if I get a prefix. I would hope that there would be an announcement perhaps area by area as it happens.
Slightly off topic, I am hopin g for an announcement that the Gigabit service will arrive on schedule....sometime in 2016.
You might have to restart the modem after you plug in the other router. That is in the case where you have two routers plugged into the modem, with the modem running in bridge mode. Both routers should end up with IP addresses after the restart. Now the question is whether or not native IPV6 was enabled in your area. I haven't seen any announcement from Rogers, anywhere, indicating that IPV6 was finally being enabled.
Being following the progress of this thread for past 2 years now and want to give a bit of an update. Native Rogers IPV6 works from what I tested under the following conditions.
I notice most are still running in tunnel mode and are getting speed of 25Mbps. With the setup I discribe above, this may work better for you.
Saw your note today and immediately tried it. I am in Guelph. Lo and Behold a real IPV6 address, two IPV6 DNS.
I tried IPV6-test and only got a score of 17. No IPV6 hostname and ICMP filtered.
Thank you Rogers. ( Although you might have left a message on this forum to say when it was coming.)
That is awesome, timlocke. How is the speed? As for the ICM and HOSTNAME issue, you'll have to set rules in the firewall and dns for those, which will resolve the filter and hostname issue. I don't recall the exact settings you need as I've already taken down the test lab. However, it should be allowing icm on both ipv4 and ipv6 through the WAN for the LAN or ANY (preferably ANY). A single rule for both can be set in this instance.