Once fixed though, I have the same results. routes are not applied to the kernel. ospfv3. Applying a `/31` to the point to point interface:
```
vlan200: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
options=4600703<RXCSUM,TXCSUM,TSO4,TSO6,LRO,RXCSUM_IPV6,TXCSUM_IPV6,MEXTPG>
ether 9a:c7:bd:e8:62:dc
inet 10.200.1.1 netmask 0xfffffffe broadcast 255.255.255.255
inet6 fe80::98c7:bdff:fee8:62dc%vlan200 prefixlen 64 scopeid 0x4
groups: vlan
vlan: 200 vlanproto: 802.1q vlanpcp: 0 parent interface: iavf0
media: Ethernet autoselect (10Gbase-SR <full-duplex>)
status: active
nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> ```
allows the route to be shared . Configuration is :
```
protocol ospf v3 ospfv4 { ipv4 {
import filter ospf_import;
export filter ospf_export;
};
area 0 {
interface "lo1" { stub yes; };
interface "vlan200" {
type ptp;
cost 10;
};
};
} ```
Benoît Chesneau, Enki Multimedia
—
t. +33608655490
On Sunday, March 31st, 2024 at 01:42, Benoit Chesneau <benoitc@enki-multimedia.eu> wrote:
I get the same result as well. On freebsd when starting I also get this message " Cannot find next hop address".
On Saturday, March 30th, 2024 at 16:04, Pim van Pelt via Bird-users <bird-users@network.cz> wrote:
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@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@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/