- Bird-users - Mailing Lists

why ABR flood lsa3 to non-backbone area?
by chan alfie 06 May '24

06 May '24

hi community, I got some confused of ospf lsa3. topology: r1 --a12-- r2 --a0-- r3 --a34-- r4 | | +---a23 ---+ r1(intf:r1r2) and r2(intf:r2r1) are belong to area 12, ptp network: 10.0.12.0/30 r2(intf:r20r30) and r3(intf:r30r20) are composed to area 0, ptp network: 10.0.100.0/30 r2(intf:r2r3) and r3(intf:r3r2) are composed to area 0, ptp network: 10.0.23.0/30 r3(intf:r3r4) and r4(intf:r4r3) are cmposed to area 34, ptp network: 10.0.34.0/30 r1 has a stub net: 10.1.1.0/30 r4 has a stub net: 10.4.2.0/30 why r2/r3 regenerated lsa3 and advertise on area 23, isn't it prohibited ABR to flood lsa3 to non-backbone area? r2 ``` bird> s o l type 3 area 23 Area 0.0.0.23 Type LS ID Router Sequence Age Checksum 0003 10.0.12.3 10.0.0.2 80000004 1088 6885 0003 10.0.34.3 10.0.0.2 80000004 1064 d9f3 0003 10.0.100.3 10.0.0.2 80000004 1088 9cf8 0003 10.1.1.3 10.0.0.2 80000004 1070 3ab3 0003 10.4.2.3 10.0.0.2 80000004 1060 6f70 0003 10.0.12.3 10.0.0.3 80000004 1063 c61c 0003 10.0.34.3 10.0.0.3 80000004 1069 6f67 0003 10.0.100.3 10.0.0.3 80000004 1069 96fd 0003 10.1.1.3 10.0.0.3 80000004 1063 984a 0003 10.4.2.3 10.0.0.3 80000004 1062 05e3 ```

1 0

build: symbol ‘bfd_auth_type’ is used, but is not defined as a token and has no rules
by Zhang Maiyun 01 May '24

01 May '24

Hello, I was trying to build the latest commit and encountered this error: nest/config.Y:615.19-31: error: symbol ‘bfd_auth_type’ is used, but is not defined as a token and has no rules It looks like commit e6dbde688 introduced a dependency on the type `bfd_auth_type` into `nest/config.Y`. However, if protocol bfd is not enabled (e.g. because of disabling pthreads), `proto/bfd/config.Y` won’t get included in the parser and thus `bfd_auth_type` is undefined. Perhaps this should be fixed? Thanks! Maiyun Zhang (he/him)

1 0

BIRD at various meetings (until Jun 2024)
by Maria Matejka 30 Apr '24

30 Apr '24

Dear BIRD users, I'd like to share our preliminary meeting schedule with you. * I was talking at NANOG 90 in Charlotte, NC, USA, about lossless prefix aggregation for forwarding. See the recording here: https://www.youtube.com/watch?v=35xgLPoQags * Ondřej Zajíček is going to talk about our development state at the upcoming Euro-IX Route Server Workshop (not public, afaik) * I'm going to remotely participate at IETF 119 (mid-March). If you wanna direct me to any specific working group which I should join, feel free to send me a pointer. * We're planning to attend Euro-IX 40th Forum and RIPE 88 in person (more info later). * We may attend NANOG 91 and IETF 120 remotely. We're just a small busy team, we can't be everywhere. We very much appreciate when anybody presents about using BIRD in any setup. Also, if there are any meetings with remote attendance possible where BIRD talks happen, or even just recordings, please let us know – we love all the feedback! We occasionally get some links. Thank you for all of that! Also if you really wish us to be at some meeting, please let us know. As you probably can see, we are now trying the cover the main meetings of North America and Europe. There are some thoughts about covering other regions, not realized yet, with no definitive timelines. With all that, have a nice time and hopefully see you soon! Happy routing! Maria -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.

1 1

"<ERR> bfd1: Socket error: Destination address required"
by Fran 30 Apr '24

30 Apr '24

Hello there, I get the error message: "<ERR> bfd1: Socket error: Destination address required" (ubuntu 22.04, bird via ppa 2.15.1) running BFD and MP-BGP via IPv6 over wireguard interfaces. Not all BGP neighbors are reachable. Relevant (I hope) config: log "/var/log/bird/bird.log" all; protocol device { } protocol bfd { accept ipv6 direct; interface "wg_blue*"; interface "wg_green" { multiplier 3; interval 500 ms; }; neighbor 2001:db8:f000::2 dev "wg_green" local 2001:db8:f000::1; neighbor 2001:db8:f000:ffff::2 dev "wg_blue2" local 2001:db8:f000:ffff::1; neighbor 2001:db8:f000:fffc::5 dev "wg_blue1" local 2001:db8:f000:fffc::1; neighbor 2001:db8:f000:fffc::4 dev "wg_blue1" local 2001:db8:f000:fffc::1; neighbor 2001:db8:f000:fffc::3 dev "wg_blue1" local 2001:db8:f000:fffc::1; neighbor 2001:db8:f000:fffc::2 dev "wg_blue1" local 2001:db8:f000:fffc::1; } protocol bgp EXAMPLE { local as 65001; neighbor 2001:db8:f000::2 as 65044; direct; med metric yes; ipv4 { ... }; ipv6 { ... }; bfd on; } If I remove the BFD config for the non-established BGP neighbors, the error message disappears (although there are still non-established BFD sessions for established BGP neighbors (BFD not yet confed on the other end)). At first I did not create neighbor statements for BFD, then I added "dev" and "local" options - no improvement. No revelations with "debug protocols all". Any ideas? Thanks a lot! Best, fran

3 4

Large communities indicating RPKI VALID status
by Nigel Kukard 30 Apr '24

30 Apr '24

Hi all, I was busy reading https://bgpfilterguide.nlnog.net/guides/reject_invalids/ and noticed the following text... Note: REALLY DONT store the validation state inside a bgp_community or bgp_large_community or bgp_ext_community variables. It can cause CPU & memory overload resulting in convergence performance issues. I was wondering if this is still an issue and if it would still be a bad idea to indicate that RPKI was VALID using communities on multiple full BGP feeds? Is anyone doing this at present? are you seeing significant load? Kind Regards Nigel

7 10

`default cost` setting is not applied
by Benoit Chesneau 29 Apr '24

29 Apr '24

Hi, I have the following configuration: ``` define ospf_v4_routes = [ 198.19.0.0/16 ]; filter ospf_export { if (net.type = NET_IP4 && ! (net ~ [ 0.0.0.0/0 ])) then reject; accept; } filter ospf_import { if (net.type = NET_IP4 && net ~ ospf_v4_routes) then accept; reject; } protocol ospf v2 ospfv4 { debug all; ipv4 { import filter ospf_import; export filter ospf_export; }; area 0.0.0.0 { interface "lo1" { stub yes; }; interface "vlan600" { type ptp; cost 15; bfd on; }; };} ``` I would expect the metric around 300 + cost of the interface but I get this route metric "E2 0.0.0.0/0 [15/10000] via 198.19.4.65, vlan600" in the switch. When I set the metric manually in the export function: ``` filter ospf_export { if (net.type = NET_IP4 && ! (net ~ [ 0.0.0.0/0 ])) then reject; ospf_metric1 = 300; unset(ospf_metric2); accept;} ``` I get the correct metric: ``` E1 0.0.0.0/0 [315] via 198.19.4.65, vlan600 ``` Any idea what could be the issue ? Did I misunderstood the usage of the `default cost` setting? Benoît

1 0

How to set ospf as external route as ext1?
by chan alfie 29 Apr '24

29 Apr '24

The default ospf ASE will be set as rts_ospf_ext2, how to change it, and set the ospf ASE as rts_ospf_ext1?

2 1

How to make ospf advertise stubnet base on the interface/subnet state?
by chan alfie 29 Apr '24

29 Apr '24

Hi, community I have create a loopback interface on linux and assign 4 subnets on it. ``` ip link add dev lo235 type dummy ip link set lo235 up ip addr add 10.23.5.1/30 dev lo235 ip addr add 10.23.5.5/30 dev lo235 ip addr add 10.23.5.9/30 dev lo235 ip addr add 10.23.5.13/30 dev lo235 ``` stubnet <prefix> { summary;}; is used on an originator routers(r235) ospf area, and it indeed propagted the summary prefix instead of subnets, here is the config: r235: ``` area 10.23.0.0 { ... stubnet 10.23.5.0/28 { summary; } ... } ``` r235: ``` show ospf state ... router 10.23.0.5 distance 0 ... stubnet 10.23.5.0/28 metric 10 ... ``` but when I shutdown the lo235 or delete all of the subnets, the 10.23.5.0/28 is still advertised by r235. r235 ``` ip link set lo235 down or ip addr del 10.23.5.1/30 dev lo235 ip addr del 10.23.5.5/30 dev lo235 ip addr del 10.23.5.9/30 dev lo235 ip addr del 10.23.5.13/30 dev lo235 ``` r235 ``` bird> show ospf state router 10.23.0.5 distance 0 ... stubnet 10.23.5.0/28 metric 10 ``` How to make ospf advertise stubnet base on the interface/subnet state, (interface up/down, subnets existed or not)? By the way, networks{} clause works as expected. When the subnet of originator router is dismiss, the ABR's networks will take effect(disappear of appear).

2 1

IPv4 next-hops over IPv6
by Jay Hanke 28 Apr '24

28 Apr '24

Has anyone implemented lab or production IPv4 next hops over an IPv6 only IX vlan with BIRD as the route server? I'm interested to hear your experiences. Specifically router vendor interop. Jay

7 12

Current bird via bookworm-backports?
by Oliver Seufer 26 Apr '24

26 Apr '24

Hello, The version 2.0.12 included in Debian Bookworm unfortunately lacks a few current features. I would therefore greatly appreciate it if a Debian package with the latest version could be provided. Either through bookworm-backports or directly through bird.network.cz Is there a possibility that this will be provided by the bird project? Like it was done for Debian Bullseye back then? I greatly appreciate your work on bird, and I also enjoy trying out new features. Best regards, Oliver Seufer

7 11