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

Add Fullnode network port diagnostic mechanism #3915

Closed
mvines opened this issue Apr 20, 2019 · 0 comments · Fixed by #5795
Closed

Add Fullnode network port diagnostic mechanism #3915

mvines opened this issue Apr 20, 2019 · 0 comments · Fixed by #5795
Milestone

Comments

@mvines
Copy link
Member

mvines commented Apr 20, 2019

Problem

I burned a ton of time in #3840 debugging what ultimately turned out to be an incorrect inbound network configuration of the VM I was using. Repair requests from other nodes were being blocked by the firewall settings 🤕. This is very likely going to be a problem for others and we'll surely have a ton of support requests as a result.

Proposed Solution

Add a mechanism solana-fullnode,solana-gossip, or some other cli tool that ensures that all inbound/outbound ports are not being blocked, perhaps via some ping/pong with the cluster entry point node.

Also confirm that the ports reported over gossip by other nodes are accessible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant