Nmap Development mailing list archives
Re: Discovery issue
From: Daniel Miller <bonsaiviking () gmail com>
Date: Thu, 31 Oct 2013 09:26:32 -0500
On 10/31/2013 07:24 AM, martin.pilote () videotron com wrote:
Hello, I searched over the web and i was not able to find out what is wrong with nmap. I'm doing vulnerability scan with nessus but before i'm using nmap to check wich IP is alive. Soo before Mars 2013, i was using nmap with -sn, --reason and results was pretty fine. After updated from version 5.5 to 6.4, almost all the IP is not considered as UP. I've tested yesteday with version 5.5 and 6.4 for 6300 IP : 5.5 = 132 are UP 6.4 = 1648 are UP When i check into the result, a lot of them seem to be caused by a reset and most of them dont have any open or filtered port. Any one have a clue ? Martin _______________________________________________ Sent through the dev mailing list http://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Martin,So that we can better diagnose your problem, would you mind sending the output of "nmap --version" and "nmap --iflist" (sanitized if you like)? There were some changes to route detection between those versions, and you may have an interface type that we don't handle yet. Also, information about your OS would be helpful.
Dan _______________________________________________ Sent through the dev mailing list http://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- Discovery issue martin . pilote (Oct 31)
- Re: Discovery issue Daniel Miller (Oct 31)
- Re: Discovery issue martin . pilote (Oct 31)
- Re: Discovery issue Daniel Miller (Oct 31)