I have been running 378.51 for a couple of days now. Did a factory reset and manual configuration after installing it. IPv6 is via an HE tunnel. The wan-start script correctly configures the tunnel on boot. Included in my wan-start script is some code to write an entry showing the tunnel endpoint update result in a persistent log on the USB memory stick every time wan-start is run. I am not using any other advanced features (eg: VPN, Samba, etc.), however I added entware-based DNSCrypt instances for both IPv4 and IPv6 (which I did not have running on the previous firmware, which was stable for months at a time).
Everything works properly initially.
However, after a few hours, IPv6 connectivity with the outside world fails. Devices still receive an IPv6 address, and can ping each other on the home network side of the router, but cannot connect to or ping external IPv6 addresses. Previously I have seen similar symptoms when the tunnel endpoint failed to update an external IP change, however, the persistent log does not show any change during that time and manually looking up the current endpoint value on the HE Tunnelbroker web panel shows it matches my current external IP.
So far, it seems to happen when I'm not around or overnight. The router log overwrites the beginning, and I can't see any entry showing what might have failed (not that I'm an expert at reading router logs anyway!) I can see that the IPv4 instance of DNSCrypt successfully obtained new certificate keys (seems to happen about once an hour), but there are repeated failures when the IPv6 instance tries to update, suggesting that the IPv6 connectivity failed prior to the earliest logged event.
It would be nice if someone could simply say "Oh yes, we know all about that, just change x to y and all will be well." However, I have been searching the forum and can't find the easy solution. So can someone suggest the next step to diagnose the problem? Maybe a script that will create a persistent log on the memory stick of possible clues to watch for? (Please speak slowly and use small words: I'm not very good at this stuff!)
Everything works properly initially.
However, after a few hours, IPv6 connectivity with the outside world fails. Devices still receive an IPv6 address, and can ping each other on the home network side of the router, but cannot connect to or ping external IPv6 addresses. Previously I have seen similar symptoms when the tunnel endpoint failed to update an external IP change, however, the persistent log does not show any change during that time and manually looking up the current endpoint value on the HE Tunnelbroker web panel shows it matches my current external IP.
So far, it seems to happen when I'm not around or overnight. The router log overwrites the beginning, and I can't see any entry showing what might have failed (not that I'm an expert at reading router logs anyway!) I can see that the IPv4 instance of DNSCrypt successfully obtained new certificate keys (seems to happen about once an hour), but there are repeated failures when the IPv6 instance tries to update, suggesting that the IPv6 connectivity failed prior to the earliest logged event.
It would be nice if someone could simply say "Oh yes, we know all about that, just change x to y and all will be well." However, I have been searching the forum and can't find the easy solution. So can someone suggest the next step to diagnose the problem? Maybe a script that will create a persistent log on the memory stick of possible clues to watch for? (Please speak slowly and use small words: I'm not very good at this stuff!)
