TCP RESET after SACK in Kernel 2.6

[Christian Schwarz]

Hi!

We're running a Debian Linux router with masquerading enabled
to access a customers site.  The customer connection has a lot of
packet loss, so we receive some TCP SACK-messages.

Our old system with Debian 3.1 and Kernel 2.4.xx handled this correctly,
but after upgrading to Debian 4.0 and Kenrel 2.6.26.5, sometimes the
SACK-queries are answered with a TCP RESET by the kernel.

Does someone have any hints for me how to fix this?

Background question: we have the following setup:

  client host  ->  router w/ masquerading  ->  target host

When the target host sends a SACK-query, is it the router's job to
resend the packets or is this the client host's job?


Thanks for your help!


Cheers,

Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html