DHCPv6 on WAN interface doesnt get IPV6

Hello, I am using latest stable ROS7 on RB750gr3.

On ROS6 I can get /64 IPV6 prefix assigned AND IPV6 WAN address as assigned by my ISP.
I am getting the following assigned in ROS6:
/64 IPV6 prefix
/128 IPV6 address on WAN interface

However, on ROS7, I also get /64 IPV6 prefix assigned but it get stuck searching if I select prefix+address on ETHER1 (WAN INTERFACE).
I am getting this on ROS7:
/64 IPV6 prefix
–missing IPV6 on WAN interface (stuck searching)

I turned off IPV6 firewall as a test and still only get prefix but not WAN IPV6 address.

I have some servers that are IPV6 only and I wish to remotely access my mikrotik through the IPV6 address.

I found a workaround by using the ::1 LAN IPV6 address and allowing myself through the firewall but this does not seem like the right way of doing things. I can get to the first address assigned to my LAN interface out of the /64 IPV6 prefix, but I prefer to get to it using the WAN address but it stuck searching and never gets IPV6.

For the record, it works in ROS6 with no problems.

One more note, when will RB750gr3 get hardware offload or fastrack for IPV6 firewall?

Thank you,
alexv305

It depends on what your ISP is offering.
It is “unusual” to get a WAN IPv6 address using DHCPv6. Usually that is done with SLAAC, PPPoE or whatever.
Try without the “address” checkmark and see what IPv6 address you then have on the WAN (a local address?).
Put the obtained prefix in a pool and set the LAN address from the pool, see if you get a valid address on the LAN and if you have IPv6 connectivity.

My ISP provides a /128 on the WAN interface and assigns a /64 prefix. On router OS 6 I can see the /128 on Ether1 and the /64 prefix assigned, but since upgrading to ROS7 stable the DHCPv6 client gets stuck searching if I enable both “address” and “prefix” on the client. If I disable “address” and leave only “prefix” it works fine, I get a /64 prefix and I can assign to my LAN as normal but I want the /128 assigned on the WAN interface as well. Both /128 and /64 are public IPv6 addresses.

But are you sure you do not get the /128 when you leave off the “address” checkmark?
As I wrote, it may be assigned another way than with DHCPv6.
You can try configure as I wrote above and then use “tool traceroute” to see what the WAN address is.
(I think it is still not displayed properly in /ipv6 addresses)
You may need to set “accept router advertisements” to YES in /ipv6 settings.

Hello, as it turns out my ISP is doing some strange things with different MAC addresses that their modem sees. For example, if I use the default Mikrotik MAC address it does not let me get prefix. I changed my WAN MAC address to match intel and now I am able to get IPV6 prefix and IPV6 public on WAN interface. Very strange.

That is not strange at all.
They probably allow you only a single IP on the WAN interface, and you likely did not “release” the lease you got on your other system.
You just unplugged it and plugged in the MikroTik, and started asking for another lease.
You don’t get that because you already have one.
So you can check what the lease time is, and unplug the router long enough for it to lapse, and then it will most likely work with the correct MAC.
Or you can try to release it, but with RouterOS that does not actually work for your case because when you click “release”, the router immediate realizes that it has no lease and asks for a new one, of course again using the same MAC.