Nmap Development mailing list archives
Re: Error when running nmap -sP on internal network
From: Nelson <komseh () gmail com>
Date: Thu, 5 Mar 2009 12:52:15 -0600
nevermind... make clean and distclean fixed the issue On Thu, Mar 5, 2009 at 12:44 PM, Nelson <komseh () gmail com> wrote:
Testing on another network today... reverse dns resolution is definitely causing this error. On Wed, Mar 4, 2009 at 10:59 PM, Nelson <komseh () gmail com> wrote:I just made a co from svn and did some arp discovery on this local network. Errored out with: nmap: nsock_connect.c:292: nsock_connect_udp: Assertion `nsi->state == NSIOD_STATE_INITIAL || nsi->state == NSIOD_STATE_UNKNOWN' failed. Aborted attached is the output from: nmap --packet-trace -d2 -v -v -sP 10.71.0.0/24 This does not happen when I specify -n
_______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Error when running nmap -sP on internal network Nelson (Mar 04)
- Re: Error when running nmap -sP on internal network Nelson (Mar 05)
- Re: Error when running nmap -sP on internal network Nelson (Mar 05)
- Re: Error when running nmap -sP on internal network Fyodor (Mar 06)
- Re: Error when running nmap -sP on internal network Fyodor (Mar 06)
- Re: Error when running nmap -sP on internal network Daniel Roethlisberger (Mar 08)
- Re: Error when running nmap -sP on internal network Nelson (Mar 05)
- Re: Error when running nmap -sP on internal network Nelson (Mar 05)