Forum Discussion
Solved
IPv6 configuration settings?
Short version, I have purchased own wireless router to replace the router functions of the Telus Gateway (T3200M). The gateway is currently being used as a modem only. Everything is working great (be...
Just a quick update. TP-Link technical support reached out to me via TP-Link Community (Web Forum). My lack of IPv6 connection was resolved in two mouse clicks on the IPv6 configuration page. Kudos to TP-Link for the follow up email asking me was everything working okay and if there was anything else they could help me out with. 😊
Just a quick update. TP-Link technical support reached out to me via TP-Link Community (Web Forum). My lack of IPv6 connection was resolved in two mouse clicks on the IPv6 configuration page. Kudos to TP-Link for the follow up email asking me was everything working okay and if there was anything else they could help me out with. 😊
So what was the fix if you don't mind posting?
I don't mind at all.
"Get IPv6 Address" in WAN settings was changed to "DHCPv6"
An IPv6 connection was established but it turns out its transient. Disappears after a few hours. IPv6 Release/Renew causes a reconnection but again it doesn't last more than a few hours. I'm at a loss. I have TP-Link Canada chewing on it and I should receive word from them today or tomorrow. No sense contacting Telus again; they are not interested. The thing is, I don't know which end the problem is. With Telus or TP-Link. The TP-Link IPv6 router settings are a carbon copy of the Telus Gateway.
The only exception I can see is the LAN setting prefix length. its 56 in the Telus router and 64 in the TP-LINK. I have no idea if that makes any difference or not 😕.S.H.
Thanks, I have been setting up and tinkering with my new router, TP-Link AXE16000, and this has had me stumped. I've been able to get it working using the process you mentioned above but am having the exact same issue of it dropping. I have read that it should be 56 but I do not see a way of changing it from 64?
All through my ordeal, I've been attempting to break it down and look at may be going wrong one piece at a time. The prefix length has to do with the total number of subnets which as far as I can determine has nothing to do with connection issues. So another dead end. So moving on...at this moment in time, this is the longest time span IPv6 connection been alive. I came across a tiny bit of information that may have solved my problem. There is a windows service call "IP Helper" that can interfere with some aspects of IPv6 connections. It was one thing to look at if experiencing problems and was recommended to disable the service as a trouble shooting step. So I went ahead and disabled that service. Easy to turn off and turn back on again if one feels the need. Hold down the Windows key and press R (Windows + R) Type in Services.msc in the box and click OK. Scroll down to IP Helper, right click, select properties. In the drop-down menu in Startup Type, select Disabled click Apply then click Okay. You still have to stop the service so either restart your computer or just click on IP Helper Status and then click Stop. That will stop the service right away without a reboot. It sounds somewhat complicated but its easy when you can see it in front of you. If I still have IPv6 in the morning, that was it.
