On Wed, Mar 27, 2024 at 09:08:35AM +, Benoit Chesneau wrote:
> Hi everyone,
>
> I was reading the ospv3 spec and this link
> https://networklessons.com/ospf/ospfv3-for-ipv4- and was wondering if such
> features is supported in bird 2. Can we announce loopbacks via OSPFv3 and
> remove the
correction: the error message is not related particularly to bird but seems
related to this issue in latest freebsd release:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275341
Once fixed though, I have the same results. routes are not applied to the
kernel. ospfv3. Applying a `/31` to
I get the same result as well. On freebsd when starting I also get this message
" Cannot find next hop address".
Benoît
On Saturday, March 30th, 2024 at 16:04, Pim van Pelt via Bird-users
wrote:
> Hoi,
>
> On 3/30/24 15:50, Pim van Pelt wrote:
>
>> OSPFv3 adjacency did establish, but no
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
Hoi,
On 3/27/24 10:08, Benoit Chesneau wrote:
I was reading the ospv3 spec and this
linkhttps://networklessons.com/ospf/ospfv3-for-ipv4-
and was wondering if such features is supported in bird 2. Can we
announce loopbacks via OSPFv3 and remove the need to use OSPFv2 and ptp
subnets ?
I
