My provider gives a /56 per client, using prefix delegation.

All I had to do is to add a

Code: Select all

ipv6 dhcp-client
add add-default-route=yes interface=ether1 pool-name=mypool request=prefix

to get the /56. If it does not work with your provider, try "request=address"

After you get a prefix you can get your own address as:

Code: Select all

/ipv6 address
add address=::1 from-pool=mypool interface=bridge

and by default it will advertise the prefix, so any SLAAC capable device in the network will get another address or permanent/temporary addresses from the same /64

Even if you use the dhcp-client, it is doing prefix delegation + SLAAC, not stateful DHCP.

If the ISP uses SLAAC on the point to point link between you and them then there is a setting that allows the router to get an address that way. I believe it is global though. Makes your device behave like a client as in IPv6 those are the devices that should react to other routers RAs.

They "should" give you a usable prefix some other way like DHCPv6 prefix delegation. They may do SLAAC and DHCPv6 PD but that would be an odd combination at least here in the US.

/ipv6 settings print 
                       forward: yes
              accept-redirects: yes-if-forwarding-disabled
  accept-router-advertisements: yes-if-forwarding-disabled
          max-neighbor-entries: 8192

It will get you a /64, which I hope you can advertise again.

Did you tried enable router advertisements?

Code: Select all

/ipv6 settings set accept-router-advertisements=yes

The problem is not lack of dhcp (personally I prefer manual static config, because unlike with dhcp, it's not so easy to change anytime ISP feels like it, so it's really static), but the lack of your own prefix. That's how it's supposed to work, connect router to ISP, get a prefix and have own separate subnet(s) behind your router. If you can get addresses only using SLAAC, there's no place for your router and your whole subnet is accessible for ISP. It's possible to solve that by using router with ND proxy (RouterOS doesn't have that) or perhaps something can be done with bridge and filters (I didn't test it with IPv6, only with IPv4 in the past), but it's still not good enough.

The problem is not lack of dhcp (personally I prefer manual static config, because unlike with dhcp, it's not so easy to change anytime ISP feels like it, so it's really static), but the lack of your own prefix. That's how it's supposed to work, connect router to ISP, get a prefix and have own separate subnet(s) behind your router. If you can get addresses only using SLAAC, there's no place for your router and your whole subnet is accessible for ISP. It's possible to solve that by using router with ND proxy (RouterOS doesn't have that) or perhaps something can be done with bridge and filters (I didn't test it with IPv6, only with IPv4 in the past), but it's still not good enough.

...
The problem is solved. but the solution is very inconvenient. you need to adjust your hands.

it doesn't make much sense

• setting accept-router-advertisements=yes under /ipv6 settings
• configuring DHCPv6 client to request prefix and storing it into a pool
• configuring LAN interface (usually that's bridge) with IPv6 address from pool. This then enables router sending RAs on LAN interface which in turn allows LAN clients to perform SLAAC ... they'll end up in same IPv6 subnet as router's LAN interface.

There is one further issue. The DHCPv6 client needs to be able to receive UDP packets on Port 546 through the relevant interface, and your firewall configured as necessary.