netdev
[Top] [All Lists]

Re: [PATCH] Make netfilter handle SACK in NAT'ed connections (was Re: Fw

To: laforge@xxxxxxxxxxxx (Harald Welte)
Subject: Re: [PATCH] Make netfilter handle SACK in NAT'ed connections (was Re: Fw: oops/bug in tcp, SACK doesn't work?)
From: kuznet@xxxxxxxxxxxxx
Date: Mon, 28 Jan 2002 20:38:32 +0300 (MSK)
Cc: netdev@xxxxxxxxxxx
In-reply-to: <20020127095716.H16571@xxxxxxxxxxxxxxxxxxxxxxx> from "Harald Welte" at Jan 27, 2 09:57:16 am
Sender: owner-netdev@xxxxxxxxxxx
Hello!

> The only question remaining is:  Is it worth the effort?  What do the
> core linux developers think? 

What's about me, I think it is required. There are no reasons to drop sacks,
when you already have code to mangle data.

About complexity... does not matter, "complexity" happens when something
is logically not quite trivial. SACK mangling is just straight hand work
rather than complexity. It is even not long looking at the patch. :-)

Unlike timestamps. Timestamps are better to delete even when not mangling.


BTW what is this?

                        /* Half a match?  This means a partial retransmisison.
                           It's a cracker being funky. */

>From code I cannot guess, what does it mean. Does this mean that NAT can
block some valid data?

Alexey

<Prev in Thread] Current Thread [Next in Thread>