From: "Othman, Ossama" <ossama.othman@intel.com>
To: "mptcp@lists.linux.dev" <mptcp@lists.linux.dev>
Subject: mptcpd 0.8 released
Date: Fri, 24 Sep 2021 16:38:49 +0000 [thread overview]
Message-ID: <SJ0PR11MB5182C3E255457FF9F472E80CF2A49@SJ0PR11MB5182.namprd11.prod.outlook.com> (raw)
Version 0.8 of the Multipath TCP Daemon - mptcpd - is now available on
GitHub at:
https://github.com/intel/mptcpd/releases/tag/v0.8
Many thanks to Paolo Abeni, Davide Caratti, and Daniel Danzberger for
their contributions.
Release notes:
- The mptcpd library API now splits path management operations
specific to the in-kernel path manager found in the upstream Linux
kernel into a separate "mptcpd_kpm" API namespace to differentiate
ADD_ADDR and REMOVE_ADDR related operations between the in-kernel
and user space cases. The operations for the two are different and
have different use cases.
- Two new mptcpd command line arguments were added: "--addr-flags" and
"--notify-flags", along with the equivalent settings in the mptcpd
system configuration file (e.g., /etc/mptcpd/mptcpd.conf).
"addr-flags" are used when announcing an IP address. Similar flags
are used by the "ip mptcp" sub-command. See the ip-mptcp(8) and man
page for further details on these address related flags.
"notify-flags" provides for further control over how plugins are
notified of changes to local IP addresses. See the mptcpd(8) man
page shipped with this mptcpd release for further details.
- Improve the mptcpd "addr_adv" plugin by making it set suitable MPTCP
resource limits in the kernel, such as expanding the maximum number
of subflows to allow subflows associated with advertised IP
addresses to be created.
- The mptcpd plugin directory name in the mptcpd system configuration
file may now be left empty to improve "multilib" support found in
some Linux distributions. A compile-time default will be used if no
plugin directory name is found in the mptcpd system configuration
file or the mptcpd command line options.
- Mptcpd command line options now properly take precedence over the
corresponding mptcpd system configuration setting. This addresses
an issue that prevented mptcpd from starting if a required setting
was not specified in the mptcpd system configuration file even
though the same setting was configured through the mptcpd command
line.
- A new "mptcpize" program was added that allows legacy TCP-only
applications to transparently use MPTCP by either of the following
approaches:
- leverage library inter-positioning to transparently replace TCP
socket calls with their MPTCP counterparts.
- enable or disable TCP to MPTCP socket conversion through an
existing systemd unit file.
- Build regressions against ELL versions 0.31 and 0.33 were
corrected.
reply other threads:[~2021-09-24 16:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=SJ0PR11MB5182C3E255457FF9F472E80CF2A49@SJ0PR11MB5182.namprd11.prod.outlook.com \
--to=ossama.othman@intel.com \
--cc=mptcp@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.