Skip to content
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

Open
tmalaher opened this issue Feb 11, 2022 · 2 comments
Open

Distinguish between open/refused/timeout #11

tmalaher opened this issue Feb 11, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@tmalaher
Copy link

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.

@JustinTimperio JustinTimperio added the enhancement New feature or request label Feb 12, 2022
@JustinTimperio
Copy link
Owner

Send over a PR, and i'll give this new feature a test.

@tmalaher
Copy link
Author

Not happy with my current implementation. Need to do some more research/experimentation.
Go does not make it easy to distinguish the reasons that a Dial fails, unlike ECONNREFUSED in C.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants