-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distinguish between open/refused/timeout #11
Labels
enhancement
New feature or request
Comments
Send over a PR, and i'll give this new feature a test. |
Not happy with my current implementation. Need to do some more research/experimentation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In my local copy I've made modifications so that the portResult distinguishes between these three cases:
Connect OK - LISTEN process on the other end made a connection
Timeout - Firewall blocked connection
Connection Refused - Firewall did not block connection, but no LISTENing process on the other end. Thus this port could be used for a new server process
I find this handy because I don't want to have to open new ports in the firewall, and so I need to see what ports are open without having to run a listening process on all ports.
The text was updated successfully, but these errors were encountered: