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
router 10.255.255.201
distance 1
router 10.255.255.11 metric 1
stubnet 2a09:4c2:1f:ff:ff::201/128 metric 1
stubnet 2a09:4c2:1f:ff:91::/127 metric 1

birdc show interfaces (all other interfaces than loopback0 has been left out)
BIRD 2.0.7 ready.
<snip>
loopback0 up (index=3)
MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
2a09:4c2:1f:ffff::/128 (Preferred, scope univ)
fe80::500e:2eff:feb5:8b1d/64 (Preferred, scope link)
<snip>

ip addr show (all other interfaces than loopback0 has been left out)
<snip>
3: loopback0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 52:0e:2e:b5:8b:1d brd ff:ff:ff:ff:ff:ff
    inet6 2a09:4c2:1f:ffff::/128 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::500e:2eff:feb5:8b1d/64 scope link
       valid_lft forever preferred_lft forever
<snip>

Best Regards
Anders Hansen


On Fri, Jan 31, 2020 at 10:54 PM Ondrej Zajicek <santiago@crfreenet.org> wrote:
On Fri, Jan 31, 2020 at 09:58:23PM +0100, Anders Hansen wrote:
> Hi list
>
> I'm having issues with a Debian 10 based router running BIRD 2.0.7.
>
> On the router I have several interfaces where OSPFv3 is active. All good.
> Besides those interfaces, i also have a dummy interface named loopback0.
>
> Config example:
>         area 0 {
>                 interface "ens*" {
>                         type ptp;
>                         cost 1;
>                         hello 5;
>                 };
>                 interface "loopback0" {
>                         stub;
>                         cost 1;
>                 };
>         };
>
> The ens interfaces work just fine. However, the /128 I have configured on
> the loopback0 interfaces is constantly not being picked up by BIRD. It's
> like BIRD completely ignores the existence of that interface. It simply
> won't announce that /128 out to its peers connected through the ens
> interfaces. If i change the /128 to a /127 instead, the prefix is
> advertised by bird.

Hi

Works for me. What is reported by 'birdc show ospf state',
'birdc show interfaces' and 'ip addr show' commands ?

--
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."