Thanks, Ondrej. The other end is a Mikrotik and it could seem that you are correct in your statement.

/routing ospf-v3 lsa print detail where originator=10.255.255.11
instance=default area=backbone type=router id=0.0.0.0 originator=10.255.255.11 sequence-number=0x80000233 age=919 checksum=0x5E3 options="V6|E|R" body=
flags=EXTERNAL
link-type=Point-To-Point iface-id=18 neighbor-iface-id=18 neighbor-routerId=10.255.255.201 metric=1

instance=default area=backbone type=intra-area-prefix id=0.0.0.0 originator=10.255.255.11 sequence-number=0x800000DC age=925 checksum=0x30EC options="" body=
referenced-LS-type=Router LSA
referenced-LS-ID=0
prefix=2a09:4c2:1f:ffff::/128 options=01000000 (LA)
prefix=2a09:4c2:1f:ff:91::/127 options=00000000

So both the linknet and the loopback seems to be advertised correctly, by BIRD. However, i'm unsure what the LA means here - but thats a Mikrotik subject, i suppose, so i'll go there and ask for help.

Again, thanks Ondrej and i'm very sorry for believing this was a BIRD issue :)

Best Regards

Anders Hansen

On Sat, Feb 1, 2020 at 5:37 PM Ondrej Zajicek <santiago@crfreenet.org> wrote:

On Sat, Feb 01, 2020 at 01:03:31PM +0100, Anders Hansen wrote:
> I suppose I must be doing something wrong then :)
> Here's the output from the commands:
>
> birdc show ospf state
> BIRD 2.0.7 ready.
> area 0.0.0.0
> router 10.255.255.11
> distance 0
> router 10.255.255.201 metric 1
> stubnet 2a09:4c2:1f:ffff::/128 metric 0
> stubnet 2a09:4c2:1f:ff:91::/127 metric 1

Seems like the address is picked by BIRD and properly incorporated into
LSAdb. Perhaps the other side ignores it for some reason?

--
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."