ipv6 with controld stops working after about 2 hours

[innov8ideas4u]

Ipv6 stops working after 2 hours , I have a gt axe 16000 , my telus gateway is in bridge mode to the router and I'm using controld for DoT . I have tried literally every setting possible on my router and endpoint and can not get ipv6 to keep working after approx 2 hours. I have tried the controld daemon , and manual settings , I even changed to DoH and the problem still was happening. If I change any setting in the ipv6 menu and save then it starts working again, but only for 2 hours. When I got to the syslog on webgui and go to ipv6 tab it will show that I have and address but the WAN gateway will be blank. I have tried cronjobs and DDNS and literally every setting that I can change. I have spent hours and hours talking with "barry" the controld ai but can not figure this out. Any help or ideas from anyone would be greatly appreciated! Thanks!

 

[dave14305]

Sounds like your IPv6 address or route expired without getting renewed. Check in /tmp/wan0_bound6.env to see what lifetime numbers appear after the address or prefix.

 

[innov8ideas4u]

Sounds like your IPv6 address or route expired without getting renewed. Check in /tmp/wan0_bound6.env to see what lifetime numbers appear after the address or prefix

PREFIXES=2001:56a:7854:d800::/56,7190,7490,class=0001b558
I'm not too sure how to interpret the contents of the file that well , I'm a student, still trying to learn linux , "barry" says this when I pasted the contents of the file to it

PREFIXES=2001:56a:7854:d800::/56,7190,7490,class=0001b558 <br>
Those 2 numbers after the prefix (7190, 7490) are likely the preferred lifetime and valid lifetime, both in seconds. That’s about 2 hours (7490 seconds ≈ 2 hours 5 min), matching your expiry window.
So, your router is handed a 2-hour IPv6 prefix from your ISP, and for some reason, it’s not getting renewed before expiry—thus, IPv6 breaks until you reapply settings and get a new lease.
The issue looks to be with how Telus delegates IPv6 over their bridged setup, not with Control D.
For further guidance, you’ll want to: See if your Merlin firmware has an option like “Enable DHCPv6 PD Renewal” or similar (sometimes via hidden nvram settings).

Thanks for your help with this! not having ipv6 isn't affecting me but more of personal mission to try and understand what the heck is going on with this and why I cant seem to fix it

 

[dave14305]

I would suggest creating a Merlin custom script so you can see when the dhcp events occur. The script can be empty, it will still log the dhcp event in the system log.

echo "#!/bin/sh" > /jffs/scripts/dhcpc-event
chmod 750 /jffs/scripts/dhcpc-event

Make sure custom scripts are enabled in the firmware.

You can also enable IPv6 debugging with:

nvram set ipv6_debug=1
nvram commit
service restart_dhcp6c