11.9. Release 6.5

New Features

  • Added log profiles that contain logging settings — servers, format, protocol, and event types; one or more log profiles can be assigned to a pool

Fixed

  • Fixed deadlocks in various subsystems

  • Fixed sending unnecessary excess NAT logs

  • Fixed excessive usage of mbuf packets

  • Fixed an issue where adding an interface to the bond while reading startup-config caused the interface to change its ADMIN status

Changes

  • Added the TX Discards counter to the show overruns command. This counter indicates that the system cannot buffer new packets if the TX queue and the local work buffer for the port are full. Such packets will be dropped and counted in TX Discards

  • Added ability to configure number of tbl8s:

    • route_table_num_tbl8s — the number of tbl8s for IPv4 route tables (LPM)

    • route_table6_num_tbl8s - the number of tbl8s for IPv6 route tables (LPM)

  • Added an error message when system cannot add a route to the FIB

  • Added RECMP reinitialization when disabling a nexthop

  • Increased node name size to 256

  • Added a missing memory allocation error check

  • Added management for the pool stats-thread

Hotfixes

Release 6.5.2

  • Fixed CLI commands showing empty output instead of error messages when interface lookup or other operations failed. Proper error messages are now displayed

  • Fixed the memory leak in the show ip neighbor interface IFNAME command when the specified interface was not found

  • Fixed the memory leak that could occur when route lookup failed during neighbor discovery

  • Neighbor Advertisement without the Target Link-Layer Address option and Override=0 now correctly transitions the entry state to REACHABLE when Solicited=1 (RFC 4861 Section 7.2.5, Case II)

  • Fixed IPv6 neighbor entries getting stuck in the PROBE state indefinitely due to unicast Neighbor Solicitation packets being sent with an incorrect destination address

  • Fixed an issue where nb_paired counters could be incorrectly updated when an external IP address was removed from a pool while active subscribers were still using it. This could lead to incorrect state tracking when subscribers were automatically moved to another IP address

Release 6.5.1

  • Fixed IPv6 routing with NAT64 enabled

  • Fixed removal of a NAT log profile

  • Fixed creation of an empty $huge_vm_mem file

  • Fixed detection of host memory configuration changes