-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
The problem that 65535 ports are fully open #2514
Comments
Can I try resolving these issue? |
@Ma1Dong I think you should give range of 200 ports at a time ? |
Put a cap on the ports |
I didn't express myself clearly,sorry。What I mean is When I scan the port of an IP,he result is that all ports on this IP are open,Obviously, this is caused by firewall policy,so,When I scan the addresses in bulk(nmap -iL ip.txt),I want to skip the IP in there,I can't use timeout,This may affect the results of other ip。 so,it is a good idea for me to skip the scan of an IP when the number of ports is greater than 200。What should I do,thank you! For example,I need to scan 100 IP addresses,In the scan result, all ports of the 60th IP address are open. This IP address occupies a lot of scanning time。 The command I use is: |
So I think we should add a -count option also |
sorry,I don't understand what you mean,What I'm thinking is that when you have too many open ports, I want to skip this IP scan。Nmap does not provide this parameter。 |
|
@rewanthtammana @bonsaiviking @wongwaituck Hey could you let me know where I can do the changes ? |
@bhaveshraj336 https://seclists.org/nmap-dev/2014/q2/545 you can try this patch |
The problem that 65535 ports are fully open is frequently encountered. Or thousands of ports open. If I want to skip the scan of the IP address if the number of ports exceeds 200, how should I solve this problem? Thank you.
The text was updated successfully, but these errors were encountered: