Hi @natanzi , ok it could make sense that if the server is reachable then the result is Y, and otherwise N.
But what’s the configuration of the ping like though? What would be the packet size and how many ping should be sent? Most OS’s don’t send just 1 ping. For example, Windows I think send 4 or 5 pings, and then give you a percentage results depending on how many of the 4 or 5 were reachable. In Linux, and I assume on MacOS would be the same, it keeps pinging until you actually break (CTRL-C) it. Would it be just 1 ping in Knime’s case? If it’s just 1 ping, it will simply calculate the reachability at THAT time (when it executed) - while each ping would also actually calculate the reachability at the time it ran, running several pings show patterns of the connectivity (hence why OS’s send multiple pings).
Also, as I mentioned, ping returns other information such as the ttl and the response time.
As I said, I think it can be a great feature, but I’m not sure how it should be implemented. And to also re-iterate what I said, it’s different from a dns lookup. Great feature to have, but it should not be used to replace a dns lookup.