Skip to content
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

Connecting to bootnode fails #4907

Closed
martinconic opened this issue Nov 21, 2024 · 1 comment · Fixed by #4909
Closed

Connecting to bootnode fails #4907

martinconic opened this issue Nov 21, 2024 · 1 comment · Fixed by #4909
Labels
needs-triaging new issues that need triaging

Comments

@martinconic
Copy link
Contributor

⚠️ Support requests in an issue-format will be closed immediately. For support, go to Swarm's Discord.

Context

Summary

Connecting to bootnode fails:

"time"="2024-11-20 15:49:53.360738" "level"="warning" "logger"="node/kademlia" "msg"="connect to bootnode failed" "bootnode_address"="/ip4/49.12.172.37/tcp/32490/p2p/QmZsYCbkUXWpfR34PmUwMJvHwJtGfbcMMoAp1G2EydkpRA"
"time"="2024-11-20 15:49:53.360749" "level"="debug" "logger"="node/kademlia" "msg"="discover to bootnode failed" "bootnode_address"="/dnsaddr/sepolia.testnet.ethswarm.org" "error"="discover /dnsaddr/bee-0.sepolia.testnet.ethswarm.org: discover /ip4/49.12.172.37/tcp/32490/p2p/QmZsYCbkUXWpfR34PmUwMJvHwJtGfbcMMoAp1G2EydkpRA: network status unknown: connect full close stream reset"

Expected behavior

Actual behavior

Steps to reproduce

Possible solution

@martinconic martinconic added the needs-triaging new issues that need triaging label Nov 21, 2024
@istae istae linked a pull request Nov 21, 2024 that will close this issue
4 tasks
@istae
Copy link
Member

istae commented Nov 21, 2024

with #4871 bootnodes started blocklisting peers
which caused first time connecting peers to be blocklisted almost instantly because the bootnode blocklists peers for protocol requests like pullsync
generally these requests are not fired after the warmup period but if the warmup period is reduced then the fresh node can be blocked from joining the network through the bootnode.

the fix should be that peers should be sending any protocol requests to the bootnode, ever which is handled in #4909

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triaging new issues that need triaging
Projects
None yet
2 participants