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

Peer discovery failure #5

Open
varuneranki opened this issue Oct 16, 2024 · 2 comments
Open

Peer discovery failure #5

varuneranki opened this issue Oct 16, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@varuneranki
Copy link
Owner

Peers cannot discover when docker containers are deployed across the network.

Network 1 used: EDUROAM hosted by University of Paderborn
Network 2 used: WebAuth hosted by University of Paderborn
Network 3 used: Home network self-hosted with Vodafone (WORKS Flawless)

Diagnosis of networks 1 & 2 is not possible and unknown firewall settings.

@varuneranki varuneranki added the bug Something isn't working label Oct 16, 2024
@varuneranki varuneranki self-assigned this Oct 16, 2024
@varuneranki
Copy link
Owner Author

Solution use LibP2P NAT Hole Punching .

@varuneranki
Copy link
Owner Author

NAT Hole Punching has ongoing issues and solution cannot be achieved until it is fixed.

Partial Solution: use Network 3 to run tests and generate results.
How?
use docker network and join the containers to the network for performing peer to peer discovery and test the FeverBFT algorithm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant