Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Limit P2P Connections from Same IP #3497

Closed
bytemaster opened this issue May 28, 2018 · 5 comments
Closed

Limit P2P Connections from Same IP #3497

bytemaster opened this issue May 28, 2018 · 5 comments
Assignees
Milestone

Comments

@bytemaster
Copy link
Contributor

To prevent DOS attacks against public endpoints we need to limit the number of connections from the same IP.

@bytemaster bytemaster added this to the Version 1.0 milestone May 28, 2018
@pmesnier
Copy link
Contributor

Right. In this case, the limit should be 1. Using multiple connections to avoid message backlogs or to have a priority band is useful and we may want to add that later, however in that case we should have a second listen socket bound to some ephemeral port number which is supplied to the peer during handshake, and maybe only if a handshake is received signed by a known peer. But I digress.

@bytemaster
Copy link
Contributor Author

for our testing we would like the option to have the same IP connect multiple times, but it should default to banning it.

@pmesnier
Copy link
Contributor

how about an option p2p-max-nodes-per-host. I was translating IP address to "node" but you mean from multiple nodes on a given host address. Should this also be enforced on localhost?

@spoonincode
Copy link
Contributor

Because the default max number of connections is 25 for net_plugin, it seems like this sort of change won't get you much for out of box protection?

@bytemaster
Copy link
Contributor Author

This can be addressed at proxy level.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants