-
Notifications
You must be signed in to change notification settings - Fork 55
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
Returned Address Sets always contains ip *.*.*.255 #4
Open
gonzochic opened this issue
Feb 3, 2019
· 2 comments
· Fixed by gabstv/netscan#1 · May be fixed by #7
Open
Returned Address Sets always contains ip *.*.*.255 #4
gonzochic opened this issue
Feb 3, 2019
· 2 comments
· Fixed by gabstv/netscan#1 · May be fixed by #7
Comments
nitper
added a commit
to nitper/netscan
that referenced
this issue
Mar 6, 2019
pass copies of `ip` and `port` into the goroutine fixes jessfraz#4
The current Scan() is unusable right now. I was thinking that something was wrong on my network. Thanks for the PR! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
if you run
Scan()
the result will always contain the number of open ips on the specific port but always the same IP (e.g. 10.0.1.255 or 192.168.1.255).This is caused because you dereference a variable inside a GO Routine which was referenced inside a Range Loop.
and then
To fix that, you need to copy the id first into a variable and pass it into the go routine (as you did with address).
The text was updated successfully, but these errors were encountered: