-
Notifications
You must be signed in to change notification settings - Fork 717
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] Masternodes running on IPv6 will not allow more than 16 connections #2696
Comments
maxconnections sets the most connections to peers (in + outbound) the most automatic outbound connections are limited to 16 Lines 60 to 61 in 5a7b514
|
Hi Peter |
Limiting connection is a good thing, the server CPU suffers when there is too many threads. usually up to 16 connections is ok to support the network but I checked my nodes on IPv6 and I have some with 37 connections, so not sure what the problem is |
As I dive deeper into the subject I realized there are 2 aspects and now this #2696 (comment) answer makes sense. There are incoming connection and outgoing connections. like I said "on IPv6 and I have some with 37 connections" this means 16 is like outgoing, and 21 is incoming, my limit is set to 128 I vote to close this ticket as not an issue, all works OK by design |
Masternodes running on IPv6 will not allow more than 16 connections
Can you reliably reproduce the issue?
If so, please list the steps to reproduce below:
Expected behavior
Masternodes on IPv6 should allow more connections
Actual behavior
Masternodes running on IPv6 will not allow more than 16 connections
Screenshots.
If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.
What version of PIVX Core are you using?
"version": 5040000,
"protocolversion": 70924,
"services": "NETWORK/BLOOM/",
"walletversion": 170000,
Machine specs:
Any extra information that might be useful in the debugging process.
This is normally the contents of a
debug.log
,db.log
orconfig.log
file. Raw text or a link to a pastebin type site are preferred.The text was updated successfully, but these errors were encountered: