Folks, is it normal that all incoming peers are unreachable?
The port numbers from these incoming peers look like dynamically opened ports as a result from an incoming connection to the respective hosts. I would expect the respective firewalls to deny access to those ports, but why would gLiveView display zero traffic and those peers to be “Unreachable”?
My understanding is, that the IP:Port of this node finds its way into the mainnet-topology of those peers and that is why this node has incoming connections from those peers.
i guess atleast your own producer should be reachable. i only have 3 incoming now and 1 is unreachable. had up to 7 yesterday i think. 3 or 4 where unreachable then
exactly, i was discussing about this topic with another SPO, and we believe is only ICMP test and nothing more.
when the nodes need to communicate for the blockchain, i believe it will work properly based on open port for the service.
Are you filtering ICMP packets? It is part of some guides and causes your nodes to not respond to ping anymore.
Check your ‘sudo nano /etc/ufw/before.rules’ for the following rule: ‘-A ufw-before-input -p icmp --icmp-type echo-request -j DROP’ (under: # ok icmp codes for INPUT)
Thanks for posting this. I just spent the last couple hours investigating the same phenomenon and was about to open up more ports on my firewall because gLiveView makes it look like something is not working. Thankfully I thought of posting the question on this forum first and your post came up as a suggestion as I was writing the post. This is probably making some pools less secure than they should be. They should remove that from the tool.
