In some of the datacenters or ISPs, users are only offered a “plain” IPv6 configuration: one single /64 subnet with a gateway address, which means the clients behind the routerOS will not be able to assigned a provided IPv6 because a router aims to connect two different subnets.
There are multiple solutions to this scenario like NAT, 6to4/6to6, ND proxy, etc.
Among all those solutions, ND proxy provides the most elegant, clean and native architecture: fully native IPv6, best compatibility on router’s clients, etc.
Currently,
However, while currently routerOS supports ND Proxy, it only supports proxying a single IPv6 for each config entry, which hugely limited its usability, when the LAN side has arbitrary number of hosts using SLAAC (especially Windows and Androids will create themselve multiple IPv6 as a privacy feature).
I understand that this can be overcame by some kind of scripting or tricks, but none of them is better than native support of subnet.
See attached below. The IPv6 ND Proxy doesn’t take a subnet but only one specific address.
As a loyal routerOS customer who purchased several L10/L1 CHR licenses as well as many Mikrotik hardwares, I kindly request that Mikrotik considers the proposal below:
The IPv6 ND Proxy should take subnet address when adding proxy entries.
IPv6 is becoming a thing today, adding this capability greately makes routerOS more flexible. Other users also shared their confusion on this see below. And implementing this proposal will ultimately resolve most of their problems.
Please also stop asking users to “talk with their ISP”, “use NAT” or “use DHCPv6(not even supported by Android)” or workaround with some tricks etc., as most Mikrotik users are pretty experienced, they know what they are doing and they look for best solution out of all.
I collected a few of threads which could be resolved by this proposal.
I think a better proposal is to have a 2nd mode (beside the existing one) for ND Proxy, called "Delegate Prefix" for example, that has a drop-down selection for "Upstream Interface" and a drop-down selection for "Downstream Interface".
In this mode, with "Accept Router Advertisements" enabled for the "upstream" interface, the /64 prefix received from RA on the "upstream" interface will be automatically advertised on the "downstream" interface. No needs for manually hardcoding the prefix like in your proposal.
For routing to work correctly, the router will automatically add a dynamic /ipv6 address entry for the "downstream" interface, assigning itself a SLAAC address within the prefix, with prefix length /64 and advertised=yes. On the "upstream" interface, it doesn't need any address assignment, but if you want, it can also assign itself a /128 address entry from the same subnet with advertise=no.
The rest of the NDP proxy functionality are implemented as expected.
But the forum is not the right place for requesting features from MikroTik. You should create a support ticket for that: