Unreliable IPv6: IPv6 addresses are all deprecated - make it stop

RouterOS General
1

For a while now I have had unreliable IPv6 addresses, most specifically all IPv6 addresses are marked deprecated on MacOS and the end user experience is terrible.

What do I need to do to stop clients losing their SLAAC addresses? If you look closely below, all IPv6 addresses are deprecated.

en0: flags=8b63<UP,BROADCAST,SMART,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> mtu 1500
	options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
	ether 82:e8:18:c5:d7:c1
	inet6 fe80::10c8:eb02:c870:c5ba%en0 prefixlen 64 secured scopeid 0xb 
	inet6 2axx:xxx:xx:xx:c2f:28a3:4271:25ac prefixlen 64 deprecated autoconf secured 
	inet6 2axx:xx:xx:xx:f50a:7d20:117d:e00a prefixlen 64 deprecated autoconf temporary 
	inet 192.168.220.40 netmask 0xffffff00 broadcast 192.168.220.255
	inet6 fd00:1822:c5ed:a74f:1457:59a9:a596:2ebc prefixlen 64 autoconf secured 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
2

You may use this

image
image1227×1500 197 KB

or provide your configuration and then forum experts may help you

3

7.21beta2? Same issue here, SUP-201304, disabling DHCPv6 IA_PD Client then enabling it again, every time before the time “Prefix Expires After” goes by 50%, works around the problem.

That means, if your ISP gives you 72 hours prefix lifetime, you need to disable then enable DHCPv6 Client every 36 hours, or earlier.

4

v7.20.1 and earlier versions.

Disabling and re-enabling the interface has the same effect of resetting things, as does a restart. The problem then returns later.

It seems worse on wired networks, I see it less on wireless.

I have a static allocation of IPv6 from my provider, it’s not DHCPv6 for me.