Re: ACK is being sent with a sequence of 0 every time.

[James Rogers <jamesmrogers () gmail com>]

I see this sequence number issue as different  than the spurious port
closed bug, that I why I broke it up in a different email.

On Wed, Jun 13, 2012 at 4:16 PM, David Fifield <david () bamsoftware com> wrote:
> On Wed, Jun 13, 2012 at 03:58:28PM -0400, James Rogers wrote:
> > Thanks for the other comment location and the revision log number.  I
> > will read that.
> >
> > I'll try  get_random_u32() there to see what effect that has.
>
> get_random_u32 in the seq field won't do anything to solve this bug. I
> suggest you save that for later. That's only if we decide that sending
> seq=0 all the time for ACK probes is the wrong thing to do.
>
> You're better off doing experiments with tcp_probe_match.
>
> David Fifield
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/