You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even when running a small network, peer should not get banned if not misbehaving.
To achieve that
the counter for getPeers should be reset every discovery period (30s)
Returned length of peer list should be lowered to 200 from 1000
Actual behavior
When connecting 2 nodes, since one node constantly ask for peers (since it does not have enough outbound peer) from seed node, it will reach threshold of banning after a while.
Every 30s it will increase penalty by 10, so after 300s it will get banned
Steps to reproduce
Connect 2 local nodes and wait for more than 5 mins to see if non-seed node will get banned
Which version(s) does this affect? (Environment, OS, etc...)
5.0.0-alpha.0
Additional Information
Resetting the counter every 10s on peer/base.ts should mitigate this problem
The text was updated successfully, but these errors were encountered:
Expected behavior
Even when running a small network, peer should not get banned if not misbehaving.
To achieve that
200
from1000
Actual behavior
When connecting 2 nodes, since one node constantly ask for peers (since it does not have enough outbound peer) from seed node, it will reach threshold of banning after a while.
Every 30s it will increase penalty by 10, so after 300s it will get banned
Steps to reproduce
Connect 2 local nodes and wait for more than 5 mins to see if non-seed node will get banned
Which version(s) does this affect? (Environment, OS, etc...)
5.0.0-alpha.0
Additional Information
Resetting the counter every 10s on
peer/base.ts
should mitigate this problemThe text was updated successfully, but these errors were encountered: