From: "Leonid Zeitlin" <lz@csltd.com.ua>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter@vger.kernel.org
Subject: Re: Invalid SACK numbers in NAT'ed packets
Date: Fri, 25 Apr 2008 11:50:28 +0300 [thread overview]
Message-ID: <006b01c8a6b1$884da030$5101a8c0@csltd.intranet> (raw)
In-Reply-To: Pine.LNX.4.64.0804241130040.30382@blackhole.kfki.hu
Thanks, Jozsef, I see.
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?
Thanks,
Leonid
----- Original Message -----
From: "Jozsef Kadlecsik" <kadlec@blackhole.kfki.hu>
To: "Leonid Zeitlin" <lz@csltd.com.ua>
Cc: <netfilter@vger.kernel.org>
Sent: Thursday, April 24, 2008 12:33 PM
Subject: Re: Invalid SACK numbers in NAT'ed packets
> On Thu, 24 Apr 2008, Leonid Zeitlin wrote:
>
>> > or use IPV4OPTSTRIP for the SYN packets sent/received in this direction
>> > as
>> > a selective workaround for the problem.
>>
>> What is IPV4OPTSTRIP? How can I get it? It's not in standard iptables
>> (not the
>> one that I have anyway), and I can't find it at the netfilter site
>> either.
>
> It's a target extension which can be found in patch-o-matic-ng. But sorry,
> I mixed up: it strips off IPv4 options and not TCP options, so it'd not
> help.
>
> Best regards,
> Jozsef
> -
> E-mail : kadlec@blackhole.kfki.hu, kadlec@sunserv.kfki.hu
> PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
> Address : KFKI Research Institute for Particle and Nuclear Physics
> H-1525 Budapest 114, POB. 49, Hungary
>
next prev parent reply other threads:[~2008-04-25 8:50 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 [this message]
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
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='006b01c8a6b1$884da030$5101a8c0@csltd.intranet' \
--to=lz@csltd.com.ua \
--cc=kadlec@blackhole.kfki.hu \
--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