Re: using nmap and find

[Tom Sellers <nmap () fadedcode net>]

On 4/3/2016 8:10 AM, Mike . wrote:
> hello all
>
>
> i might look stupid here, but oh well. still need this solved. i am using a simple FIND to view a VERY SPECIFIC 
> LINE/STRING using nmap. i want to see the exact payload lines probing a host. why the
> hell do i continue to see all this NSOCK info when i don't wish to see it???! an example:
>
>
> nmap -n -T4  192.168.0.10 -p 1500 -sV -d2 | find "sending probe"
>
>
> output is this!  : 
>
>
> NSOCK INFO [2.1480s] nsock_iod_new2(): nsock_iod_new (IOD #1)
> NSOCK INFO [2.1490s] nsock_connect_tcp(): TCP connection requested to 192.168.0.
> 10:1500 (IOD #1) EID 8
> NSOCK INFO [2.1490s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS f
> or EID 8 [192.168.0.10:1500]
> NSOCK INFO [2.1500s] nsock_read(): Read request from IOD #1 [192.168.0.10:1500]
> (timeout: 6000ms) EID 18
> Service scan sending probe NULL to 192.168.0.10:1500 (tcp)
> NSOCK INFO [8.1510s] nsock_trace_handler_callback(): Callback: READ TIMEOUT for
> EID 18 [192.168.0.10:1500]
> NSOCK INFO [8.1510s] nsock_write(): Write request for 10 bytes to IOD #1 EID 27
> [192.168.0.10:1500]
> Service scan sending probe Verifier to 192.168.0.10:1500 (tcp)
> NSOCK INFO [8.1510s] nsock_read(): Read request from IOD #1 [192.168.0.10:1500...........(goes on for a long time)
>
>
> all i want here is the following line:  Service scan sending probe NULL
>
> thanks
> Mike

Mike,
  The output streams are different. You need to redirect STDERR to null using 2>nul

See the instructions and example here:
  http://seclists.org/nmap-dev/2015/q4/164

Verified to work on Windows 10.

Tom

_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/