Invalid IPv6 route enries from OSPFv3

RouterOS RouterOS beta
1

I recently updated my RB4011 to the 7.1 stable tree and since i find some wired looking entries in my ipv6 routing table:

  DAd  XXXX:XX:5722:8180::/57                                                      1
  DIoH XXXX:XX:5722:8180::/64       LAN-INT                                      110
  DAc  XXXX:XX:5722:8180::/64       LAN-INT                                        0
  DIoH XXXX:XX:5722:8181::/64       LAN-SRV                                      110
  DAc  XXXX:XX:5722:8181::/64       LAN-SRV                                        0
  DIoH XXXX:XX:5722:8182::/64       WLAN-SEC                                     110
  DAc  XXXX:XX:5722:8182::/64       WLAN-SEC                                       0
  DIoH XXXX:XX:5722:8183::/64       WLAN-INT                                     110
  DAc  XXXX:XX:5722:8183::/64       WLAN-INT                                       0

These are from a prefix i got delegated and im announcing on my local interfaces. I have the same behavior for site-local prefixes i announce:

  DAc  fc00:1:2:3::/64     LAN-SRV                                        0
  DIoH fc00:1:2:3::/64     LAN-SRV                                      110
  DAc  fc00:1:2:4::/64     LAN-INT                                        0
  DIoH fc00:1:2:4::/64     LAN-INT                                      110

The networks are exported to OSPF, but the route entries do not make any sense, as the 4011 shouldn’t have HW-offloading. Did i mention that the route entries cannot be deleted?

Has anyone else seen smth. like this? This is a config converted from ROS6 were it was working just fine, but maybe things are done differently on v7?
Thanks!

2

Okay, so the entries have something to do with OSPFv3. When I disable the v3 instance those strange entries are gone from the routing table.
I’m using this OSPFv3 config:

/routing id
add disabled=no id=10.255.255.2 name=id-1 select-dynamic-id=""
/routing ospf instance
add name=default-v3 router-id=id-1 version=3
/routing ospf area
add instance=default-v3 name=backbone-v3
add area-id=0.0.0.18 instance=default-v3 name=local-v3
/routing ospf interface-template
add area=backbone-v3 cost=10 interfaces=IPv6-BB1 priority=1 type=ptp
add area=backbone-v3 cost=10 interfaces=IPv6-BB2 priority=1 type=ptp
add area=local-v3 cost=10 interfaces=LAN-INT passive priority=1
add area=local-v3 cost=10 interfaces=WLAN-SEC passive priority=1
add area=local-v3 cost=10 interfaces=WLAN-INT passive priority=1
add area=local-v3 cost=10 interfaces=LAN-SRV passive priority=1

It almost seams like the 4011 is learning its own LSAs and then invalidating them. Very strange!

3

Same problem, version 7.6

4

This has been the case for a long time now. I think it is lower priority to get fixed as it doesn’t cause any issues other than the routing table being larger than it needs to be.