Messages

Yes, after IPv6 was working I installed 23.1.6 and rebooted, and it was still working afterwards.

I just tried gpb's suggestion to re-save the WAN interface again, and this time it worked.  I don't know what that did or why it worked today but not 3 days ago.

I have joined you there.  This is not a new problem but recently it's become a higher priority for me.

After a reset to factory defaults and a restore of the configuration I'm happy to say that IPv6 is working now.  Now I just need to figure out why live log updates aren't working anymore, and what else isn't quite right.

Well, I just upgraded from the quoted release to 23.1.2 and now I have no connectivity at all.  A ping request from the router to any external site returns "ping: sendto: Permission denied".

Indeed it does fail.  Is there a message thread somewhere that I can monitor to track progress and/or share my results?

I don't know much about how your proxy is configured, but secure DNS runs over either TLS on port 853 or HTTPS on port 443.  I'd guess that you're using DNS over HTTPS (DoH) and that's trying to pass through your proxy and can't.  Do you have the option to switch to DNS over TLS (DoT)?

I have the same problem with IPv6, and noticed that my speed has dropped as well.  Thanks for posting your findings, but I don't understand the rules you created to fix it.  Is there a page that describes the NPTv6 rules you've created?

I'm just as puzzled.  Mine's broken again and I didn't change anything. 

It doesn't sound like the WAN is broken.  Bullet #2 from OP indicates that IPv6 is working from the router.

In my case (which matches OP's description), I'm DHCPv6 and the router has the same IPv6 address that it's had for months or more, and I can 'ping -6 google.com' from there.  The clients on the internal network also have their same addresses but cannot 'ping -6' outside of the local network anymore.  A quick visit to ipv6-test.com confirms that there is no ipv6 from the client.

Update: as luck would have it, it's working now.  I did make some changes yesterday to try and resolve it (including setting accept_rtadv=0 and restarting) but it was still broken when I left it.  I'll try to find out what happened.

Lo and behold, after enjoying a couple of months of stability with 22.7.x, the upgrade to 22.7.4 has broken IPv6 again.  Diagnosing the situation shows that <snip>

Thanks for posting.  I don't visit this forum often but I'm in the same situation and that's why I'm here today; glad to hear it's not just me. 

What tools are you using to test performance?  I'm seeing some improvement with kmod, but the speed is still a small fraction of what should be possible, I think.

Indeed you are correct.  Thanks for the tip.  It's working and I'll do some performance tests once I'm at a remote location.

Hmmm...thanks.  I've done that and rebooted but now wireguard-go always shows red on the Services dashboard.  What log should I be looking at?

I've set up wireguard a long time ago.  Do I have to do anything new to take advantage of the kernel support?  I'm asking because it's still pretty slow.

I see os-wireguard under Plugins, and under Packages I have os-wireguard-devel, wireguard-go, and wireguard-tools.