Unable to establish ospf6 adjacency when attached to a vrf

[ChrisHills463]

Describe the bug

Using the frr docker image quay.io/frrouting/frr:8.5.2 I am unable to establish ospf6 adjacency in a vrf, wheras the equivalent non-vrf configuration works as expected, and the ospf adjacency is established for both non-vrf and vrf networks.

• Did you check if this is a duplicate issue?
• Did you test it on the latest FRRouting/frr master branch?

To Reproduce

• pe1 config

pe1:/# ip link add internet type vrf table 10
pe1:/# ip link set eth1 master internet
pe1:/# cat /etc/frr/frr.conf
frr version 8.5.2_git
frr defaults traditional
hostname pe1
log stdout informational
ipv6 forwarding
!
interface eth1 vrf internet
 ip address 20.20.20.0/31
 ip ospf area 0
 ipv6 address 2a20::/127
 ipv6 ospf6 area 0
exit
!
interface eth2
 description To pe2
 ip address 10.10.10.0/31
 ip ospf area 0
 ipv6 address 2a10::/127
 ipv6 ospf6 area 0
exit
!
router ospf
 ospf router-id 10.10.10.0
exit
!
router ospf vrf internet
 ospf router-id 20.20.20.0
exit
!
router ospf6
 ospf router-id 10.10.10.0
exit
!
router ospf6 vrf internet
 ospf router-id 20.20.20.0
exit
!
end

• pe2 config

pe1:/# ip link add internet type vrf table 10
pe1:/# ip link set eth1 master internet
pe1:/# cat /etc/frr/frr.conf
frr version 8.5.2_git
frr defaults traditional
hostname pe2
log stdout informational
ipv6 forwarding
!
interface eth1 vrf internet
 ip address 20.20.20.1/31
 ip ospf area 0
 ipv6 address 2a20::1/127
 ipv6 ospf6 area 0
exit
!
interface eth2
 ip address 10.10.10.1/31
 ip ospf area 0
 ipv6 address 2a10::1/127
 ipv6 ospf6 area 0
exit
!
router ospf
 ospf router-id 10.10.10.1
exit
!
router ospf vrf internet
 ospf router-id 20.20.20.1
exit
!
router ospf6
 ospf router-id 10.10.10.1
exit
!
router ospf6 vrf internet
 ospf router-id 20.20.20.1
exit
!
end

Expected behavior

Running show ipv6 ospf6 vrf internet neighbor on pe1 or pe2 should show a neighbor.

Screenshots

pe1# show ip ospf neighbor 
Neighbor ID     Pri State           Up Time         Dead Time Address         Interface                        RXmtL RqstL DBsmL
10.10.10.1        1 2-Way/DROther   12.612s           37.387s 10.10.10.1      eth2:10.10.10.0                      0     0     0

pe1# show ip ospf vrf internet neighbor 
VRF Name: internet
Neighbor ID     Pri State           Up Time         Dead Time Address         Interface                        RXmtL RqstL DBsmL
20.20.20.1        1 2-Way/DROther   0.828s            39.171s 20.20.20.1      eth1:20.20.20.0                      0     0     0

pe1# show ipv6 ospf6 neighbor 
Neighbor ID     Pri    DeadTime    State/IfState         Duration I/F[State]
10.10.10.1        1    00:00:33     Full/DR              00:00:21 eth2[BDR]

pe1# show ipv6 ospf6 vrf internet neighbor 
Neighbor ID     Pri    DeadTime    State/IfState         Duration I/F[State]

Versions

• OS Version: Host: Debian 10.11 // Guest: Alpine Linux 3.17.4 (from frrouting/frr:8.5.2)
• Kernel: 4.19.0-17-amd64
• FRR Version: 8.5.2

Additional context

I also noticed that the IPv6 address does not get set for the vrf interface, whereas the ipv4 address is set as expected.

pe1:/# ip addr show dev eth1
35109: eth1@if35108: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9500 qdisc noqueue master internet state UP group default 
    link/ether aa:c1:ab:cf:e8:7f brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet 20.20.20.0/31 brd 255.255.255.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::a8c1:abff:fecf:e87f/64 scope link 
       valid_lft forever preferred_lft forever

35111: eth2@if35110: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9500 qdisc noqueue state UP group default 
    link/ether aa:c1:ab:c0:13:90 brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet 10.10.10.0/31 brd 255.255.255.255 scope global eth2
       valid_lft forever preferred_lft forever
    inet6 2a20::/127 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::a8c1:abff:fec0:1390/64 scope link 
       valid_lft forever preferred_lft forever

[github-actions]

This issue is stale because it has been open 180 days with no activity. Comment or remove the autoclose label in order to avoid having this issue closed.

[frrbot]

This issue will be automatically closed in the specified period unless there is further activity.

[xanderZ7]

Has this issue been fixed, or has a solution been found?