Wrong congestion-window when sequence numbers wrap around

[Christoph Paasch]

When the sequence numbers wrap around, the owin-max value is incorrect.

This is because u_long is used inside tcptrace everywhere. On 64-bit arches this makes a 8-byte variable. Thus, wrap-arounds are incorrectly handled. tcptrace should rather use u_int32_t when handling sequence numbers.

I am ready to submit patches, but where is the development of tcptrace going on?

Cheers,
Christoph

[gobble (gobbledegeek)]

I am looking at a suspicious max_owin figure right now on tcptrace. How can I confirm if it is this bug?

max owin: 18446744069415090185 bytes
avg owin: 253448508186350 bytes
wavg owin: 46856436230412512 bytes

[Christoph Paasch (christoph-paasch)]

Looking at your values of owin, I think you can be sure that you are affected by the bug.