so, i have owned mikrotiks for about one year now, i'm now up to abou 40 devices.

I'm a big big avocate for IPv6, but each time i actuall y try to implement it i find a huge barrier.

For now the biggest one is the tunneling trough VPN, i have 28 VPNs setup on the central router, and more in other satellite routers

Why, oh why is the local address a consecutive number that is so hard to manipulate or change??

fe80::14/64
fe80::15/64
fe80::1c/64
fe80::1d/64
fe80::1e/64
fe80::20/64
fe80::21/64
fe80::26/64
fe80::2a/64
fe80::3b/64
fe80::41/64

for some reason fe80::21/64 has been a pain in the a** for me, another mikrotik also loves to use it as a local address on a vpn, i do not know how to tell them "please, not, use this instead"

Main problem comes with OSPF:

Discarding packet: locally originated
src address=fe80::21
Discarding packet: locally originated
src address=fe80::21
Discarding packet: locally originated
src address=fe80::21


So, basically between the master mikrotik and this specific mikrotik there can be no IPv6 connectivity because the Local address on Mk1/VPN is the same as in Mk2/VPN2... if this is not clear, let me put it this way:

Mikrotik 1 ---> Mikrotik 2 share a VPN on which they have Mk1 Local Adress as fe80::21 and Mk2 as fe80::22, then Mk2 has another vpn on which the Mk2 uses as local address fe80::21 and as remote fe80::23, and now there's an ip conflict.

This issue is on v6.49.3

This is one of the problems i have on ipv6 the second major problem is that i can't figure out how to hand out Prefixes on dhcpv6 (i have a /48 prefix delegated)

Why, oh why is the local address a consecutive number that is so hard to manipulate or change??

fe80::14/64
fe80::15/64
for some reason fe80::21/64 has been a pain in the a** for me, another mikrotik also loves to use it as a local address on a vpn, i do not know how to tell them "please, not, use this instead"

Main problem comes with OSPF:

Discarding packet: locally originated
src address=fe80::21
Discarding packet: locally originated
src address=fe80::21
Discarding packet: locally originated
src address=fe80::21


So, basically between the master mikrotik and this specific mikrotik there can be no IPv6 connectivity because the Local address on Mk1/VPN is the same as in Mk2/VPN2... if this is not clear, let me put it this way:

Mikrotik 1 ---> Mikrotik 2 share a VPN on which they have Mk1 Local Adress as fe80::21 and Mk2 as fe80::22, then Mk2 has another vpn on which the Mk2 uses as local address fe80::21 and as remote fe80::23, and now there's an ip conflict.

This is one of the problems i have on ipv6 the second major problem is that i can't figure out how to hand out Prefixes on dhcpv6 (i have a /48 prefix delegated)

Why are you manually handing out/assigning FE80:: addresses? This seems wrong.. Is it a static /48? I strongly suggest you use that instead..

IPv6 prefixes.. IPv6-Pool and IPv6-DHCP-Server on your central router.

Why are you manually handing out/assigning FE80:: addresses? This seems wrong.. Is it a static /48? I strongly suggest you use that instead..

IPv6 prefixes.. IPv6-Pool and IPv6-DHCP-Server on your central router.

It is nothing to do with the user configuration or global unicast (GUA) / unique local (ULA) addresses. Whilst Mikrotik generate EUI-64 based link-local addresses from the EUI-48 MAC address on interfaces, they only do so for interfaces which have a MAC address, and appear to use the internal interface index for those which do not. The only way to change these is to delete the interface and create a new one which will use the next free internal ID.