|
| 1 | +24 September 2021 - mptcpd 0.8 |
| 2 | + |
| 3 | +- The mptcpd library API now splits path management operations |
| 4 | + specific to the in-kernel path manager found in the upstream Linux |
| 5 | + kernel into a separate "mptcpd_kpm" API namespace to differentiate |
| 6 | + ADD_ADDR and REMOVE_ADDR related operations between the in-kernel |
| 7 | + and user space cases. The operations for the two are different and |
| 8 | + have different use cases. |
| 9 | + |
| 10 | +- Two new mptcpd command line arguments were added: "--addr-flags" and |
| 11 | + "--notify-flags", along with the equivalent settings in the mptcpd |
| 12 | + system configuration file (e.g., /etc/mptcpd/mptcpd.conf). |
| 13 | + "addr-flags" are used when announcing an IP address. Similar flags |
| 14 | + are used by the "ip mptcp" sub-command. See the ip-mptcp(8) and man |
| 15 | + page for further details on these address related flags. |
| 16 | + "notify-flags" provides for further control over how plugins are |
| 17 | + notified of changes to local IP addresses. See the mptcpd(8) man |
| 18 | + page shipped with this mptcpd release for further details. |
| 19 | + |
| 20 | +- Improve the mptcpd "addr_adv" plugin by making it set suitable MPTCP |
| 21 | + resource limits in the kernel, such as expanding the maximum number |
| 22 | + of subflows to allow subflows associated with advertised IP |
| 23 | + addresses to be created. |
| 24 | + |
| 25 | +- The mptcpd plugin directory name in the mptcpd system configuration |
| 26 | + file may now be left empty to improve "multilib" support found in |
| 27 | + some Linux distributions. A compile-time default will be used if no |
| 28 | + plugin directory name is found in the mptcpd system configuration |
| 29 | + file or the mptcpd command line options. |
| 30 | + |
| 31 | +- Mptcpd command line options now properly take precedence over the |
| 32 | + corresponding mptcpd system configuration setting. This addresses |
| 33 | + an issue that prevented mptcpd from starting if a required setting |
| 34 | + was not specified in the mptcpd system configuration file even |
| 35 | + though the same setting was configured through the mptcpd command |
| 36 | + line. |
| 37 | + |
| 38 | +- A new "mptcpize" program was added that allows legacy TCP-only |
| 39 | + applications to transparently use MPTCP by either of the following |
| 40 | + approaches: |
| 41 | + - leverage library interpositioning to transparently replace TCP |
| 42 | + socket calls with their MPTCP counterparts. |
| 43 | + - enable or disable TCP to MPTCP socket conversion through an |
| 44 | + existing systemd unit file. |
| 45 | + |
| 46 | +- Build regressions against ELL versions 0.31 and 0.33 were |
| 47 | + corrected. |
| 48 | + |
1 | 49 | 13 April 2021 - mptcpd 0.7
|
2 | 50 |
|
3 | 51 | - MPTCP path management generic netlink events recently added to the
|
4 |
| - upstream Linux kernel are now supported, and propagated to mptcpd |
5 |
| - plugins. The same API is also found in the multipath-tcp.org |
| 52 | + upstream Linux kernel (v5.12) are now supported, and propagated to |
| 53 | + mptcpd plugins. The same API is also found in the multipath-tcp.org |
6 | 54 | kernel. Differences between the two kernels are transparent to
|
7 | 55 | mptcpd plugins.
|
8 | 56 |
|
|
0 commit comments