In order to prevent excessive resource consumption by a libp2p node it's important to understand limits are applied and how to tune them to the needs of your application.
This is important for DoS attack mitgation - there is a more holistic discussion and general advice on that topic at the main libp2p docs website.
- Connection limits
- Closing connections
- Inbound connection threshold
- Stream limits
- Transport specific limits
- Allow/deny lists
- How much memory will be used for buffering?
It's possible to limit the total amount of connections a node is able to make (combining incoming and outgoing). When this limit is reached and an attempt to open a new connection is made, existing connections may be closed to make room for the new connection (see Closing connections).
- Note: there currently isn't a way to specify different limits for incoming vs. outgoing. Connection limits are applied across both incoming and outgoing connections combined. There is a backlog item for this here.
We can also limit the number of connections in a 'pending' state. These connections have been opened by a remote peer but peer IDs have yet to be exchanged and/or connection encryption and multiplexing negotiated. Once this limit is hit further connections will be closed unless the remote peer has an address in the allow list.
All fields are optional. The default values are defined in src/connection-manager/index.ts - please see that file for the current values.
import { createLibp2p } from 'libp2p'
const node = await createLibp2p({
connectionManager: {
/**
* The total number of connections allowed to be open at one time
*/
maxConnections: 100,
/**
* How many connections can be open but not yet upgraded
*/
maxIncomingPendingConnections: 100,
},
});When choosing connections to close the connection manager sorts the list of connections by the value derived from the tags given to each peer. The values of all tags are summed and connections with lower valued peers are eligible for closing first. If there are tags with equal values, the shortest-lived connection will be closed first.
import { createLibp2p } from 'libp2p'
import { peerIdFromString } from '@libp2p/peer-id'
const libp2p = await createLibp2p({})
const peerId = await peerIdFromString('123Koo...')
// tag a peer
await libp2p.peerStore.merge(peerId, {
tags: {
'my-tag': {
value: 50, // 0-100 is the typical value range
ttl: 1000, // optional field, this tag will be deleted after this many ms
}
}
});
To prevent individual peers from opening multiple connections to a node, an inboundConnectionThreshold is configurable. This is the number of connections per second an individual peer can open to a node, once this threshold is crossed all further connections opened by that peer will be rejected until the threshold resets in the next second.
All fields are optional. The default values are defined in src/connection-manager/index.ts - please see that file for the current values.
import { createLibp2p } from 'libp2p'
const node = await createLibp2p({
connectionManager: {
/**
* A remote peer may attempt to open up to this many connections per second,
* any more than that will be automatically rejected
*/
inboundConnectionThreshold: 100,
},
});
libp2p stream multiplexers impose limits on the amount of streams that can be opened per connection, and also the amount of data that will be buffered for a given stream. The data should be consumed as fast as possible - if a stream's input buffer exceeds the limits set the stream will be reset.
These settings are done on a per-muxer basis, please see the README of the relevant muxer you are using.
@chainsafe/libp2p-yamux supports the following.
All fields are optional. The default values are defined in @chainsafe/libp2p-yamux/src/config.ts - please see that file for the current values.
import { createLibp2p } from 'libp2p'
import { yamux } from '@chainsafe/libp2p-yamux'
const node = await createLibp2p({
streamMuxers: [
yamux({
/**
* The total number of inbound protocol streams that can be opened on a given connection
*
* This field is optional, the default value is shown
*/
maxInboundStreams: 100,
/**
* The total number of outbound protocol streams that can be opened on a given connection
*
* This field is optional, the default value is shown
*/
maxOutboundStreams: 100,
})
]
});
When registering listeners for custom protocols, the maximum number of simultaneously open inbound and outbound streams per-connection can be specified. If not specified these will default to 32 inbound streams and 64 outbound streams.
If more than this number of streams for the given protocol are opened on a single connection, subsequent new streams for that protocol will be immediately reset.
Since incoming stream data is buffered until it is consumed, you should attempt to specify the minimum amount of streams required to keep memory usage to a minimum.
All fields are optional. The default values are defined in src/registrar.ts - please see that file for the current values.
import { createLibp2p } from 'libp2p';
const node = await createLibp2p({});
node.handle(
'/my-protocol/1.0.0',
(streamData) => {
// ..handle stream
},
{
maxInboundStreams: 100,
maxOutboundStreams: 100,
}
);Some transports allow configuring additional limits, please see their READMEs for full config options.
A non-exhaustive list follows:
The @libp2p/tcp transport allows additional limits to be configured.
All fields are optional. The full list of options is defined in @libp2p/tcp/src/index.ts - please see that file for more details.
import { createLibp2p } from 'libp2p'
import {tcp } from '@libp2p/tcp'
const node = await createLibp2p({
transports: [
tcp({
/**
* Inbound connections with no activity in this time frame (ms) will be closed
*/
inboundSocketInactivityTimeout: 20,
/**
* Outbound connections with no activity in this time frame (ms) will be closed
*/
outboundSocketInactivityTimeout: 20,
/**
* Once this many connections are open on this listener any further connections
* will be rejected - this will have no effect if it is larger than the value
* configured for the ConnectionManager maxConnections parameter
*/
maxConnections: 50,
}),
],
});
It is possible to configure some hosts to always accept connections from and some to always reject connections from.
import { createLibp2p } from 'libp2p'
const node = await createLibp2p({
connectionManager: {
/**
* A list of multiaddrs, any connection with a `remoteAddress` property
* that has any of these addresses as a prefix will be accepted ignoring
* all connection limits
*/
allow: [
'/ip4/43.123.5.23/tcp/3984',
'/ip4/234.243.64.2',
'/ip4/52.55',
// etc
],
/**
* Any connection with a `remoteAddress` property that has any of these
* addresses as a prefix will be immediately rejected
*/
deny: [
'/ip4/132.14.52.64/tcp/3984',
'/ip4/234.243.64.2',
'/ip4/34.42',
// etc
],
},
});
There is no a single config value to control the amount of memory js-libp2p uses.
Important details for ascertaining this are:
- Each connection has a multiplexer
- Each multiplexer has a buffer for raw incoming data (
muxer.maxUnprocessedMessageQueueSize) - The incoming data is parsed into messages for each stream and queued (
muxer.maxStreamBufferSize) - Each multiplexer has a stream limit for number of streams (
muxer.maxInboundStreams,muxer.maxOutboundStreams).
As a result, the max amount of memory buffered by libp2p is approximately:
connectionManager.maxConnections *
(muxer.maxUnprocessedMessageQueueSize
+ (muxer.maxInboundStreams * muxer.maxStreamBufferSize)
+ (muxer.maxOutboundStreams * muxer.maxStreamBufferSize)
)