Slow IPV6 redetection after reconnect

[walkerx]

I noticed earlier I had lost IPv6, so restarted my connection but this still didn't start straight away so rebooted the system and still unable to get dpinger to start and no ipv6 detected on the wan.

I rebooted and restarted the connection a few times and still nothing, but as I was then deciding to check with my ISP (Zen) the Wan interface showed IPv6 and dpinger started. This was after a considerable amount of time (about 10 minutes), so why is it so slow in getting IPv6 back up and running.

[marjohn56]

Have you got it set up using dhcp6? Zen gives you the ability to use static assignments, so use them. The only issue you'll ever then have is on a few occasions dpinger does not recover when a PPPoE down/up event happens, usually a BT line hiccup; to get around that I use Monit to watch the dpinger daemons and restart them if they are down.

[walkerx]

Have you got it set up using dhcp6? Zen gives you the ability to use static assignments, so use them. The only issue you'll ever then have is on a few occasions dpinger does not recover when a PPPoE down/up event happens, usually a BT line hiccup; to get around that I use Monit to watch the dpinger daemons and restart them if they are down.

Using the static as setup with your help when switched from sky and to the qotum

Originally I wasn't getting any IPv6 throughput from clients but dpinger and dhcpv6 were showing active and the gateway monitor was reporting that all was ok.

There were no leases in the Dhcpv6 for local devices and connection had been active over 30 days.

I restarted dpinger and dhcpv6 but still no ipv6 locally so restarted the unit, when then connected I was getting no ipv6 details on the wan only ipv4, i restarted the connection but still no good so rebooted again. This still never worked and so I started writing an email to ISP to see if there were issues and it finally came back up before I sent anything.

[gogolathome]

I had nothing but troubles keeping ipv6 alive with 20.7.
Then I switched back to 20.1 and everything is rock solid.
You have to wait for upstream fixes. I have no clue what is wrong.

[marjohn56]

Using the static as setup with your help when switched from sky and to the qotum

That's what I don't get, if you have set statics, there is ALWAYS the GUA address on the WAN. There is an issue with radvd which is intermittent and prevents the LAN side clients from getting routes etc, this may be what you are suffering from. I am currently running RTADVD in place of RADVD and so far so good, that doesn't help you though. If you see this happening again, try restarting radvd.

[walkerx]

Using the static as setup with your help when switched from sky and to the qotum

That's what I don't get, if you have set statics, there is ALWAYS the GUA address on the WAN. There is an issue with radvd which is intermittent and prevents the LAN side clients from getting routes etc, this may be what you are suffering from. I am currently running RTADVD in place of RADVD and so far so good, that doesn't help you though. If you see this happening again, try restarting radvd.

thanks, will do as when checked thinkbroadband and uptime robot connection these showed fine and only disappeared between the period I restarted and the link showing ipv6

I have just checked settings under lan and the ipv6 is set to track interface

and under wan ipv6 is set to dhcpv6 (im trying to locate some old emails but don't think ever changed this setting)

[marjohn56]

In that case you are using dhcv6 and not statics.

[walkerx]

In that case you are using dhcv6 and not statics.

yeh, i've just found an old email from when testing Google Wifi and the Deco - we got it all working using Dhcpv6 on WAN so left it as is.