Can you share a ticket ID, so I can +1 this?
@MikroTik as motivation, use-cases, or expected user experience:
I lost one hour because of this. Thanks to this post
from mducharme, I was confident enough to go for try-and-error.
- My first problem was, RouterOS might have created an IPv6 randomly (via Privacy Extensions; RFC 3041). How shall I know RouterOS uses a stable address via the IPv6 prefix and Modified EUI-64?
- My second problem was, for now exactly 10 years, we have IPv6 in consumers’ hands. For example, Apple macOS does it automatically the way the IETF protocol designers envisioned it in RFC 2461 exactly 22 years ago. Although I went for the QuickSet ‘WISP AP’ / bridge, why do I have to enable IPv6 manually? Consequently, I did not know whether it is enabled and what was assigned. Furthermore, such double-checking is required because there are networks with faulty routers advertising invalid IPv6 prefixes. OK, that would be visible on a computer within that network as well; what if I VPN into that RouterOS?
- My third problem is, that because I could not determine it yet, how does RouterOS get its DNS server: Does it extract RDNSS, and when that does not exist (or the RA flag O is set) does it ask via DHCPv6 automatically? Or does RouterOS not do DNSv6 at all and just DNSv4?
OK, Microsoft Windows, Apple macOS, and other UNIX systems like Ubuntu are consumer software. Nevertheless, a non-consumer software should not be worse in user experience, on default – except there is a good reason. The current situation is like flying blind. So, these were my three reasons (plus one hour wasted) for a +1.