I'm running a 0.15 full node, it's still currently downloading the chain, but I cannot get it to be reachable.
I have opened ports 8332:8333, and set up firewall policies for port 8333. With this config I managed to get the node to be visible by https://bitnodes.21.co/ twice, but when I'd redo the test just a minute after in order to double check, it'd fail without having touched anything.
Since then I've been trying to recreate this config, resetting the service, recreating the port forwarding policies in the router etc. but I haven't managed to connect again.
When I run netstat -tuplen on the node, I can see the following: Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:8332 0.0.0.0:* LISTEN 1000 66314 3341/bitcoind
tcp 0 0 0.0.0.0:8333 0.0.0.0:* LISTEN 1000 66346 3341/bitcoind
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 11362 –
tcp6 0 0 ::1:8332 :::* LISTEN 1000 66312 3341/bitcoind
tcp6 0 0 :::8333 :::* LISTEN 1000 66345 3341/bitcoind
Which makes me think the ports aren opened correctly, since there are no packages sent or received.
I can see this type of traces: receive version message: /Satoshi:0.15.0(UASF-SegWit-BIP148)/: version 70015, blocks=486762, us=126.96.36.199:52288, peer=0 receive version message: /bitnodes.21.co:0.1/: version 70015, blocks=486762, us=188.8.131.52:8333, peer=4
Which seems like the node is reachable.
I can also see messages the likes of: connect() to 184.108.40.206:8333 failed after select(): Connection refused (111) version handshake timeout from 4 connect() to [2001:0:9d38:6ab8:2029:2343:a118:7799]:8333 failed: Network is unreachable (101)
Which don't look good
When I run: bitcoin-cli getpeerinfo I have peers connected to (just 2 or 3 though)
I don't have more than 8 connections, usually 2-7
What happened? I managed to get the node online but then a minute later it would no longer work. How can I verify my port forwarding is correct? what firewall policies should I setup?
Thanks a lot