Re: Who is testing the new Nmap IPv6 support

[David Fifield <david () bamsoftware com>]

On Mon, Jun 13, 2011 at 12:09:31PM +0200, Luis MartinGarcia. wrote:
> On 06/13/2011 11:49 AM, Vlatko Kosturjak wrote:
> > On Sat, Jun 11, 2011 at 03:08:50AM -0700, Fyodor wrote:
> > > When we released the new IPv6 improvements (Nmap 5.52.IPv6.Beta2) on
> > > Wednesday we received tons of attention on the social networks, but
> > > very few bug reports.  Maybe that means it is working great for
> > > everyone, or perhaps it means that more people retweeted it than
> > > actually try it.  Is anyone here using the IPv6 suppport and can you
> > > post a description of how it is working for you?
> > Since you asked :) It's not IPv6 related, but IPv4. New Nmap is 
> > crashing on OS detection.
> >
> > Nmap version
> > ============
> > $ nmap --version
> > Nmap version 5.52.IPv6.Beta2 ( http://nmap.org )
> > Platform: i686-pc-linux-gnu
> > Compiled with: liblua-5.1.4 openssl-1.0.0d libpcre-8.12 nmap-libpcap-1.1.1 nmap-libdnet-1.12 ipv6
> > Compiled without:
> >
> > Command line
> > ============
> > nmap -PN -p-65535 --max-hostgroup 16 -sT -sV --webxml -T4 -v -O -oA o -iL i
> >
> > Last interesting lines
> > ======================
> > Initiating Service scan at 10:28
> > Scanning 301 services on 16 hosts
> > Service scan Timing: About 22.92% done; ETC: 10:31 (0:01:54 remaining)
> > Service scan Timing: About 56.81% done; ETC: 10:32 (0:01:36 remaining)
> > Service scan Timing: About 80.73% done; ETC: 10:32 (0:00:37 remaining)
> > Completed Service scan at 10:33, 290.58s elapsed (301 services on 16 hosts)
> > Initiating OS detection (try #1) against 16 hosts
> > Wrong probe number (0) passed to sendT1_7Probe()
> > QUITTING!
>
> This is my fault. I recently removed some piece of code from osscan2.cc
> that appeared to be dead. Although I tested it three times, obviously I
> was wrong and the code is actually run in certain situations. Revision
> 23917 should fix the problem. Vlatko, could you please test if it does?

Vlatko, can you get a stack trace from the assertion failure? I asked
Luis to remove the relevant code and I too am surprised that it is being
called.

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