Skip to main content
added 12 characters in body
Source Link
jtgrassie
  • 19.4k
  • 4
  • 15
  • 52

The default value for in-peers is -1 (unlimited). The reason -1 is (in effect) unlimited is because max_in_connection_count is an unsigned integer and therefore 0-1 wraps to the maximum of an uint32_t (i.e. 2^32-1).

If you need to limit the inbound connections, set in-peers=N (replacing N with the number of incoming peers to allow) in your daemon config.

The default value for in-peers is -1 (unlimited). The reason -1 is unlimited is because max_in_connection_count is an unsigned integer and therefore 0-1 wraps to the maximum of an uint32_t (i.e. 2^32-1).

If you need to limit the inbound connections, set in-peers=N (replacing N with the number of incoming peers to allow) in your daemon config.

The default value for in-peers is -1 (unlimited). The reason -1 is (in effect) unlimited is because max_in_connection_count is an unsigned integer and therefore 0-1 wraps to the maximum of an uint32_t (i.e. 2^32-1).

If you need to limit the inbound connections, set in-peers=N (replacing N with the number of incoming peers to allow) in your daemon config.

Source Link
jtgrassie
  • 19.4k
  • 4
  • 15
  • 52

The default value for in-peers is -1 (unlimited). The reason -1 is unlimited is because max_in_connection_count is an unsigned integer and therefore 0-1 wraps to the maximum of an uint32_t (i.e. 2^32-1).

If you need to limit the inbound connections, set in-peers=N (replacing N with the number of incoming peers to allow) in your daemon config.