This has ben dolved but maybe someone googles for it: after connection ipv6 hop_limit is zero (hop_limit=0), which results non-working ipv6 connection. (In linux it’s
/proc/sys/net/ipv6/conf/wlan0/hop_limit
for example.)
When I keep IPv6 ND hop limit on default (like in winbox) it seems to use ‘0’ as hop limit value.
I haven’t checked RFCs whether that’s good or bad (probably it’s standards compliant value meaning “undefined”) but when a machine is using NetworkManager (which is default for newer Debian installs for example) it blindly fills hop limit from RA into network interface, and hop_limit=0 results ipv6 disconnectivity.
Set it to safe 64 or so instead of the default and it’ll work just fine.
/ipv6 nd set [ find default=yes ] hop-limit=64
This may be a NM bug or not but definitely bites hard (no ipv6 connections work) and hard to figure out.
Hope this helps.