# IP-MPTCP(8) - man - phpman

[IP-MPTCP(8)](https://www.chedong.com/phpMan.php/man/IP-MPTCP/8/markdown)                                     Linux                                    [IP-MPTCP(8)](https://www.chedong.com/phpMan.php/man/IP-MPTCP/8/markdown)



## NAME
       ip-mptcp - MPTCP path manager configuration

## SYNOPSIS
       **ip** [ _OPTIONS_ ] **mptcp** { **endpoint**  | **limits**  | **help**  }


       **ip** **mptcp** **endpoint** **add** _IFADDR_ [ **port** _PORT_ ] [ **dev** _IFNAME_ ] [ **id** _ID_ ] [ _FLAG-LIST_ ]

       **ip** **mptcp** **endpoint** **del** **id** _ID_

       **ip** **mptcp** **endpoint** **show** [ **id** _ID_ ]

### ip mptcp endpoint flush

       _FLAG-LIST_ := [ _FLAG-LIST_ ] _FLAG_

       _FLAG_ := [ **signal** | **subflow** | **backup** ]

       **ip** **mptcp** **limits** **set** [ **subflow** _SUBFLOW_NR_ ] [ **add**___**addr**___**accepted** _ADD_ADDR_ACCEPTED_NR_ ]

### ip mptcp limits show

### ip mptcp monitor


## DESCRIPTION
       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 cre‐
       ation:


       The **endpoint** object specifies the IP addresses that will be used and/or announced for addi‐
       tional subflows:


       ip mptcp endpoint add      add new MPTCP endpoint
       ip mptcp endpoint delete   delete existing MPTCP endpoint
       ip mptcp endpoint show     get existing MPTCP endpoint
       ip mptcp endpoint flush    flush all existing MPTCP endpoints


       _PORT_   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.

              _ID_ is a unique numeric identifier for the given endpoint


       **signal** the endpoint will be announced/signalled to each peer via an ADD_ADDR MPTCP sub-option


### subflow
              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.


       **backup** the endpoint will be announced as a backup address, if this is a **signal** endpoint, or
              the subflow will be created as a backup one if this is a **subflow** endpoint



       The **limits** object specifies the constraints for subflow creations:


       ip mptcp limits show   get current MPTCP subflow creation limits
       ip mptcp limits set    change the MPTCP subflow creation limits


       _SUBFLOW_NR_
              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** endpoints, additional subflows started by the peer.


       _ADD_ADDR_ACCEPTED_NR_
              specifies the maximum number of ADD_ADDR suboptions accepted for each MPTCP connec‐
              tion. The MPTCP path manager will try to create a new subflow for each accepted
              ADD_ADDR option, respecting the _SUBFLOW_NR_ limit.



       **monitor** displays creation and deletion of MPTCP connections as well as addition or removal of
       remote addresses and subflows.


## AUTHOR
       Original Manpage by Paolo Abeni <<pabeni@redhat.com>>



iproute2                                     4 Apr 2020                                  [IP-MPTCP(8)](https://www.chedong.com/phpMan.php/man/IP-MPTCP/8/markdown)