Noticed the same issue today while setting up a WG tunnel. Both sides have only public IPv6 (although dynamic), IPv4 is CGNAT. The WG peer configuration prefers IPv4 (private, CGNAT) and fails to connect.

There should be a way to prefer IPv6.

I think /ipv6/address> set accept-router-advertisements=no "solved" the issue I was seeing the very same issue and was scratching my head. Was relieved to see your thread and indeed disabling RA did fix the issue for me. However, I do have a backup link which requires RA to fetch an IPv6 ...

It would have been great if the `fetch` tool supported specifying an interface. The use case for me is, I have multiple WAN interfaces, and I want to send a health check request from each WAN indicating that it's able to reach the internet. I use this service to do this -- https://healthchecks.io/ S...

I am using ZeroTier on my hap ac2 and was really surprised to know that its not available for my hex s. This is really disappointing.

Hope the MMIPS package which can be used on the hex s is made available soon.

+10000 for MMIPS

I'm also on the same boat. I have an SXT LTE6, passthrough with IPv4 works great, but IPv6 passthrough doesn't work. The client interface has a DHCPv6 client enabled, but it doesn't receive the IPv6 address. If I disable passthrough, IPv6 address gets assigned to the Mikrotik device. Is this not sup...