public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] bird: Update to version 2.0.8
Date: Mon, 02 Aug 2021 14:46:18 +0100	[thread overview]
Message-ID: <44098006-D49A-4476-AC23-5A2B676E8452@ipfire.org> (raw)
In-Reply-To: <20210731190443.2899151-1-adolf.belka@ipfire.org>

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

Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 31 Jul 2021, at 20:04, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> - Update from 2.0.7 to 2.0.8
> - Update of rootfile not required
> - Changelog
>   Version 2.0.8 (2021-03-18)
>     o Automatic channel reloads based on RPKI changes
>     o Multiple static routes with the same network
>     o Use bitmaps to keep track of exported routes
>     o Per-channel debug flags
>     o CLI commands show info from multiple protocols
>     o Linux: IPv4 routes with IPv6 nexthops
>     o Filter: Optimized redesign of prefix sets
>     o Filter: Improved type checking of user filters
>     o Filter: New src/dst accessors for Flowspec and SADR
>     o Filter: New 'weight' route attribute
>     o Filter: BGP path mask loop operator
>     o Filter: Remove quitbird command
>     o RIP: Demand circuit support (RFC 2091)
>     o BGP: New 'allow as sets' and 'enforce first as' options
>     o BGP: Support for BGP hostname capability
>     o BGP: Support for MD5SIG with dynamic BGP
>     o BFD: Optional separation of IPv4 / IPv6 BFD instances
>     o BFD: Per-peer session options
>     o RPKI: Allow build without libSSH
>     o RPKI: New 'ignore max length' option
>     o OSPF: Redesign of handling of unnumbered PtPs
>     o OSPF: Allow key id 0 in authentication
>     o Babel: Use onlink flag for routes with unreachable next hop
>     o Many bugfixes
>   Notes:
>     Automatic channel reloads based on RPKI changes are enabled by default,
>      but require import table enabled when used in BGP import filter.
>     BIRD now uses bitmaps to keep track of exported routes instead of
>      re-evaluation of export filters. That should improve speed and accuracy in
>      route export handling during reconfiguration, but takes some more memory.
>     Per-channel debug logging and some CLI commands (like 'show ospf neighbors')
>      defaulting to all protocol instances lead to some minor changes in log and
>      CLI output. Caution is recommended when logs or CLI output are monitored by
>      scripts.
> 
> 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 ee1829907..a57e745a5 100644
> --- a/lfs/bird
> +++ b/lfs/bird
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 2.0.7
> +VER        = 2.0.8
> 
> THISAPP    = bird-$(VER)
> DL_FILE    = $(THISAPP).tar.gz
> @@ -32,7 +32,7 @@ DL_FROM    = $(URL_IPFIRE)
> DIR_APP    = $(DIR_SRC)/$(THISAPP)
> TARGET     = $(DIR_INFO)/$(THISAPP)
> PROG       = bird
> -PAK_VER    = 7
> +PAK_VER    = 8
> 
> DEPS       =
> 
> @@ -46,7 +46,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_MD5 = dc884bbe5905578e452f28158700527c
> +$(DL_FILE)_MD5 = d807bdb34b27fe15ba8b71e83474eb27
> 
> install : $(TARGET)
> 
> -- 
> 2.32.0
> 

           reply	other threads:[~2021-08-02 13:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20210731190443.2899151-1-adolf.belka@ipfire.org>]

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=44098006-D49A-4476-AC23-5A2B676E8452@ipfire.org \
    --to=michael.tremer@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