Nmap Development mailing list archives
Re: nmap (win32 4.60) bug and a fix
From: Ionreflex <ionreflex () gmail com>
Date: Fri, 11 Apr 2008 10:41:33 -0400
There you go, with some delays : [snap] Microsoft Windows XP [version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Program Files\Nmap>nmap 192.168.51.255 Starting Nmap 4.60 ( http://insecure.org ) at 2008-04-10 16:29 Est (heure d'ÚtÚ) Note: Host seems down. If it is really up, but blocking our ping probes, try -PN Nmap done: 1 IP address (0 hosts up) scanned in 0.617 seconds C:\Program Files\Nmap>nmap -PN 192.168.51.255 Starting Nmap 4.60 ( http://insecure.org ) at 2008-04-10 16:29 Est (heure d'ÚtÚ) Nmap done: 1 IP address (0 hosts up) scanned in 0.617 seconds C:\Program Files\Nmap>ipconfig /all Configuration IP de Windows Nom de l'hôte . . . . . . . . . . : m4tr1x Suffixe DNS principal . . . . . . : null.p0rt4l.net Type de nœud . . . . . . . . . . : Hybride Routage IP activé . . . . . . . . : Non Proxy WINS activé . . . . . . . . : Non Liste de recherche du suffixe DNS : null.p0rt4l.net null.p0rt4l.net p0rt4l.net Carte Ethernet eth0: Suffixe DNS propre à la connexion : null.p0rt4l.net Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet Adresse physique . . . . . . . . .: 00-1A-4B-00-00-00 DHCP activé. . . . . . . . . . . : Oui Configuration automatique activée . . . . : Oui Adresse IP. . . . . . . . . . . . : 192.168.51.248 Masque de sous-réseau . . . . . . : 255.255.255.0 Passerelle par défaut . . . . . . : 192.168.51.1 Serveur DHCP. . . . . . . . . . . : 192.168.1.1 Serveurs DNS . . . . . . . . . . : 192.168.1.1 Serveur WINS principal. . . . . . : 192.168.1.1 Bail obtenu . . . . . . . . . . . : 10 avril 2008 15:43:30 Bail expirant . . . . . . . . . . : 18 avril 2008 15:43:30 C:\Program Files\Nmap> [/snap] In my point of view, it should scan all decks in my LAN, right ? Am I doing something wrong ? 2008/4/9, DePriest, Jason R. <jrdepriest () gmail com>:
What happens if you point it at the broadcast address for your local network? If I point it at 192.168.51.255 I get the same thing you do because I can't get to that address. If I point it at my own .255 address (I am in a class C), it works fine. I still don't get a loop. I've attached a -vvv -d9 output of my scanning a valid .255. -Jason _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
_______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Re: nmap (win32 4.60) bug and a fix Fyodor (Apr 08)
- Re: nmap (win32 4.60) bug and a fix Ionreflex (Apr 09)
- Re: nmap (win32 4.60) bug and a fix DePriest, Jason R. (Apr 09)
- Re: nmap (win32 4.60) bug and a fix Ionreflex (Apr 11)
- Re: nmap (win32 4.60) bug and a fix Dudi I (May 04)
- Re: nmap (win32 4.60) bug and a fix DePriest, Jason R. (Apr 09)
- Re: nmap (win32 4.60) bug and a fix Ionreflex (Apr 09)