DHCPv6 client has started working on the VLAN interface. I didn't change anything.

I found that DHCPv6 works with the ISP, but the request packets are unable to be captured by Wireshark.

I finally succeded to get the "bound" status on the ipv6 dhcp-client and also got a prefix from my ISP. The main issue was related to a specific dhcp config needed for "dhcp sollicit" packets sent by the router. I have the same issue of DHCPv6 Client packets not being sent by th...

I did a simple test connecting ether2 (without a bridge) directly to my PC and running Wireshark. I created an IPv4 DHCP Client and IPv6 DHCP Client on ether2. I am able to see IPv4 DHCP packets, but there are no DHCPv6 (or any IPv6) packets captured in Wireshark. I also ran the RouterOS internal Pa...

Another interesting observation: When IPv6 DHCP Client is working on the S interface PVID, it obtains a prefix but the entry is marked as invalid and is shown in red. [admin@MikroTik] > ipv6 dhcp-client print Flags: D - dynamic, X - disabled, I - invalid # INTERFACE STATUS REQUEST PREFIX 0 XI wan1 s...

How does your /ipv6 firewall export look like? The DHCPv6 client sends the initial request to a multicast address but the response comes from a unicast one, so "accept established" doesn't work. And unlike the DHCPv4 client, the DHCPv6 one is not connected "closer to the wire" t...

I have the same issue on v6.48. DHCPv6 Client does not work on a VLAN interface, or the master bridge interface PVID. It's stuck on "searching". However, I found another bug which acts as a workaround. You can create a DHCPv6 Client that runs on the S interface (ether1) PVID instead of the...

I would also like to see DNS over HTTPS support so I can use Cloudflare's service. Since the RouterOS DNS service is only a forwarder, DNSSEC can only be done by the upstream iterative resolver. To prevent tampering between RouterOS and the upstream resolver, DNS over HTTPS is required.

I would also like to see support for DNS over HTTPS so I can use Cloudflare's service.

There is some mention of a configuration program (probably only for Windows), but not how it accesses the module. I think the "EBM program" is the same as "Ethernet Boot and Management" mentioned further down in the spec sheet. I wonder if it's simply accessible via a default IP...