IPv6 ULA Address Lost on Reboot

Hello-

I'm using WebFig, 6.48.3 on hap ac2.

I've added an IPv6 pool for ULA (IPv6 -> Pool):

Here's the output:
Flags: D - dynamic

NAME PREFIX PREFIX-LENGTH EXPIRES-AFTER

0 ipv6ula fd4c:rest_of_upper_64::/64 64

So far looks good.
Then I add an IPv6 address belonging to that ULA (IPv6 -> Addresses -> "Add New")
Enabled checked, from pool: ipv6ula, address: ::1/64, Interface: bridge, "Advertise" checked, and everything else defaulted.

After clicking "Apply", the address is added and everything looks good. My other IPv6 Devices pickup the ULA and SLAAC.

When I reboot the router, my ::1 is gone.

Has anyone else observed this behavior? Am I doing something wrong?

Thanks!

I don’t have 6.48.3, but quick test with 6.48.6 says that it survives reboot just fine. And I don’t know why you bother with pool, you could simply add whole address directly.

If you add your global addr also as ::1 from your global pool, one of those ::1 goes away after a reboot, the system considers them as duplicates or something. You have to use different addresses to satisfy RouterOS.

If it happens, then not always, I tried three pools, one address from each, all exactly same ::1/64 and all three survived reboot.

On the same interface?

Oops, that’s it, only one address survives there. So it’s a bug.

Same on 6.49.2

Did anyone try v7?

The behaviour described above at post #3 http://forum.mikrotik.com/t/ipv6-ula-address-lost-on-reboot/154386/7 is still valid in v6 and v7, when something regarding this will change I’m guessing it’s gonna be in the changelog.
But I don’t think anyone has a support ticket opened for this and I won’t bother, I’m just using different addresses.

Are there any more prerequisites for the particular setup?
I have tried with RouterOS 7.5,


/ipv6 pool
add name=ULA-Pool-LAN prefix=fd00:410::/64 prefix-length=64
/ipv6 address
add address=::1 from-pool=ULA-Pool-LAN interface=ether1

Rebooted router few times, ::1 stays there.
What are the devices used on your setups?

Quick test with CHR, you need more than one pool and address:

/ipv6 pool
add name=xx1 prefix=2001:db8:1::/48 prefix-length=64
add name=xx2 prefix=fd00:410::/64 prefix-length=64
/ipv6 address
add address=::1 from-pool=xx1 interface=test1
add address=::1 from-pool=xx2 interface=test1

You’ll have this:

> /ipv6/address/print
Flags: I, D - DYNAMIC; G, L - LINK-LOCAL
Columns: ADDRESS, FROM-POOL, INTERFACE, ADVERTISE
 #    ADDRESS                       FROM-POOL  INTERFACE          ADVERTISE
...
19  G 2001:db8:1::1/64              xx1        test1              yes
20  G fd00:410::1/64                xx2        test1              yes
21 DG fd00:410::1/64                           test1              no
22 DG 2001:db8:1::1/64                         test1              no

And after reboot:

> /ipv6/address/print
Flags: I, D - DYNAMIC; G, L - LINK-LOCAL
Columns: ADDRESS, FROM-POOL, INTERFACE, ADVERTISE
 #    ADDRESS                       FROM-POOL  INTERFACE          ADVERTISE
...
13  G 2001:db8:1::1/64              xx1        test1              yes
...

Btw, what’s with those dynamic entries (#21 and #22 before reboot)?

Thank you for the update, it did the trick. Filling the report, hopefully it will be fixed shortly.

One year, not bad. http://forum.mikrotik.com/t/v7-1rc1-development-is-released/151250/243
Glad that it’s getting looked into, anyway.
Thank you.

Znevna, thank you very much for pointing it out, there was a report in our ticketing system (that provided description for this issue and link to this topic). It is always great idea to duplicate the same report on support@mikrotik.com/help.mikrotik.com

Considering how other IPv6 related quirks were completely ignored in the forum by staff (?) such as this:
http://forum.mikrotik.com/t/ip6-address-from-pool-bug-fixed/134313/1 identical to this one: http://forum.mikrotik.com/t/ipv6-address-assignment-hint/107540/1
or this:
http://forum.mikrotik.com/t/v7-1rc5-development-is-released/152877/110
or this:
http://forum.mikrotik.com/t/changing-ipv6-prefix/155531/62
I can’t remember more right now, I thought it would be futile to open tickets just to get the usual MikroTik answers. I don’t wanna get disappointed on purpose :slight_smile: