[Ns-bugs] [Bug 499] wireshark complains if ack number is nonzero but ACK flag not set

Tue Feb 17 02:29:59 PST 2009

http://www.nsnam.org/bugzilla/show_bug.cgi?id=499

--- Comment #3 from Gustavo J. A. M. Carneiro <gjcarneiro at gmail.com>  2009-02-17 05:29:59 EDT ---
(In reply to comment #2)
> I have some questions about this and the patch.
> 
> - TCP should always set the ACK flag once the connection is synchronized.  So,
> just looking at the trace, it seems that the bug may rather be in not setting
> an ACK flag.

I also tried to always set the ACK flag, but it made things worse (all
connections were not established).  I guess lack of skill on my part.  I have
no idea which approach is better, I am no TCP expert, I am merely responding to
the wireshark warning.  With the patch TCP works equally well (i.e. not very
well, but that is a different story) and wireshark doesn't complain anymore.

> 
> - is the ESP intentional here, or is this an indication of something else that
> may be wrong with the TCP payload?  ESP should not have an SPI that is all
> zeros.
> 

I do not know why wireshark sees ESP.  This is supposed to be just 'dummy'
onoff application data.

-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.