Skip to content

Commit

Permalink
setup: move 'endpoints' examples before 'limits'
Browse files Browse the repository at this point in the history
Because the examples are only about the endpoints, not the limits.

Signed-off-by: Matthieu Baerts (NGI0) <[email protected]>
  • Loading branch information
matttbe committed Jun 11, 2024
1 parent f3adc6b commit aa8e152
Showing 1 changed file with 13 additions and 13 deletions.
26 changes: 13 additions & 13 deletions setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -157,19 +157,6 @@ Optionally, the following flags can be set:

The IP address is an IPv4 or IPv6 address.

#### Limits

It is also important to make sure the limits are high enough:

```sh
ip mptcp limits set [ subflows NR ] [ add_addr_accepted NR ]
```

`subflows` is the limit of created and accepted subflows (paths), and
`add_addr_accepted` is the limit of accepted `ADD_ADDR` -- IP address
notification from the other peer -- that will result in the creation of
subflows.

#### Example

- Servers can announce extra IP addresses:
Expand All @@ -184,6 +171,19 @@ ip mptcp endpoint add 10.2.2.2 dev eth0 signal
ip mptcp endpoint add 100.64.1.134 dev usb0 subflow backup
```

#### Limits

It is also important to make sure the limits are high enough:

```sh
ip mptcp limits set [ subflows NR ] [ add_addr_accepted NR ]
```

`subflows` is the limit of created and accepted subflows (paths), and
`add_addr_accepted` is the limit of accepted `ADD_ADDR` -- IP address
notification from the other peer -- that will result in the creation of
subflows.

### Manual routing configuration

<details markdown="block">
Expand Down

0 comments on commit aa8e152

Please sign in to comment.