Re: Why 232 rounds?

["Luis MartinGarcia." <luis.mgarc () gmail com>]

On 10/13/2012 11:30 AM, Fyodor wrote:
> On Fri, Oct 12, 2012 at 10:34 AM, Luis MartinGarcia.
> <luis.mgarc () gmail com> wrote:
> > I am happy to report that as of r30027, the issue Fyodor reported, is
> > fixed. Could you please svn update and try again?
> Thanks Luis.  The "Error opening capture device" error is gone.
> However, when I try to run it as nonroot against scanme.nmap.org port
> 80, I get this repeatable failure starting on the third probe:
>
> [fyodor@hax nmap-npingchanges]$ nping/nping scanme.nmap.org
>
> Starting Nping 0.6.02 ( http://nmap.org/nping ) at 2012-10-13 01:58 PDT
> SENT (0.0000s) Starting TCP Handshake > 74.207.244.221:80
> RECV (0.0200s) Handshake with 74.207.244.221:80 completed
> SENT (1.0010s) Starting TCP Handshake > 74.207.244.221:80
> RECV (1.0230s) Handshake with 74.207.244.221:80 completed
> SENT (2.0010s) Starting TCP Handshake > 74.207.244.221:80
> RECV (2.0010s) Possible TCP RST received from 74.207.244.221:80 -->
> Cannot assign requested address
> SENT (3.0000s) Starting TCP Handshake > 74.207.244.221:80
> RECV (3.0000s) Possible TCP RST received from 74.207.244.221:80 -->
> Cannot assign requested address
> SENT (3.9990s) Starting TCP Handshake > 74.207.244.221:80
> RECV (3.9990s) Possible TCP RST received from 74.207.244.221:80 -->
> Cannot assign requested address
>
> TCP connection attempts: 5 | Successful connections: 2 | Failed: 3 (40.00%)
> Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A
> Tx time: 3.99832s | Tx bytes/s: 0.00 | Tx pkts/s: 0.00
> Rx time: 4.99908s | Rx bytes/s: 0.00 | Rx pkts/s: 0.00
> Nping done: 1 IP address pinged in 5.14 seconds
>
>
> I'm not sure if this is due to trying to bind the same source address
> or what.  But it doesn't happen for me with the trunk nping:
>
> [fyodor@hax nmap]$ nping/nping scanme.nmap.org
>
> Starting Nping 0.6.02 ( http://nmap.org/nping ) at 2012-10-13 01:59 PDT
> SENT (0.0178s) Starting TCP Handshake > scanme.nmap.org:80 (74.207.244.221:80)
> RECV (0.0395s) Handshake with scanme.nmap.org:80 (74.207.244.221:80) completed
> SENT (1.0198s) Starting TCP Handshake > scanme.nmap.org:80 (74.207.244.221:80)
> RECV (1.0414s) Handshake with scanme.nmap.org:80 (74.207.244.221:80) completed
> SENT (2.0218s) Starting TCP Handshake > scanme.nmap.org:80 (74.207.244.221:80)
> RECV (2.0436s) Handshake with scanme.nmap.org:80 (74.207.244.221:80) completed
> SENT (3.0248s) Starting TCP Handshake > scanme.nmap.org:80 (74.207.244.221:80)
> RECV (3.0472s) Handshake with scanme.nmap.org:80 (74.207.244.221:80) completed
> SENT (4.0268s) Starting TCP Handshake > scanme.nmap.org:80 (74.207.244.221:80)
> RECV (4.0462s) Handshake with scanme.nmap.org:80 (74.207.244.221:80) completed
>
> Max rtt: 22.394ms | Min rtt: 19.456ms | Avg rtt: 21.426ms
> TCP connection attempts: 5 | Successful connections: 5 | Failed: 0 (0.00%)
> Tx time: 4.01011s | Tx bytes/s: 99.75 | Tx pkts/s: 1.25
> Rx time: 4.02957s | Rx bytes/s: 49.63 | Rx pkts/s: 1.24
> Nping done: 1 IP address pinged in 4.05 seconds
>
>
> Cheers,
> Fyodor

Hi,

I couldn't reproduce the problem. However, I think I've fixed it in
r30030. It was probably being caused by a sockaddr_storage structure
that wasn't being properly initialized. Can you please svn up and try again?

Regards,

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