From: Patrick McHardy <kaber@trash.net>
To: Herve Eychenne <rv@wallfire.org>
Cc: Harald Welte <laforge@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: TCPMSS is not restricted to mangle table
Date: Mon, 05 Dec 2005 02:11:37 +0100 [thread overview]
Message-ID: <439393C9.5020001@trash.net> (raw)
In-Reply-To: <20051205004548.GC5617@eychenne.org>
Herve Eychenne wrote:
> On Mon, Dec 05, 2005 at 01:27:09AM +0100, Patrick McHardy wrote:
>
>
>>I just noticed the TCPMSS target is not restricted to the
>>mangle table. Any opinions about whether we should change
>>this, perhaps with a warning period?
>
>
> See the manpage itself... I just copy-pasted the kernel config description
> (probably written by Marc Boucher?) when adding TCPMSS to the manpage
> some years ago.
>
> So look for TCPMSS, notice the given example:
> iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
> -j TCPMSS --clamp-mss-to-pmtu
>
> and realize that most uses of TCPMSS (which I fear are not that
> rare) probably occur within the filter table.
> You can expect a global change to be quite difficult, I guess... :-(
Thanks, I didn't know this, I'm going to change this to refer to
the mangle table. This still leaves the option of a warning, but
want I really wanted to know was whether anyone cares. From a
consistency point of view it should be restricted, for the
functionality it doesn't matter.
next prev parent reply other threads:[~2005-12-05 1:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 0:27 TCPMSS is not restricted to mangle table Patrick McHardy
2005-12-05 0:45 ` Herve Eychenne
2005-12-05 1:11 ` Patrick McHardy [this message]
2005-12-06 4:30 ` Aleksandar Milivojevic
2005-12-06 5:12 ` Patrick McHardy
2006-01-03 7:05 ` Jan Engelhardt
2006-01-03 11:14 ` Patrick McHardy
2006-01-03 11:38 ` Jan Engelhardt
2006-01-06 14:32 ` Harald Welte
2005-12-05 0:55 ` Tom Eastep
2005-12-05 1:33 ` Philip Craig
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=439393C9.5020001@trash.net \
--to=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=rv@wallfire.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.