mptcpd 0.11

- Support for the user space MPTCP path management generic netlink API
  in the Linux 5.19 kernel was implemented.

  - MPTCP address advertisements may now be managed through the
    mptcpd_pm_add_addr() and mptcpd_pm_remove_addr() functions.
    Listening sockets required for accepting subflow joins through
    advertised addresses will be handled automatically by mptcpd if
    not previously created through the mptcpd listener manager API
    described below.

  - The mptcpd_pm_add_addr() struct sockaddr parameter is now
    non-const to allow a zero valued TCP port to be updated with the
    ephemeral port chosen by the kernel and passed back to the user
    through that struct sockaddr parameter.

  - Subflows may be managed through mptcpd plugins through the
    mptcpd_pm_add_subflow(), mptcpd_pm_set_backup(), and
    mptcpd_pm_remove_subflow().

  - A new "mptcpd_lm" listener manager interface was added to the
    mptcpd library.  It allows plugins to explicitly manage listening
    sockets that are needed when advertising addresses, such as when
    creating listener pools.  The global mptcpd listener manager may
    be retrieved through the mptcpd_pm_get_lm() function.

- Propagate the "server side" flag to "new_connection" and
  "connection_established" plugin operations.

- Support a new "fullmesh" address flag in the mptcpd configuration
  file and command line "addr-flags" configuration option.  "fullmesh"
  is only relevant to the in-kernel path manager.  See the ip-mptcp(8)
  man page for details on the "fullmesh" address flag.

- Allow the mptcpd network monitor unit test to pass if it detects an
  active interface without any IPv4 or v6 addresses.  This can occur
  when an interface is attached to a bridge.  The bridge would have
  attached IP addresses but not the interface.

- Memory leaks that occured when parsing the "addr-flags" and
  "notify-flags" entries in the mptcpd configuration file were fixed.

- A use-after-free memory error was corrected in the mptcpd
  "load-plugins" configuration code.

- Improved the underlying mptcpd ID manager hash algorithm by replacing
  the existing trivial hash with the MurmurHash3 algorithm.

Author: Ossama Othman

NEWS

@@ -1,3 +1,52 @@
+19 August 2022 - mptcpd 0.11
+
+- Support for the user space MPTCP path management generic netlink API
+  in the Linux 5.19 kernel was implemented.
+
+  - MPTCP address advertisements may now be managed through the
+    mptcpd_pm_add_addr() and mptcpd_pm_remove_addr() functions.
+    Listening sockets required for accepting subflow joins through
+    advertised addresses will be handled automatically by mptcpd if
+    not previously created through the mptcpd listener manager API
+    described below.
+
+  - The mptcpd_pm_add_addr() struct sockaddr parameter is now
+    non-const to allow a zero valued TCP port to be updated with the
+    ephemeral port chosen by the kernel and passed back to the user
+    through that struct sockaddr parameter.
+
+  - Subflows may be managed through mptcpd plugins through the
+    mptcpd_pm_add_subflow(), mptcpd_pm_set_backup(), and
+    mptcpd_pm_remove_subflow().
+
+  - A new "mptcpd_lm" listener manager interface was added to the
+    mptcpd library.  It allows plugins to explicitly manage listening
+    sockets that are needed when advertising addresses, such as when
+    creating listener pools.  The global mptcpd listener manager may
+    be retrieved through the mptcpd_pm_get_lm() function.
+
+- Propagate the "server side" flag to "new_connection" and
+  "connection_established" plugin operations.
+
+- Support a new "fullmesh" address flag in the mptcpd configuration
+  file and command line "addr-flags" configuration option.  "fullmesh"
+  is only relevant to the in-kernel path manager.  See the ip-mptcp(8)
+  man page for details on the "fullmesh" address flag.
+
+- Allow the mptcpd network monitor unit test to pass if it detects an
+  active interface without any IPv4 or v6 addresses.  This can occur
+  when an interface is attached to a bridge.  The bridge would have
+  attached IP addresses but not the interface.
+
+- Memory leaks that occured when parsing the "addr-flags" and
+  "notify-flags" entries in the mptcpd configuration file were fixed.
+
+- A use-after-free memory error was corrected in the mptcpd
+  "load-plugins" configuration code.
+
+- Improved the underlying mptcpd ID manager hash algorithm by replacing
+  the existing trivial hash with the MurmurHash3 algorithm.
+
 24 June 2022 - mptcpd 0.10
 
 - Inconsistent byte order handling in mptcpd was corrected.  TCP ports

configure.ac

@@ -6,7 +6,7 @@
 
 AC_PREREQ([2.69])
 AC_INIT([mptcpd],
-        [0.10],
+        [0.11],
         [[email protected]],
         [],
         [https://github.com/intel/mptcpd])

man/mptcpd.8.in

@@ -1,11 +1,11 @@
 .\" SPDX-License-Identifier: BSD-3-Clause
 .\"
-.\" Copyright (c) 2017-2021, Intel Corporation
+.\" Copyright (c) 2017-2022, Intel Corporation
 
 .\" Process this file with
 .\" groff -man -Tascii mptcpd.8
 .\"
-.TH MPTCPD 8 "2021-09-17" "Multipath TCP Daemon" "System Management Commands"
+.TH MPTCPD 8 "2022-08-19" "Multipath TCP Daemon" "System Management Commands"
 .SH NAME
 mptcpd \- multipath TCP daemon
 .SH SYNOPSIS
@@ -71,8 +71,9 @@ set flags for announced address, where
 is a comma separated list containing one or more of the flags
 .IR subflow ,
 .IR signal ,
+.IR backup ,
 and
-.I backup
+.I fullmesh
 that plugins that deal with the in-kernel path manager may use when
 advertising addresses, e.g.
 .B --addr-flags=subflow