summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorOndrej Zajicek <santiago@crfreenet.org>2022-12-11 17:28:14 +0100
committerOndrej Zajicek <santiago@crfreenet.org>2022-12-11 17:28:14 +0100
commit1e47b9f203aaaad0fb658d40a1670f1d0437f1f8 (patch)
tree07029e31753205668fa65d6d115950df00c6db7c /NEWS
parent34ebc4e1ba41c618e5d46112696011ed596c5ebc (diff)
NEWS and version updatev2.0.11
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS37
1 files changed, 37 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index e61a0b74..1fd83c86 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,40 @@
+Version 2.0.11 (2022-11-12)
+ o BGP roles (RFC 9234)
+ o BGP: Keepalive time scaling
+ o BGP: New 'min hold time' and 'min keepalive time' options
+ o BGP: New 'next hop prefer global' option
+ o Filter: For loops and direct recursion
+ o Filter: Mixed declarations of local variables
+ o Filter: Improved static type checks
+ o Filter: Literal [] for empty set
+ o Linux: Netlink KRT improvements
+ o BSD: Experimental support for Netlink API
+ o Memory management improvements
+ o Many bugfixes
+
+ Notes:
+
+ In contrast to prior versions, configured keepalive time in BGP now scales
+ with negotiated hold time to maintain proportion between the keepalive time
+ and the hold time.
+
+ The Linux KRT was updated to use the recent API for IPv6 ECMP routes instead
+ of the legacy one. Consequently, the Linux versions older than 4.11 are no
+ longer supported, at least for IPv6 ECMP routes. Also, routing table scanning
+ now runs separately for each table to avoid congestion.
+
+ There is a minor change in recursive next hop processing. Previously,
+ recursive next hop must be resolved through a non-recursive route, now it must
+ be resolved through a prefix where both the best route and all routes with the
+ same preference (as the best route) are non-recursive. The old behavior might
+ lead in some corner cases to an infinite loop of recursive next hop resolution
+ due to a priority inversion.
+
+ There is a minor change in the 'configure undo' command, it is no longer
+ available after failed reconfiguration, as the old configuration is already
+ released.
+
+
Version 2.0.10 (2022-06-16)
o BGP performance improvements
o BFD: New 'strict bind' option