Port based load balancing

[jimaek]

Lets say a user tries to ping port 22 and it fails. We dont know if the fail is because the target has a closed port 22 or if the probe itself has a firewall blocking outgoing connections to port 22. We just show connection timeout.

We could allow users to specify blocked ports per probe and when running measurements we would exclude automatically all probes that have the user selected port blocked.

[alexey-yarmosh]

Can't it be an auto check to some known host with open ports? E.g. to top 20 popular ports by schedule and to others on demand, when probe got measurement with port which failed.

[jimaek]

In theory we could but sounds complicated to auto track ports per probe

[MartinKolarik]

Blocking outgoing connections is fairly rare, checking all ports automatically would be too much work for the probe, and expecting most users to configure this doesn't seem realistic either. I'd say if anyone actually realizes they need this config, the correct thing to do is change the firewall rules.