-
Notifications
You must be signed in to change notification settings - Fork 19
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
Comparsion with nmap #3
Comments
Well, as far as I see, under my current limited circumstance, its result is 0 UDP port opened, but nmap find more. |
Provide more details, so I can replicate the issue:
|
161/162 udp
parrot linux, or more precisely, hackthebox pwnbox
no, on the cloud
yes. And also, it's a lab machine in hackthebox. But |
Ok. First of all, the port number 162 is not in database:
I will add it to the snmp in the next release. Second, what version of snmp protocol is the remote host running? It is possible but highly unlikely, that I am missing some probes for specific implementation. Also, try to increase the wait time: |
v2c. I will try later. I think the problem might be wait time, since previous scan might triggered icmp error message limit. Thanks for your quick response. |
I am always open to constructive criticism. UDPX is effective for scanning larger networks, /24 or so. Remember, that it is packet-based approach, so it does not wait for ICMP message, but rather a response. |
I'm new to this project, and it looks interesting to me. But I'm wondering
The text was updated successfully, but these errors were encountered: