Re: nmap errors on *BSDs (noted on NetBSD and MacOSX, so far) (traceroute)

[Patrik Karlsson <patrik () cqure net>]

On 23 mar 2010, at 21.56, David Fifield wrote:

> On Tue, Mar 23, 2010 at 09:18:02PM +0100, Fredrik Pettai wrote:
> > Yes, why not. I not more helpful to get a portscan then you asked for a 
> > traceroute, rather the opposite:
> >
> > $ nmap --traceroute ping.sunet.se
> >
> > Starting Nmap 5.21 ( http://nmap.org ) at 2010-03-23 21:11 CET
> > Warning: Traceroute does not support idle or connect scan, disabling...
> > Nmap scan report for ping.sunet.se (192.36.125.18)
> > Host is up (0.00025s latency).
> > Not shown: 995 closed ports
> > PORT      STATE SERVICE
> > 22/tcp    open  ssh
> > 25/tcp    open  smtp
> > 5666/tcp  open  nrpe
> > 13782/tcp open  netbackup
> > 13783/tcp open  netbackup
>
> You should be aware that even if you run the above command as root (so
> the traceroute works), you will still get a port scan in addition to the
> traceroute. To turn off the port scan you have to use the -sn option.
> Each of the scan phases can be activated and deactivated individually.
>
> David Fifield
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://seclists.org/nmap-dev/


Hmm, I just ran nmap with the traceroute option on Snow Leopard.
I'm seeing a single hop for any host I'm scanning:

sudo ./nmap -sn --traceroute scanme.insecure.org

Starting Nmap 5.21 ( http://nmap.org ) at 2010-03-23 23:03 CET
Warning: Unable to open interface vboxnet0 -- skipping it.
Nmap scan report for scanme.insecure.org (64.13.134.52)
Host is up (0.0027s latency).
rDNS record for 64.13.134.52: scanme.nmap.org

TRACEROUTE (using port 80/tcp)
HOP RTT     ADDRESS
1   3.27 ms scanme.nmap.org (64.13.134.52)

Nmap done: 1 IP address (1 host up) scanned in 0.04 seconds

I'm running the latest svn version.

//Patrik

--
Patrik Karlsson
http://www.cqure.net
http://www.twitter.com/nevdull77





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