public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] bird: Update to version 2.0.9
Date: Thu, 14 Apr 2022 10:20:57 +0200	[thread overview]
Message-ID: <20220414082057.4095999-1-adolf.belka@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2831 bytes --]

- Update from version 2.0.8 to 2.0.9
- Update of rootfile not required
- Changelog
	Version 2.0.9 (2022-02-09)
	  o BGP: Flowspec validation procedure
	  o Babel: MAC authentication support
	  o Routing table configuration blocks
	  o Optional prefix trie in routing table for faster LPM/interval queries
	  o CLI: New 'show route in <prefix>' command
	  o Filter: Faster (16-way) prefix sets
	  o Filter: MPLS label route attribute
	  o Filter: Operators to pick community components
	  o Filter: Operators to find minimum and maximum element of lists
	  o BGP: New 'free bind' option
	  o BGP: Log route updates that were changed to withdraws
	  o BGP: Improved 'invalid next hop' error reporting
	  o OSPF: Allow ifaces with host address as unnumbered PtP or PtMP ifaces
	  o OSPF: All packets on PtP networks should be sent to AllSPFRouters address
	  o Scripts for apkg-powered upstream packaging for deb and rpm
	  o Support for Blake2s and Blake2b hash functions
	  o Security keys / passwords can be entered in hexadecimal digits
	  o Memory statistics split into Effective and Overhead
	  o Linux: New option 'netlink rx buffer' to specify netlink socket buffer size
	  o BSD: Assume onlink flag on ifaces with only host addresses
	  o Many bugfixes
	  Notes:
	  - For OSPF on PtP network, BIRD now sends all packets to multicast AllSPFRouters
	    address (as required in RFC 2328 8.1). This likely breaks setups with multiple
	    neighbors on a network configured as PtP, which worked in previous versions.
	    Such links should be configured as PtMP.
	  - Since Linux 5.3, netlink socket can be flooded by route cache entries during
	    route table scan. This version mitigates that issue by using strict netlink
	    filtering.

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 lfs/bird | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lfs/bird b/lfs/bird
index c140aa811..591ccc6a7 100644
--- a/lfs/bird
+++ b/lfs/bird
@@ -26,7 +26,7 @@ include Config
 
 SUMMARY    = The BIRD Internet Routing Daemon
 
-VER        = 2.0.8
+VER        = 2.0.9
 
 THISAPP    = bird-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -34,7 +34,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = bird
-PAK_VER    = 8
+PAK_VER    = 9
 
 DEPS       =
 
@@ -50,7 +50,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 4b36688ac85967ad8c39d9c37dc717d77b1cb5c3ec44a0cf4e84ff38b8d1710d10653a1333b50cd2ede79fd7f012ec86de0baefc9ac18435693ec5b3e43b8a3a
+$(DL_FILE)_BLAKE2 = 5226058ba8989a28e8151906e194fd3065276034f1304e0e45772b17f3d8095eff6add211320a23418bfb57b2c16c96594fb85345355e3b870d7bfa2cfe119b9
 
 install : $(TARGET)
 
-- 
2.35.1


             reply	other threads:[~2022-04-14  8:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14  8:20 Adolf Belka [this message]
2022-04-18 20:59 ` Peter Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220414082057.4095999-1-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox