Nmap Development mailing list archives
Possible bug: different results based on scan range
From: "Sergio Sergio" <zerge69 () gmail com>
Date: Mon, 12 May 2008 00:01:34 -0500
Hi, I'm running the newest Nmap on Windows XP. I run the following scan: nmap xxx.xxx.1.* -p80,5060 -oN result.txt -vv Upon checking the result.txt file, I see that xxx.xxx.1.193 has port 5060 as "filtered". Then I run : nmap xxx.xxx.1.193 -p80,5060 -oN result.txt -vv When I check result.txt, I see that xxx.xxx.1.193 has port 5060 as "closed". Then I run several ranges, such as: xxx.xxx.1.100-200 xxx.xxx.1.150-250 etc. and in all cases xxx.xxx.1.193 port 5060="closed" BUT if I scan xxx.xxx.1.1-220 or any number above 220, I get port 5060="filtered" Since the results are only changing based on the scan range, I can only think it's some sort of bug. I've tried also with different T[n], but it doesn't change the results. I thought maybe I was losing packets, but I don't see why I would. I hope this helps Regards, Sergio _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Possible bug: different results based on scan range Sergio Sergio (May 11)