> Hi,
>
> I raised a similar issue sometime back on this mailing list. It
> is basically non-conformance of RFC.
>
> Its not that Linux is sending ACK only packets rather it is
> sending an unacceptable ACK segment forcing the receiver to send
> an ACK. Use Ethereal to view the ACK segments since that will
> show the sequence no. as well.
>
> I feel that it is a bug, but others may not feel the same way.
>
> The clarification/justification I heard in this mailing-list was
> that "this implementation is more interoperable with other
> implementations" compared to "sending zero window probes" as
> defined in RFC793/RFC1122.
>
>
> Regards,
>
> Praveen
Yes. I fixed the client so that it sends ACKs if it receives ACK with
non-matching seq number.
Mikulas
|