I checked what you mentioned, and if you take abit's seed for example, the ping doesn't come back however you can actually connect to the seed node (verify with $ telnet steem-seed1.abit-more.com 2001). So I guess abit must've closed his firewall to not answer icmp requests, but the seed is online.
On a related note the seed nodes status is now more resilient to random network errors that some people have been reporting. Although not an real fix for this issue, the page should now properly show those affected nodes as online. (see here)
Ah indeed, I overlooked the possibility of blocked icmp. This is problematic for the purpose of this script, which is to determine the best pings. Let me see if I can find a solution for that.
great job @drakos..Thanks buddy!!!
For those who are already using the script, check the ADDENDUM for an improved version. Thanks to @wackou for pointing out the ICMP issue.
Good work @drakos must be resteemed
hey @drakos, nice script ;)
I checked what you mentioned, and if you take abit's seed for example, the ping doesn't come back however you can actually connect to the seed node (verify with
$ telnet steem-seed1.abit-more.com 2001). So I guess abit must've closed his firewall to not answer icmp requests, but the seed is online.On a related note the seed nodes status is now more resilient to random network errors that some people have been reporting. Although not an real fix for this issue, the page should now properly show those affected nodes as online. (see here)
Ah indeed, I overlooked the possibility of blocked icmp. This is problematic for the purpose of this script, which is to determine the best pings. Let me see if I can find a solution for that.