-
Notifications
You must be signed in to change notification settings - Fork 20.5k
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
cannot connect to static/trusted peers with --maxpeers 0 #3326
Comments
I confirm this behaviour on geth 1.5.3, on geth 1.4.9, 1.4.10 and 1.4.11 the expected behaviour is still working correctly. |
Any update on this? Parity explicitly allows this: --reserved-peers FILE Provide a file containing enodes, one per line. |
System information
Geth version: 1.5.2+ (from master)
OS & Version: Windows 10
Expected behaviour
when set --maxpeer 0, only the trusted/static peers can connect
Actual behaviour
when set --maxpeer 0, even trusted/static peers can NOT connect
Steps to reproduce the behaviour
it could be caused by light clinet/server mode's implementation,
which limit connections only by maxpeers in protocol manager/handler.
besides, there is a race condition for the maxpeers check in protocol manager/handler.
you can connect to more then one static nodes even with static-nodes.js and --maxpeers 1,
but you can not further add more static nodes with admin.addPeer().
(It will be removed for "too many peers!")
Partial output of geth
notice that what have been done to peer ceabe1b1b4fa9c88
The text was updated successfully, but these errors were encountered: