128technology · Chr1st0ph3rTurn3r · Jul 22, 2024 · Jul 22, 2024 · Jul 23, 2024 · Jul 25, 2024
@@ -26,7 +26,7 @@ Version `6.1.0` introduces changes to the SSR software release model. Every six
 | --| -- | -- | -- | -- | -- |
 | Release 6.2 | [6.2.0](release_notes_128t_6.2.md#release-620-39) | November 16, 2023 | [6.2.5](release_notes_128t_6.2.md#release-625-5r2) | November 16, 2025 | May 16, 2026 |
 | Release 6.1 | [6.1.0](release_notes_128t_6.1.md#release-610-55) | April 14, 2023 | [6.1.9](release_notes_128t_6.1.md#release-619-2) | September 22, 2025 | June 22, 2026 |
-| Release 5.6 | [5.6.7](release_notes_128t_5.6.md#release-567-4) | March 16, 2023 | [5.6.15](release_notes_128t_5.6.md#release-5615-1) | June 16, 2024 | December 16, 2024 |
+| Release 5.6 | [5.6.7](release_notes_128t_5.6.md#release-567-4) | March 16, 2023 | [5.6.15](release_notes_128t_5.6.md#release-5616-3) | June 16, 2024 | December 16, 2024 |
 
 ## Out of Support
 

@@ -16638,6 +16638,82 @@ configure authority router routing pim rp group-range [<multicast-ipv4-prefix>]
 | ---- | ----------- |
 | multicast-ipv4-prefix | The value to set for this field |
 
+## `configure authority router routing rib-policy`
+
+List of protocol specific RIB policies
+
+#### Usage
+
+```
+configure authority router routing rib-policy <family> <protocol>
+```
+
+##### Positional Arguments
+
+| name | description |
+| ---- | ----------- |
+| family | The routing protocol address family |
+| protocol | The routing protocol RIB policy |
+
+##### Subcommands
+
+| command | description |
+| ------- | ----------- |
+| `delete` | Delete configuration data |
+| [`family`](#configure-authority-router-routing-rib-policy-family) | The routing protocol address family |
+| `override-generated` | Force auto-generated configuration and any modifications to it to persist on commit |
+| [`policy`](#configure-authority-router-routing-rib-policy-policy) | A policy to apply to the protocol route |
+| [`protocol`](#configure-authority-router-routing-rib-policy-protocol) | The routing protocol RIB policy |
+| `show` | Show configuration data for &#x27;rib-policy&#x27; |
+
+## `configure authority router routing rib-policy family`
+
+The routing protocol address family
+
+#### Usage
+
+```
+configure authority router routing rib-policy family [<rib-family>]
+```
+
+##### Positional Arguments
+
+| name | description |
+| ---- | ----------- |
+| rib-family | The value to set for this field |
+
+## `configure authority router routing rib-policy policy`
+
+A policy to apply to the protocol route
+
+#### Usage
+
+```
+configure authority router routing rib-policy policy [<policy-ref>]
+```
+
+##### Positional Arguments
+
+| name | description |
+| ---- | ----------- |
+| policy-ref | The value to set for this field |
+
+## `configure authority router routing rib-policy protocol`
+
+The routing protocol RIB policy
+
+#### Usage
+
+```
+configure authority router routing rib-policy protocol [<rib-protocol>]
+```
+
+##### Positional Arguments
+
+| name | description |
+| ---- | ----------- |
+| rib-protocol | The value to set for this field |
+
 ## `configure authority router routing routing-protocol`
 
 Each entry contains configuration of a routing protocol instance.
@@ -20423,6 +20499,83 @@ configure authority router routing vrf pim rp group-range [<multicast-ipv4-prefi
 | ---- | ----------- |
 | multicast-ipv4-prefix | The value to set for this field |
 
+
+## `configure authority router routing vrf rib-policy`
+
+List of protocol specific RIB policies
+
+#### Usage
+
+```
+configure authority router routing vrf rib-policy <family> <protocol>
+```
+
+##### Positional Arguments
+
+| name | description |
+| ---- | ----------- |
+| family | The routing protocol address family |
+| protocol | The routing protocol RIB policy |
+
+##### Subcommands
+
+| command | description |
+| ------- | ----------- |
+| `delete` | Delete configuration data |
+| [`family`](#configure-authority-router-routing-vrf-rib-policy-family) | The routing protocol address family |
+| `override-generated` | Force auto-generated configuration and any modifications to it to persist on commit |
+| [`policy`](#configure-authority-router-routing-vrf-rib-policy-policy) | A policy to apply to the protocol route |
+| [`protocol`](#configure-authority-router-routing-vrf-rib-policy-protocol) | The routing protocol RIB policy |
+| `show` | Show configuration data for &#x27;rib-policy&#x27; |
+
+## `configure authority router routing vrf rib-policy family`
+
+The routing protocol address family
+
+#### Usage
+
+```
+configure authority router routing vrf rib-policy family [<rib-family>]
+```
+
+##### Positional Arguments
+
+| name | description |
+| ---- | ----------- |
+| rib-family | The value to set for this field |
+
+## `configure authority router routing vrf rib-policy policy`
+
+A policy to apply to the protocol route
+
+#### Usage
+
+```
+configure authority router routing vrf rib-policy policy [<policy-ref>]
+```
+
+##### Positional Arguments
+
+| name | description |
+| ---- | ----------- |
+| policy-ref | The value to set for this field |
+
+## `configure authority router routing vrf rib-policy protocol`
+
+The routing protocol RIB policy
+
+#### Usage
+
+```
+configure authority router routing vrf rib-policy protocol [<rib-protocol>]
+```
+
+##### Positional Arguments
+
+| name | description |
+| ---- | ----------- |
+| rib-protocol | The value to set for this field |
+
 ## `configure authority router routing vrf routing-protocol`
 
 Each entry contains configuration of a routing protocol instance.

@@ -24,6 +24,59 @@ Before upgrading please review the [**Upgrade Considerations**](intro_upgrade_co
 ------
 - **Plugin Upgrades:** If you are running with plugins, updates are required for some plugins **before** upgrading the conductor to SSR version 5.4.0 or higher. Please review the [Plugin Configuration Generation Changes](intro_upgrade_considerations.md#plugin-configuration-generation-changes) for additional information.  
 
+## Release 5.6.16-3
+
+**Release Date:** July 26, 2024
+
+### Resolved Issues
+
+- **The following CVE's have been identified and addressed in this release:** 
+CVE-2024-21011, CVE-2024-21012, CVE-2024-21068, CVE-2024-21085, CVE-2024-21094, CVE-2019-13631, CVE-2019-15505, CVE-2019-25162, CVE-2020-25656, CVE-2020-36777, CVE-2021-3753, CVE-2021-4204, CVE-2021-46934, CVE-2021-47013, CVE-2021-47055, CVE-2021-47118, CVE-2021-47153, CVE-2021-47171, CVE-2021-47185, CVE-2022-0500, CVE-2022-23222, CVE-2022-3565, CVE-2022-45934, CVE-2022-48627, CVE-2022-48669, CVE-2023-1513, CVE-2023-24023, CVE-2023-25775, CVE-2023-28464, CVE-2023-31083, CVE-2023-3567, CVE-2023-37453, CVE-2023-38409, CVE-2023-39189, CVE-2023-39192, CVE-2023-39193, CVE-2023-39194, CVE-2023-39198, CVE-2023-4133, CVE-2023-4244, CVE-2023-42754, CVE-2023-42755, CVE-2023-45863, CVE-2023-51779, CVE-2023-51780, CVE-2023-52340, CVE-2023-52434, CVE-2023-52439, CVE-2023-52445, CVE-2023-52448, CVE-2023-52477, CVE-2023-52489, CVE-2023-52513, CVE-2023-52520, CVE-2023-52528, CVE-2023-52565, CVE-2023-52574, CVE-2023-52578, CVE-2023-52580, CVE-2023-52581, CVE-2023-52594, CVE-2023-52595, CVE-2023-52598, CVE-2023-52606, CVE-2023-52607, CVE-2023-52610, CVE-2023-52620, CVE-2023-6121, CVE-2023-6176, CVE-2023-6240, CVE-2023-6622, CVE-2023-6915, CVE-2023-6932, CVE-2024-0340, CVE-2024-0841, CVE-2024-23307, CVE-2024-25742, CVE-2024-25743, CVE-2024-25744, CVE-2024-26593, CVE-2024-26602, CVE-2024-26603, CVE-2024-26609, CVE-2024-26610, CVE-2024-26615, CVE-2024-26642, CVE-2024-26643, CVE-2024-26659, CVE-2024-26664, CVE-2024-26671, CVE-2024-26693, CVE-2024-26694, CVE-2024-26743, CVE-2024-26744, CVE-2024-26779, CVE-2024-26872, CVE-2024-26892, CVE-2024-26897, CVE-2024-26901, CVE-2024-26919, CVE-2024-26933, CVE-2024-26934, CVE-2024-26964, CVE-2024-26973, CVE-2024-26993, CVE-2024-27014, CVE-2024-27048, CVE-2024-27052, CVE-2024-27056, CVE-2024-27059, CVE-2024-2961, CVE-2024-33599, CVE-2024-33600, CVE-2024-33601, CVE-2024-33602, CVE-2024-32487, CVE-2023-4408, CVE-2023-50387, CVE-2023-50868, CVE-2023-4408, CVE-2023-50387, CVE-2023-50868
+------
+- **I95-47195, I95-47196, I95-49015, I95-49599, I95-56682 Forwarding plane crash, causing stranded network namespaces when LTE/PPPoE network-interface name is changed:** Implemented reinit script to reiniatilize namespace, KNI and target-interface after a configuration change in the network-interface.
+------
+- **I95-49018 Peers are not coming up for PPPoE interface on a standalone setup:** Reintroduced network `reinit` script to reinitialize namespace, KNI, and target-interface after a config change in the `network-interface`, or under abnormal conditions such as the `target-interface` being moved out from the namespace.
+------
+- **I95-49218 Filter OSPF routes using RIB Policy routes:** Use the `configure authority router routing rib-policy` command from either the routing default-instance (`configure authority router routing`) or inside `configure authority router routing vrf` to provide addtional filtering for OSPF routes. For more information see [`configure authority router routing rib-policy`](config_command_guide.md#configure-authority-router-routing-rib-policy) and [`configure authority router routing vrf rib-policy`](config_command_guide.md#configure-authority-router-routing-vrf-rib-policy).
+------
+- **I95-56203 The First Article Inspection (FAI) scan archive is empty:** Resolved an issue with `logrotate` clearing all the FAI scan archives. This was due to each archive having a unique name using a timestamp. A different service is now used to rotate the FAI scan files.
+------
+- **I95-56236 Routers unable to onboard after upgrading the Conductor:** Resolved an issue where the automated provisioner and the Quickstart processes overlapped, preventing the device state from being reviewed for errors, which stopped the onboarding process. 
+------
+- **I95-56326 / I95-57000 Potential crash while collecting TSI:** Added protection against unmapped memory access to resolve an issue where, if a TSI is collected at just the wrong time, it can cause a highway crash.
+------
+- **I95-56455 Zero-byte files when updating conductor hardware using an OTP image:** A check has been added to verify that `api.key` and `router-api.key` are non-zero length and valid. If not, the keys are regenerated.
+------
+- **I95-56527 Failure to validate and commit config; system incorrectly expected escape sequence:** Resolved an issue where capture-filter expected an escape sequence for input when it was not necessary. 
+------
+- **I95-56575 Reduce polling rate of disk monitoring and add optimization:** The disk monitoring agent polling frequently is inefficient. Reduced the frequency that disk usage is checked, and streamlined the process.
+------
+- **I95-56612 `fib-service-match any-match` missing some FIB entries:** Resolved an issue when a service-address was more specific than the last route update, a search for other less specific services was not performed. Now when the service address update is more specific, additional searches will continue. 
+------
+- **I95-56715 Address validation in migrate feature in conductor UI is not working correctly:** Resolved an isssue between the client and the server during the use of the GUI `migrate` operation, where the conductor address was not read correctly, and returning an irrelevant error message. 
+------
+- **I95-56726 `No Timeout Queue` message logged in cases where a config commit fails, or a conductor fails to load a config on startup:** Resolved an issue with `ThreadPoolWithExternalPoller` that resulted in a stack trace in the logs which starts with message `No TimeoutQueue:`.
+------
+- **I95-56727 Domain names that begin with numbers are not allowed to be configured:** Warnings are no longer generated for domain-name elements of service configurations which have labels beginning with a number, for example `123.abc.com`.
+------
+- **I95-56822 Router stuck in a continuous upgrade/failure state:** DNS name servers changes on the conductor are not honored. In cases where the DNS configuration changed post boot, the conductor software proxy would not reload the config. In this scenario the proxied router software requests would use an out of date DNS configuration for the proxied requests, resulting in failure. 
+------
+- **I95-56843 Error logs filled with irrelevant KNI network script info:** The log output has been reduced to provide related information.
+------
+- **I95-56847 lte / pppoe default-route check incorrectly reporting warnings:** Resolved an issue where warnings were incorrectly shown on the conductor for interfaces without `default-route` or `management-vector` configured.
+------
+- **I95-56850 Overlap warning on router not present on conductor:** Resolved a case where a service on a router is configured with `applies-to`, and the same service is configured on the conductor (overlap) but does not have `applies-to` configured, the validation process will generate a warning on the router but not the conductor. 
+------
+- **I95-57017 Application ID failed to block some domains:** Resolved an issue where DPI failed to identify the domain-name from SNI if the `client-hello` is split up into multiple TCP packet segments.
+------
+- **I95-57082 Unable to delete a capture-filter that contains a forward slash (/):** This issue has been resolved. 
+------
+- **I95-57110 Crash seen during add and delete peers while sending traffic:** A race condition has been fixed that could cause a crash in the packet-processing highway process if a peer-path is removed from configuration.
+------
+- **I95-57114 Unable to upgrade AWS Conductor:** Resolved an issue where an incorrect package version was installed, triggering a downgrade and preventing the upgrade.
+------
+- **I95-57205 Race condition on startup with DHCP configured on LTE or PPPoE interface, causing system to crash:** This issue has been resolved.
+
 ## Release 5.6.15-1
 
 **Release Date:** June 27, 2024

@@ -5,6 +5,11 @@ import React from "react";
 // New entries should be placed at the top.
 // ----------------------------------------------------------------------------
 export const releases = [
+  {
+    version: '5.6.16',
+    url:'release_notes_128t_5.6#release-5616-3',
+    releaseDate: 'July 26, 2024',
+  },
   {
     version: '5.6.15',
     url:'release_notes_128t_5.6#release-5615-1',