From: "Leonid Zeitlin" <lz@csltd.com.ua>
To: Jan Engelhardt <jengelh@computergmbh.de>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: Invalid SACK numbers in NAT'ed packets
Date: Fri, 25 Apr 2008 14:24:32 +0300 [thread overview]
Message-ID: <015701c8a6c6$ef5d6570$5101a8c0@csltd.intranet> (raw)
In-Reply-To: alpine.LNX.1.10.0804251256530.11644@fbirervta.pbzchgretzou.qr
If I am reading the news correctly, it is available in the latest 2.6.25
kernel, right?
Thanks,
Leonid
----- Original Message -----
From: "Jan Engelhardt" <jengelh@computergmbh.de>
To: "Jozsef Kadlecsik" <kadlec@blackhole.kfki.hu>
Cc: "Leonid Zeitlin" <lz@csltd.com.ua>; <netfilter@vger.kernel.org>;
<netfilter-devel@vger.kernel.org>
Sent: Friday, April 25, 2008 1:57 PM
Subject: Re: Invalid SACK numbers in NAT'ed packets
>
> On Friday 2008-04-25 11:02, Jozsef Kadlecsik wrote:
>
>>On Fri, 25 Apr 2008, Leonid Zeitlin wrote:
>>
>>> It appears that short of writing a custom netfilter extension, there's
>>> no way
>>> to turn off SACKs on a particular connection. Is this right?
>>
>>Yes, exactly. Actually, writing a new extension to erase any TCP option
>>isn't that hard: just replace the option with noop and recalculate the
>>checksum.
>
> There is already a TCPOPTSTRIP target.
>
prev parent reply other threads:[~2008-04-25 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 15:22 Invalid SACK numbers in NAT'ed packets Leonid Zeitlin
2008-04-23 19:31 ` Jozsef Kadlecsik
2008-04-24 9:09 ` Leonid Zeitlin
2008-04-24 9:33 ` Jozsef Kadlecsik
2008-04-25 8:50 ` Leonid Zeitlin
2008-04-25 9:02 ` Jozsef Kadlecsik
2008-04-25 10:57 ` Jan Engelhardt
2008-04-25 11:12 ` Jozsef Kadlecsik
2008-04-25 11:24 ` Leonid Zeitlin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='015701c8a6c6$ef5d6570$5101a8c0@csltd.intranet' \
--to=lz@csltd.com.ua \
--cc=jengelh@computergmbh.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox