Re: Errors on Mac 10.5 with NSE

[MadHat Unspecific <madhat () unspecific com>]

Eddie Bell wrote:
> The router may have been rate limiting your icmp exceeded messages or
> if it was a cheap router then it may not have been able to handle the
> traffic generated by -A (my old router crashed with too much nmap
> traffic!)
>
> If you can reproduce it, a dump of --packet-trace would be very useful
>   

Yeah, I ave been at client sites, so I don't think it was cheap gear, 
but rate limiting may have done it. 

Sorry for the false report.  I'll keep trying to reproduce it.  If I do, 
I'll get more info.

> - eddie
>
> On 14/11/2007, MadHat Unspecific <madhat () unspecific com> wrote:
>   
> > Kris Katterjohn wrote:
> >     
> > > MadHat Unspecific wrote:
> > >
> > >       
> > > > NEW ISSUE:
> > > > Traceroute does not appear to be working.  A host that is 11 hops away,
> > > > when I scan using the -A (I am lazy) I get an error that max TTL reached.
> > > >
> > > > TRACEROUTE (using port 22/tcp)
> > > > HOP RTT ADDRESS
> > > > ! maximum TTL reached (50)
> > > >
> > > > but when I just did a -T4 -vvv --traceroute, it works fine.
> > > > TRACEROUTE (using port 22/tcp)
> > > > HOP RTT    ADDRESS
> > > > 1   3.19   home (192.168.1.254)
> > > > ...
> > > >
> > > >
> > > > any idea or what we might try to hunt down the problem?  My brain
> > > > stopped working a few hours ago.
> > > >
> > > >         
> > > Did you use -T4 with -A?  Does --traceroute work without -T4?
> > >
> > > Can you find the minimum arguments that can reproduce this problem?
> > > Will just 'nmap --traceroute <host>' do it?
> > >
> > >       
> > Of course I am unable to reproduce it now.
> > I am wondering if it was specific to the environment I was in.
> >     


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