As an update, I have spoken to our network team and there is indeed a vendor specific difference of opinion in how the RFC is handled to maintain an IPv6 default route. Without getting into specifics, the Actiontec T3200M drops the route after 90 minutes in certain areas of North Van. There is a firmware update scheduled in the next 6 months to resolve this, unfortunately I do not have a specific date.
Workaround: Replace the Actiontec T3200M with Actiontec T1200H. This will not drop the IPv6 route.
Caveat: This older Actiontec gateway has slower WIFI and uses HPNA over Ethernet, not MOCA like the current 3200M does. If you have TV services using the coax cable in your house, this solution will break the TV aspect of the service.
If this works for you and are ok with the caveats, please reach out to the support team via the chat and mention this post. We will send out a gateway pro bono to you by mail or by technician depending on availabilities. The agent can reach out to me specifically if they need clarification. They will check the network to see if you would be impacted and advise accordingly.
Updates are pushed to the gateways either via schedule or when a factory reset is performed so without a specific date known, would recommend a manual firmware update from time to time to see if a new one has been released.
If you have any success with this workaround, please post an update here.
Thanks for all of your help looking into this issue and finding a work around. I had a quick question about getting the older Actiontec T1200H router. Will we be able to keep the newer Actiontec T3200M so that we can switch back when the new firmware is finally pushed out?
Also since this seems to be rectified by swapping to another router I was wondering if swapping over to a SFP install would also potentially resolve this as well? A few customers have managed some how to get a SFP installed into the action net router and then directly plugging the SFP into their own router, bypassing the T3200M router. Just curious.
Once again thanks!
Sorry I did not respond but I have been out of town and just got back recently. I just contacted the support rep that helped me initially that I belive you spoke to. I havent heard back yet but hopefully soon, if not I will open a chat session and see if a tech support rep through there can help send out a actionnet modem.
I will update once I have tried it out or if there is something to update on.
Yes this seems to be a common issue, the tech support reps dont seem to have the training to deal with it. In my case I had a more professional response and they forwarded it to the back office to look into. Unfortunately they came back and said that IPV6 wasn't supported and is a beta type thing, which isn't true.
This is something Telus needs to work on. With that said I think it was NFtoBC that recommend contacting support through twitter and to be honest that was where I got some traction on this issue so I do recommend using that avenue if you are having issues.
Not sure if it will work to be honest, it means there would be two prefixes pushed to a single access. Not sure if there were limits in delegation on a per connection basis. No harm in trying tho.
Spent a few minutes trying it out and it didn't work. Outside of that the only issue I had was a laptop that I had connected to wifi for some reason was failing the IPV6 test while my phone was not. Once the laptop was restarted everything worked fine. Not sure if there is some other issue here but outside of that incident everything seems to be working.
I can confirm the T1200 works and holds the routes past 90 minutes. I'm just over 24 hours of continuous working IPv6, so no route dropping here, in Surrey.
I have a bit of a unique setup that I won't mention here in order to keep this from getting complicated, but the T1200 works very well for IPv6, and with some modification to the IPv6 firewall rules that are on the router, I was able to get a 20/20 score, consistently, on ipv6-test.com. Before modifying the FW rules, I was getting 18/20.
Now, hopefully soon, both the Juniper RE's and T3200 firmwares are released and updated on the TELUS side so that we don't need these workarounds .
Let me know if you have any questions.
So not sure about Surrey but in North Vancouver apparently the issue was due to a combination of some back end hardware and the ActionTek t3200m.
With the older modem there was no issue but this was a work around as it has weaker WiFi and also some incompatibility with the TV that required additional hardware.
With that said the problem was not resolved as of a few weeks ago so I followed up with the support rep I had been talking to and he went ahead and scheduled a swap of the modem to a newer modem that apparently isn't available everywhere. Not sure what its called although the rep that swapped it out called it a Diaper Genie as that's what it looks like lol. Long story short I have not had issues since the swap.
Maybe get support to upgrade your modem?