From: Jan Engelhardt <jengelh@medozas.de>
To: kaber@trash.net
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH 2/5] doc: remove claim that TCPMSS is limited to mangle
Date: Tue, 6 Apr 2010 12:52:40 +0200 [thread overview]
Message-ID: <1270551164-2945-3-git-send-email-jengelh@medozas.de> (raw)
In-Reply-To: <1270551164-2945-1-git-send-email-jengelh@medozas.de>
There was no real restriction, and in fact, the kernel module never
had such a limitation in the last years.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
---
extensions/libxt_TCPMSS.man | 5 +----
1 files changed, 1 insertions(+), 4 deletions(-)
diff --git a/extensions/libxt_TCPMSS.man b/extensions/libxt_TCPMSS.man
index b5cb455..ac8fb4e 100644
--- a/extensions/libxt_TCPMSS.man
+++ b/extensions/libxt_TCPMSS.man
@@ -4,10 +4,7 @@ outgoing interface's MTU minus 40 for IPv4 or 60 for IPv6, respectively).
Of course, it can only be used
in conjunction with
\fB\-p tcp\fP.
-It is only valid in the
-.BR mangle
-table.
-.br
+.PP
This target is used to overcome criminally braindead ISPs or servers
which block "ICMP Fragmentation Needed" or "ICMPv6 Packet Too Big"
packets. The symptoms of this
--
1.7.0.2
next prev parent reply other threads:[~2010-04-06 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 10:52 iptables pull: osf and misc Jan Engelhardt
2010-04-06 10:52 ` [PATCH 1/5] doc: libxt_MARK: no longer restricted to mangle table Jan Engelhardt
2010-04-06 10:52 ` Jan Engelhardt [this message]
2010-04-06 10:52 ` [PATCH 3/5] libxt_recent: add a missing space in output Jan Engelhardt
2010-04-06 10:52 ` [PATCH 4/5] doc: add manpage for libxt_osf Jan Engelhardt
2010-04-06 10:52 ` [PATCH 5/5] libxt_osf: import nfnl_osf program Jan Engelhardt
2010-04-06 14:15 ` iptables pull: osf and misc Patrick McHardy
2010-04-06 18:21 ` Jan Engelhardt
2010-04-06 18:26 ` Patrick McHardy
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=1270551164-2945-3-git-send-email-jengelh@medozas.de \
--to=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).