-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Disable or limit the check whether the prover listener port is open #1574
Comments
In addition to this, there used to be a proposal to use UPnP for automatic port forwarding for testnet1. I'll try to revive it for testnet2 shortly. |
I just filed https://github.com/AleoHQ/snarkOS/pull/1575 that should aid port forwarding with UPnP-enabled routers. |
ok, it should be an option logic, not default logic |
https://github.com/AleoHQ/snarkOS/blob/506fcbf33d555a528efcec6c0fc1fe5c21902f22/src/network/peer.rs#L234-L248 |
I had tried https://github.com/AleoHQ/snarkOS/pull/1575, The problem still exists. |
Here is my network topology. |
This check is currently disabled, so closing the issue. |
💥 disable or limit the check whether the prover listen port
We run prover in home network, and the
operator
just disconnect theprover
because we can not set the NAT or port forwarding in our router. As the help from @HarukaMa, we disable the check for port inoperator
andprover
. Indeed, it not easy to do the NAT and port forwarding in home network, so we suggest disable the check forprover
.The text was updated successfully, but these errors were encountered: