announce IPV4 loopback via an OSPF v3 backbone

Pim van Pelt pim at ipng.ch
Sat Mar 30 16:04:34 CET 2024


Hoi,

On 3/30/24 15:50, Pim van Pelt wrote:
> OSPFv3 adjacency did establish, but no routes were exchanged (also 
> none with filter 'export all; import all;') --
As a quick follow up to this: routes are exchanged, but they are not 
emitted to the kernel.
root at vpp0-2:~# birdc show ospf state
BIRD 2.14 ready.

area 0.0.0.0

         router 192.168.10.2
                 distance 0
                 router 192.168.10.3 metric 5
                 stubnet 192.168.10.2/32 metric 0
                 stubnet 192.168.10.2/32 metric 0
                 stubnet 192.168.10.2/32 metric 0
                 external 192.168.10.2/32 metric2 10000
                 external 192.168.10.0/24 metric2 10000

        router 192.168.10.3
                 distance 5
                 router 192.168.10.2 metric 5
                 stubnet 192.168.10.3/32 metric 0
                 stubnet 192.168.10.3/32 metric 0
                 stubnet 192.168.10.3/32 metric 0
                 external 192.168.10.3/32 metric2 10000

I am not seeing any Netlink route messages for any of the LSAs from 
neighbor 192.168.10.3 (colored in red above).
Could it be that when using an ipv4 channel with OSPFv3, Bird ought to 
program these across address families?

|pim at vpp0-2:~$ sudo ip ro add 192.168.10.3/32 via inet6 
*fe80::5054:ff:fef0:1130* dev e1
|
groet,
Pim

-- 
Pim van Pelt
PBVP1-RIPE -https://ipng.ch/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20240330/c6c1b5e8/attachment.htm>


More information about the Bird-users mailing list