mirror of
https://github.com/nmap/nmap.git
synced 2026-08-04 06:40:48 +00:00
Add a few items, suggested by David Lam (http://seclists.org/nmap-dev/2011/q3/905)
This commit is contained in:
parent
4a947b23d0
commit
a451b65483
1 changed files with 16 additions and 0 deletions
|
|
@ -149,6 +149,22 @@
|
|||
does the IP doesn't reverse resolve) is specified on the command
|
||||
line, should we use that version, or the official rDNS, if any?
|
||||
- Some more discussion on this topic on nmap-dev may be warranted.
|
||||
|
||||
* From: David Lam <david@thedavid.net>, "Some general questions about
|
||||
Nping/Ncat"
|
||||
|
||||
In TCP traceroute mode, would it be possible to ask Nping to
|
||||
stop once it gets an SYN-ACK response back from the destination host rather
|
||||
than continuously hitting the host until the max TTL?
|
||||
|
||||
* Make broadcast ping work. Currently the following command does not
|
||||
show any captured packets:
|
||||
nping 192.168.0.255 --dest-mac ff:ff:ff:ff:ff:ff -c 1
|
||||
The cause is probably the BPF filter, which only allows replies from
|
||||
192.168.0.255.
|
||||
Also, look into official multicast addresses like 224.0.0.1. Can we
|
||||
received replies to that probe?
|
||||
|
||||
|
||||
* Do some performance testing.
|
||||
Fyodor:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue