Author

Topic: Are these peers with triple connections valid? (Read 601 times)

full member
Activity: 136
Merit: 120
November 05, 2016, 10:49:12 AM
#4
Is there an easy way to ban multiple connections from the same IP, without say, doing something drastic like blacklisting AWS IP addresses.
Not really.

Ok, thanks.

I think there might be a way to limit the number of incoming connections per IP using a reverse proxy such as HAProxy. It doesn't ban them but at least it limits the damage by blocking the extra connections. The problem for me is that HAProxy only runs on Linux and my nodes are currently Windows boxes.
I use firewall rules to limit concurrent connections.  But this is on Ubuntu, so it won't help you with Windows.
donator
Activity: 1617
Merit: 1012
Is there an easy way to ban multiple connections from the same IP, without say, doing something drastic like blacklisting AWS IP addresses.
Not really.

Ok, thanks.

I think there might be a way to limit the number of incoming connections per IP using a reverse proxy such as HAProxy. It doesn't ban them but at least it limits the damage by blocking the extra connections. The problem for me is that HAProxy only runs on Linux and my nodes are currently Windows boxes.
staff
Activity: 3458
Merit: 6793
Just writing some code
Those are spam nodes. You should just ban them.

Is there an easy way to ban multiple connections from the same IP, without say, doing something drastic like blacklisting AWS IP addresses.
Not really.
donator
Activity: 1617
Merit: 1012
Every now and then these peers connect to my node with 3 connections each. They don't take up much bandwidth but they hold the connections open for a long time.



They claim to be SPV clients. Are they valid peers and why do they need 3 connections?

Is there an easy way to ban multiple connections from the same IP, without say, doing something drastic like blacklisting AWS IP addresses.
Jump to: