The TcpListener binding is not correctly configured for Windows edge-cases.
We should port the code from Bootstrap listener that has the correct behaviour (sets the needed flag with a socket2 socket:
socket.set_only_v6(false)?;
Right now, the bug probably means:
- That windows node runners with IPv4 should bind the protocol on IPv4 format in the config in order to be routable:
[protocol]
bind = "0.0.0.0:31244"
- (Needs testing to be sure) Maybe routable windows node runners with IPv6 can only get INs from IPv6. Note: I don't seem to have trouble with this, but I'll wait for after genesis on mainnet to be sure, IN connections are few.
The TcpListener binding is not correctly configured for Windows edge-cases.
We should port the code from Bootstrap listener that has the correct behaviour (sets the needed flag with a socket2 socket:
Right now, the bug probably means: