{"id":3591,"date":"2022-12-20T17:09:06","date_gmt":"2022-12-20T20:09:06","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/ipmptcp-man8\/"},"modified":"2022-12-20T17:09:06","modified_gmt":"2022-12-20T20:09:06","slug":"ipmptcp-man8","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/ipmptcp-man8\/","title":{"rendered":"IP−MPTCP (man8)"},"content":{"rendered":"

IP\u2212MPTCP<\/h1>\n

NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
AUTHOR<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

ip-mptcp \u2212 MPTCP path manager configuration<\/p>\n

SYNOPSIS <\/a> <\/h2>\n

ip<\/b> [ OPTIONS<\/i> ] mptcp<\/b> { endpoint<\/b> | limits<\/b> | help<\/b> }<\/p>\n

ip mptcp endpoint add<\/b> IFADDR<\/i> [ port<\/b> PORT<\/i> ] [ dev<\/b> IFNAME<\/i> ] [ id<\/b> ID<\/i> ] [ FLAG-LIST<\/i> ]<\/p>\n

ip mptcp endpoint del id<\/b> ID<\/i><\/p>\n

ip mptcp endpoint show<\/b> [ id<\/b> ID<\/i> ]<\/p>\n

ip mptcp endpoint flush<\/b><\/p>\n

FLAG-LIST<\/i> := [ FLAG-LIST<\/i> ] FLAG<\/i><\/p>\n

FLAG<\/i> := [ signal<\/b> | subflow<\/b> | backup<\/b> ]<\/p>\n

ip mptcp limits set<\/b> [ subflow<\/b> SUBFLOW_NR<\/i> ] [ add_addr_accepted<\/b> ADD_ADDR_ACCEPTED_NR<\/i> ]<\/p>\n

ip mptcp limits show<\/b><\/p>\n

ip mptcp monitor<\/b><\/p>\n

DESCRIPTION <\/a> <\/h2>\n

MPTCP is a transport protocol built on top of TCP that allows TCP connections to use multiple paths to maximize resource usage and increase redundancy. The ip-mptcp sub-commands allow configuring several aspects of the MPTCP path manager, which is in charge of subflows creation:<\/p>\n

The endpoint<\/b> object specifies the IP addresses that will be used and\/or announced for additional subflows:<\/p>\n\n\n\n\n\n
<\/td>\n<\/td>\n <\/td>\n<\/tr>\n
<\/td>\n<\/td>\n <\/td>\n<\/tr>\n
<\/td>\n<\/td>\n <\/td>\n<\/tr>\n
<\/td>\n<\/td>\n <\/td>\n<\/tr>\n<\/table>\n

\"Image<\/p>\n\n\n
<\/td>\n\n

PORT<\/i><\/p>\n<\/td>\n

<\/td>\n\n

When a port number is specified, incoming MPTCP subflows for already established MPTCP sockets will be accepted on the specified port, regardless the original listener port accepting the first MPTCP subflow and\/or this peer being actually on the client side.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

ID<\/i> is a unique numeric identifier for the given endpoint<\/p>\n\n\n
<\/td>\n\n

signal<\/b><\/p>\n<\/td>\n

<\/td>\n\n

the endpoint will be announced\/signalled to each peer via an ADD_ADDR MPTCP sub-option<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

subflow<\/b><\/p>\n

if additional subflow creation is allowed by MPTCP limits, the endpoint will be used as the source address to create an additional subflow after that the MPTCP connection is established.<\/p>\n\n\n
<\/td>\n\n

backup<\/b><\/p>\n<\/td>\n

<\/td>\n\n

the endpoint will be announced as a backup address, if this is a signal<\/b> endpoint, or the subflow will be created as a backup one if this is a subflow<\/b> endpoint<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

The limits<\/b> object specifies the constraints for subflow creations:<\/p>\n

\"Image<\/p>\n

SUBFLOW_NR<\/i><\/p>\n

specifies the maximum number of additional subflows allowed for each MPTCP connection. Additional subflows can be created due to: incoming accepted ADD_ADDR option, local subflow<\/b> endpoints, additional subflows started by the peer.<\/p>\n

ADD_ADDR_ACCEPTED_NR<\/i><\/p>\n

specifies the maximum number of ADD_ADDR suboptions accepted for each MPTCP connection. The MPTCP path manager will try to create a new subflow for each accepted ADD_ADDR option, respecting the SUBFLOW_NR<\/i> limit.<\/p>\n

monitor<\/b> displays creation and deletion of MPTCP connections as well as addition or removal of remote addresses and subflows.<\/p>\n

AUTHOR <\/a> <\/h2>\n

Original Manpage by Paolo Abeni <\/p>\n

\n","protected":false},"excerpt":{"rendered":"

ip-mptcp \u2212 MPTCP path manager configuration <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,707,4],"class_list":["post-3591","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-ip-mptcp","tag-man8"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3591","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3591"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3591\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3591"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3591"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3591"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}