hello,
i'm running into a crash on 2.16.1 on FreeBSD/amd64 15.0. it happens
sometimes (not always) when reconfiguring BIRD with BFD enabled.
(gdb) run -f
Starting program: /usr/local/bird/sbin/bird -f
[New LWP 101873 of process 58914]
Thread 2 received signal SIGSEGV, Segmentation fault.
Addres
Maria Matejka:
> Well, OSPF isn't intended for filtering routes between areas this way.
> Guessing from what you have written, it may make sense e.g. to run one
> OSPF instance per area, assign each area a BGP private ASN and run BGP
> between them.
thanks Maria and Ondrej, after thinking about th
hello,
it's me again, with my OSPF network.
i was reading this blog post:
https://ipng.ch/s/articles/2024/04/06/vpp-with-loopback-only-ospfv3-part-1/
which seems to suggest that Ondrej had done some work on advertising
IPv4 prefixes into OSPFv3 with IPv6 nexthop in BIRD.
however, it's not entire
hello,
i'm using BIRD 2.16.1 on FreeBSD 15.0.
i have an OSPF ABR in area 0 and area 1. this router has a default
route via a non-OSPF interface (kernel route, imported into BIRD using
the 'kernel' protocol). i'd like to advertise this route into area 1,
but *not* into area 0.
how would i go ab
Ondrej Zajicek:
> Note that confederations in BIRD are a bit tricky. There are two styles:
> 1) Shared IGP:
> In this case, intra-confederation EBGP links should have an option
> 'gateway recursive', so bgp_next_hop is resolved recursively through
> shared IGP routes.
i see, i thought EBGP with
hello,
recently i noticed some entries in syslog like this:
Mar 15 11:03:22 uk-myb-2 bird[60388]: nl-myb-1: Invalid NEXT_HOP attribute -
neighbor address fd5b:a83:b06b:500::1
Mar 15 11:03:22 uk-myb-2 bird[60388]: nl-myb-1: Invalid route 172.20.212.0/26
withdrawn
Mar 15 11:03:22 uk-myb-2 bird[60
Ondrej Zajicek:
> On Sat, Mar 15, 2025 at 11:07:04AM +0000, Lexi Winter via Bird-users wrote:
> > Mar 15 11:03:22 uk-myb-2 bird[60388]: nl-myb-1: Invalid NEXT_HOP attribute
> > - neighbor address fd5b:a83:b06b:500::1
> > Mar 15 11:03:22 uk-myb-2 bird[60388]: nl
Maria Matejka via Bird-users:
> In short, there are two different route attributes in BIRD 2:
> - The whole route's total metric from here to the destination,
> if set explicitly by `igp_metric = N` in filters.
> I.e., a generic alternative to protocol-specific IGP metrics
> like `ospf_metr
