Using the latest I received from support the issue is resolved on my system. All peers get the correct IPv6 assigned and work as expected.

Interesting I see a report of this working correctly. I am running the current alpha and the same issue persists on a rb4011. 1 peer set up. IPV6 works as expected. Add a second peer only the most recent peer gets ipv6. The rest of the peers do not. I have tested every devices configuration on their...

There is no hope of this being fixed for arm. All tickets are closed as previously fixed. The main read in here is unless you’re on the newest arm64 stuff they don’t care and will never address this issue. Best solution find a second device to host wireguard, mdns, whatever else MikroTik won’t inclu...

interesting they can fix it for other(newer) hardware but some how it just can’t be fixed on arm.

Brooding it over, mDNS allows information to flow from on vlan to another. This may be not secure by design, this may be the explanation why Mikrotik does not plan to support it. [/quote] I can also expose winbox ports to the internet, have no firewall. All terrible security choices but the decision...

I’m new here, just waiting on the arrival of my new Mikrotik router which I was really excited about… am I to understand that in (almost) 2023 mDNS is NOT a feature of Mikrotik routers?? I have a house full of IOT devices and use Home Assistant to bridge everything beautifully to homekit for me. Al...

Is there any hope for this issue being resolved? It continues to impact on rb4011. Is this just going to be one of those if you don’t like it upgrade your hardware to a newer setup?