Describe the bug
The aggressive scanning nature of Testrun can trigger DOS attack prevention mechanisms in devices.
Naturally, this can (and will in the case of the above) cause legitimate services that Testrun wants to detect, to close. E.g. the web server running on port 5011 in the case of the above. This could manifest as a false negative in a test report.
Expected behavior
Testrun should be more graceful in its approach to avoid triggering DOS prevention mechanisms that subsequently 'hide' legitimate services from Testrun's services detection mechanism.
Environment (please provide the following information about your setup):
Additional context
This subject has been raised a number of times, notably in #885 and #1290. PR's #1516 and #1521 go some way in making Testrun more graceful, but that's only at the broad TCP and UDP service scan layer.
Describe the bug
The aggressive scanning nature of Testrun can trigger DOS attack prevention mechanisms in devices.
Naturally, this can (and will in the case of the above) cause legitimate services that Testrun wants to detect, to close. E.g. the web server running on port 5011 in the case of the above. This could manifest as a false negative in a test report.
Expected behavior
Testrun should be more graceful in its approach to avoid triggering DOS prevention mechanisms that subsequently 'hide' legitimate services from Testrun's services detection mechanism.
Environment (please provide the following information about your setup):
Additional context
This subject has been raised a number of times, notably in #885 and #1290. PR's #1516 and #1521 go some way in making Testrun more graceful, but that's only at the broad TCP and UDP service scan layer.