April 2023 - Bird-users - Mailing Lists

BIRD 3.0alpha1
by Ondrej Filip 28 Apr '23

28 Apr '23

Dear BIRD Users, we're presenting you a new alpha version of the Multithreaded BIRD. Contrary to the previous version, you have to set your desired number of threads in config by the threads N; option. Version 3.0alpha1 fixes a lot of bugs found in previous versions. Our tests show that the overall performance may be about 3-8 times better than v2.0.12; yet the real life always brings questions and problems which the development can't anticipate fully. Please run your tests and we hope we get back to you soon with a stable version. Looking forward to your reports. I thank my colleagues and namely Maria for this release! Cheers Ondrej

6 7

New to routing: radv Network not found?
by Alessandro Vesely 26 Apr '23

26 Apr '23

Hi all, I installed bird2 (Debian stock) and configured radv, following the documented example. When bird it started, it said: Apr 24 12:36:55 31 north bird: static1: Channel ipv6 connected to table radv_routes Apr 24 12:36:55 31 north bird: static1: Initializing Apr 24 12:36:55 31 north bird: radv1: Channel ipv6 connected to table radv_routes Apr 24 12:36:55 31 north bird: radv1: Initializing Apr 24 12:36:55 31 north bird: static1: Starting Apr 24 12:36:55 31 north bird: static1: State changed to up Apr 24 12:36:55 31 north bird: radv1: Starting Apr 24 12:36:55 31 north bird: radv1: State changed to up Apr 24 12:36:55 30 north bird: Started Apr 24 12:36:55 31 north bird: radv1 < interface eth2r created Apr 24 12:36:55 31 north bird: radv1 < interface ppp0 created No more logging. After some hours I get this: 541-north:bird# birdc show route for 2a02:29e1:300:e922::2 BIRD 2.0.7 ready. Network not found What does it mean? I configured static routes in the kernel. Perhaps I should only configure them in bird. 542-north:bird# ip route get 2a02:29e1:300:e922::2 2a02:29e1:300:e922::2 from :: dev eth2r proto kernel src 2a02:29e1:300:e922::1 metric 256 pref medium My ISP assigned to me 2a02:29e1:300:e900/56. I have a few addresses assigned locally, and 2a02:29e1:300:e922::1 to the lan interface (eth2r), reserving that /64 for lan hosts. A neighboring PC has 2a02:29e1:300:e922::2/64. External routing doesn't work, but this is another question (also asked on stackexchange: https://unix.stackexchange.com/questions/742826/ipv6-over-pppoe) There must be something wrong in the config, which I don't know how to fix. I paste it below. What did I get wrong? TIA Ale -----8<----- # This is a basic configuration file, which contains boilerplate options and # some basic examples. It allows the BIRD daemon to start but will not cause # anything else to happen. # # Please refer to the BIRD User's Guide documentation, which is also available # online at http://bird.network.cz/ in HTML format, for more information on # configuring BIRD and adding routing protocols. # Configure logging log syslog all; # Set router ID. It is a unique identification of your router, usually one of # IPv4 addresses of the router. It is recommended to configure it explicitly. router id 185.8.198.188; # Turn on global debugging of all protocols (all messages or just selected classes) debug protocols all; debug protocols { interfaces, states }; ipv6 table radv_routes; # Manually configured routes go here protocol static { ipv6 { table radv_routes; }; route 2a02:29e1:300:e922::/64 via "eth2r"; route 2a02:29e1:300:e900::/56 unreachable; route ::0/0 via "ppp0"; } protocol radv { propagate routes yes; # Propagate the routes from the radv_routes table ipv6 { table radv_routes; export all; }; interface "ppp0" { prefix ::/0 { autonomous off; # So do not autoconfigure any IP }; }; interface "eth2r"; # No need for any other options } ----->8-----

4 8

BIRD 1 - End Of Life: Dec 31, 2023
by Ondrej Filip 25 Apr '23

25 Apr '23

Dear BIRD users and friends, BIRD 2 has been here since 2017. The joint daemon of IPv6 and legacy IP quickly become stable and its last version is 2.13 just couple days old. Last version of BIRD 1 was 1.6.8 released in September 2019. We have already declared that we wouldn't release any other version of legacy BIRD 1 unless a serious security bug is found. It's time to say that BIRD 1 is reaching its end of life at the end of the year 2023. Please upgrade to BIRD 2 if you're still running BIRD 1. If you are waiting for BIRD 3, you can stay assured that upgrade from BIRD 2 to BIRD 3 will be smooth. Thank you for your ongoing support and understanding Ondrej & BIRD team

6 6

BIRD 2.13
by Ondrej Filip 24 Apr '23

24 Apr '23

Hello! It is very unusual for us, be we have two releases in one week. New version 2.13 is out. As you can see we changed versioning scheme from <epoch>.<major>.<minor> to more common <major>.<minor>.<patch> . From now on, you may expect that BIRD 2.13.x will be strictly only fixing bugs found in 2.13, whereas BIRD 2.14 will also contain new features. I thank my colleagues and namely Santiago for this release! Version 2.13 o Babel: IPv4 via IPv6 extension (RFC 9229) o Babel: Improve authentication on lossy networks o BGP: New 'allow bgp_med' option o BSD: Support for IPv4 routes with IPv6 nexthop on FreeBSD o Experimental BMP protocol implementation o Important bugfixes Notes: This BIRD version contains an alpha release of BMP protocol implementation. It is not ready for production usage and therefore it is not compiled by default and have to be enabled during installation.

2 2

Potential issue in RIP: missing handing rtes in rip_receive_request
by Mingwei Zheng 24 Apr '23

24 Apr '23

Hi, I am doing testing work on network protocols and there is one possible issue I noticed in RIP: When packet command is RIP_CMD_UPDATE_REQUEST, the protocol will call function rip_receive_request to respond to request called from rip_rx_hook. In RFC2453: https://datatracker.ietf.org/doc/html/rfc2453#section-3.9.1 Examine the list of RTEs in the Request one by one. For each entry, look up the destination in the router's routing database and, if there is a route, put that route's metric in the metric field of the RTE. If there is no explicit route to the specified destination, put infinity in the metric field. Once all the entries have been filled in, change the command from Request to Response and send the datagram back to the requestor. However in the function rip_receive_request, it seems that only one rte is examined. Could you please take a look at this part? I would really appreciate it. Thank you! Best, Mingwei

2 1

Bird installation from source code error with during make
by saifullah＠fiberathome.net 23 Apr '23

23 Apr '23

Hi, I am getting following error during make in Ubuntu server. Please help me. make: *** [Makefile:113: obj/client/birdc.o] Error 1 Thanks & Regards Saifullah Nasar Connecting our future with light

1 0

[PATCH] IPv4 over IPv6 nexthop support on FreeBSD
by Luiz Amaral 21 Apr '23

21 Apr '23

Hello, While experimenting in FreeBSD 13.1 with IPv4 over IPv6 nexthop routes, I realized that BIRD was unable to read routes from the kernel as well as export routes to the kernel. The support for it was implemented in FreeBSD 13.1 [1]. I have attached a patch that made it work for me on FreeBSD 13.1, both importing and exporting to/from kernel. I believe the patch will still need some work, as from a quick look, OpenBSD still has no support for it. I'm happy to implement any suggested improvements and send a v2 of it. Thank you, Luiz [1] https://reviews.freebsd.org/D30398

3 7

RE: BIRD is taking too much time to converge 106362 prefixes from a non-client iBGP neighbor
by saifullah＠fiberathome.net 19 Apr '23

19 Apr '23

Hi CPU MHz: 2494.140. I found the BIRD is using different CPU at different time and it’s crossing 100% utilization using command “htop”. It’s happening when I am trying to establish a neighbor where prefix count is more than 106K. I found that BIRD3 support multi-core. Is there any way to install BIRD 3? Thanks & Regards Abu Nasar Md. Saifullah From: Darshan Kowlaser <darshan(a)darshankowlaser.com> Sent: Tuesday, April 18, 2023 11:00 PM To: saifullah(a)fiberathome.net Subject: Re: BIRD is taking too much time to converge 106362 prefixes from a non-client iBGP neighbor Hi Something to consider is that BGP on BIRD runs on a single core. If you slow clock speed you are going to run into issues? What is the CPU utilization while the BIRD daemon stopped? On Tue, Apr 18, 2023 at 6:18 PM <saifullah(a)fiberathome.net <mailto:saifullah@fiberathome.net> > wrote: Hi Dear, Thank you for your feedback. The server I am using of 16 VCPU with 2 threads per CPU and 16 GB RAM. I found that CPU utilizations is crossing 100% in a CPU. Any way to install and configure BIRD so that it uses all CPU simultaneously? Thanks & Regards Abu Nasar Md. Saifullah -----Original Message----- From: Ondrej Zajicek <santiago(a)crfreenet.org <mailto:santiago@crfreenet.org> > Sent: Monday, April 17, 2023 6:17 PM To: saifullah(a)fiberathome.net <mailto:saifullah@fiberathome.net> Cc: bird-users(a)network.cz <mailto:bird-users@network.cz> Subject: Re: BIRD is taking too much time to converge 106362 prefixes from a non-client iBGP neighbor On Thu, Apr 13, 2023 at 11:47:12PM +0600, saifullah(a)fiberathome.net <mailto:saifullah@fiberathome.net> wrote: > Hi, > > Thanks for your feedback. The topology is BIRD is connected with total > 8 neighbors (1 is non-client and 7 are in client mode) for my setup. > The non-client neighbor is actually a high end central RR router which > advertise about 106k prefixes to BIRD and with other 7 client, the > prefix count is below 100. > > 1. During that time, I have checked and found that CPU load was normal. > 2. I also checking prefix count using command "show protocols all > <non_client_neighbor>" and found prefixes were increasing gradually. Hi If CPU was normal (idle), then it is unlikely an issue with BIRD. Prefixes are processed as they arrive, so they are delayed only if BIRD cannot catch up and use 100% CPU (note that it is single-threaded, so you have to check load on individual CPUs and not aggregate load, like is default in 'top'). Perhaps the other side send prefixes slowly? -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago(a)crfreenet.org <mailto:santiago@crfreenet.org> ) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net <http://wwwkeys.pgp.net> ) "To err is human -- to blame it on a computer is even more so." Connecting our future with light Connecting our future with light

2 1

BIRD is taking too much time to converge 106362 prefixes from a non-client iBGP neighbor
by saifullah＠fiberathome.net 18 Apr '23

18 Apr '23

Dear Concern, After installing BIRD, I made iBGP neighbor with 8 routers. From a non-client neighbor it should receive about 106362 prefixes but I found it is taking huge time to process and converge the mentioned prefixes. It took about 35 minutes to process, converge and advertise prefixes to other neighbors. Is it normal behavior or am I missing sometime to make faster convergence? Kindly suggest me. Related configuration parts are given below (actual IP and names are changed): router id <local_ip>; vpn4 table vpntab4; template bgp template_rr_non_client { local <local_ip> as as_number; neighbor as as_number; vpn4 mpls { table vpntab4; import all; export all; }; } protocol bgp <non_client_neighbor> from template_rr_non_client { neighbor non_client_neighbor_ip; } template bgp template_rr_client2 { local <local_ip> as as_number; neighbor as as_number; rr client; rr cluster id <local_ip>; vpn4 mpls { table vpntab4; import all; export all; }; } # protocol bgp client1 from template_rr_client2 { neighbor client1_ip; . . . } protocol bgp client7 from template_rr_client2 { neighbor client7_ip; } Thanks & Regards Saifullah Nasar Connecting our future with light

2 7

Sample configuration for this L3VPN topology
by Ramanathan Selvamani 14 Apr '23

14 Apr '23

Hi Team, Can you share a sample config for l3vpn topology like the one shown in the diagram below? CE1 (VRF1) -> PE1 ß --- à PE2 --> CE2 (VRF1) | | CE3 (VRF2) --> | | ------> CE3 (VRF2) Thanks, Ramanathan

1 2