Intermittent ipv6 connectivity after upgrading to fiber in North Vancouver

SOLVED
Connector

Intermittent ipv6 connectivity after upgrading to fiber in North Vancouver

I just upgraded to fiber from DSL and got swapped to a T3200m modem as well. I am still getting an ipv6 address (real 2001:569:...)however, routing of ipv6 is no longer working. Windows responds "Destination net unreachable" when trying to ping any valid ipv6 address. I am able to ping the link local and ipv6 address of the T3200m. On the T3200m, using the ipv6 ping test page, all internet addresses are timing out as well which leads me to believe there's an issue in the core network. I've rebooted both the ONT (Nokia) and T3200m but the same problem persists.

 

Ipv6 was working fine on DSL, and it has intermittently worked in the 36 hours or so that I've had fiber but it seems more down than up. Is anyone else experiencing this issue? Any next troubleshooting steps?

0 Likes
1 ACCEPTED SOLUTION

Hello

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.

 

Jordan

 

View solution in original post

0 Likes
40 REPLIES 40
TELUS Employee

Hey folks

I can help take a look into this but to speed things along I would like to determine if this is a result of moving to Fiber, issue is caused by the Actiontec 3200 or merely a network config issue isolated to a specific network element. 

The core routing and distribution layers between DSL and Fiber is exactly the same, the access layers are the only things different.

If anyone has a chance, can you bypass the Actiontec completely and plug the PC into the same port of what the Actiontec was using (usually it is ONT port1) Let it sit overnight and retest connectivity in the AM. 

We aren't aware of major connectivity issues involving IPV6, this is tested quite extensively. That being said, we have an extremely low volume of users for it so far.

 

If everything works fine with the Actiontec out of the way, please post the firmware revision it is using.

 

Jordan

Are you referring to IPv6 testing using a PC? If so I believe that doesn't work because most DHCPv6 clients don't request a /56 prefix, while a router does.

0 Likes

I think you are right, /64 is meant for hosts.

Let me take this back and think about it a different way.

Jordan

0 Likes

I've tested a while ago (for different reasons) under Linux and it's possible to request a /56 prefix, emulating a router under Linux. Other then that, nope.

0 Likes

Disregard the two "Under Linux"'s. A bit sleepy 😛

0 Likes

Just a update on my issue. I live in North Van and this issue is due to some hardware in the telusn infestructure.

There is no ETA on the fix and I am willing to be this is a combination of lack of trainingnon the tech support side and people not nessiaarly knowing there is a issue. I suggest anyone that that has this issue contact support and insist they look into it.

I finally got traction using Twitter support and asking them to escalate it. Some of their escalation support reps know what is going on, but a very small amount. Infact in my previous inquiries the back offices response was that ipv6 is not supported...which is not true.

So long story short...if you are having this issue complain so the issue will be escalated.
0 Likes

Hi folks

I think we have found the problem and found a workaround. Might need another day or two before we can release next steps. Thank you for your patience!

Jordan

 

0 Likes

Great news. Thanks for the update Jordan!
0 Likes

Hello

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.

 

Jordan

 

View solution in original post

0 Likes

Hi there,
I've recently upgraded to Fibre in North Vancouver as well and have been noticing the same issue. I'm on the latest firmware (31.164L.18) for my router (T3200M) and can see that for the first ~90 minutes there is a valid IPv6 route however after that the route drops and I lose IPv6 connectivity resulting in intermittent slow downs/disconnects with my devices until they fallback to IPv4.

Once I knew what to look for I was able to find that a business in the same building as well as a friend a couple blocks away are also experiencing the very same issue.

@Jordan_Labelle You mention that an update would be released to the T3200M that would fix this issue. Do you have any news on that?

Thanks,
Matthew

0 Likes

Unfortunately not. 

It has been confirmed the new WIFI hub works fine in maintaining the IPV6 route. This new gateway has more or less superseded the Actiontec 3200.

If you don't want to wait and need an immediate resolution, speak to our technical support teams and mention this thread. 

The technical support team will need to check the distribution layer and see the equipment that the service runs through to confirm if you are impacted. 

We have an internal understanding to have the T3200m replaced with the WIFI hub once it is confirmed.

 

Jordan

 

 

0 Likes

Hey Jordan/all,

 

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.

 

Thanks!

0 Likes

Perfect, thanks for the update. I will share this with our network teams internally.

 

Jordan

 

 

0 Likes

Any updates on this issue?  Still doesn't appear to be a firmware update.  

0 Likes

If could be upto six months wait so around June.
0 Likes

Any update on this? IPv6 still seems to be broken in my area of North Vancouver.

0 Likes

See my reply to the post below this.

0 Likes
Friendly Neighbour

I live in Surrey and have the same issues described here, i.e. ipv6 not working after 30-90 minutes after reboot. It's now nearly Oct 2019. Any update on a fix for this ipv6 issue?

0 Likes

Hi,

 

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?

0 Likes

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!

0 Likes