Re: nmap 5.10-beta1

[David Fifield <david () bamsoftware com>]

On Mon, Dec 14, 2009 at 10:40:38AM +0200, Maxim wrote:
> Greetings. nmap 5.10-beta1 don't have a bug but a little usability lost.
> when using network scan to detect hosts up output become multiline, so
> such filtering
> as "grep up" is seamless now.
>
> Examples of network scanning:
>
> version 5.10-beta1
> shamanu4 # nmap -v -sP 192.168.65.1-254 | grep up
> Host is up (0.16s latency).
> Host is up (0.00016s latency).
> Host is up (0.00027s latency).
> Host is up (0.00025s latency).
> Host is up (0.00043s latency).
> Host is up (0.00062s latency).
> Host is up (0.00072s latency).
> Host is up (0.00037s latency).
> Host is up (0.00037s latency).
> Host is up (0.00051s latency).
>
> version 5.0
> shamanu4 # nmap -v -sP 192.168.65.1-254 | grep up
> Host 192.168.65.1 is up (0.048s latency).
> Host 192.168.65.2 is up (0.00022s latency).
> Host 192.168.65.10 is up (0.00038s latency).
> Host 192.168.65.15 is up (0.00047s latency).
> Host 192.168.65.17 is up (0.00060s latency).
> Host 192.168.65.24 is up (0.0017s latency).
> Host 192.168.65.27 is up (0.00040s latency).
> Host 192.168.65.28 is up (0.00036s latency).
> Host 192.168.65.29 is up (0.00049s latency).

Try
        nmap | grep -B 1 "^Host is up"
or
        nmap | grep "^Nmap scan report" | grep -v "host down"
instead. If you don't give the -v option to Nmap you don't need the
second grep. We started to get more information from a ping scan than
could be shown easily on a single line, like both the forward and
reverse DNS name. Here's part of that discussion:

http://seclists.org/nmap-dev/2009/q4/199

I admit, though, that this is clumsier than it used to be.

David Fifield
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/