From: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
To: Patrick McHardy <kaber@trash.net>
Cc: Jan Engelhardt <jengelh@medozas.de>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>,
Linux Networking Developer Mailing List <netdev@vger.kernel.org>
Subject: Re: [PATCH] iptables/man: IPv6 TOS mangling fix was backported to 2.6.35-longterm too
Date: Wed, 24 Aug 2011 11:55:54 +0900 [thread overview]
Message-ID: <1314154554.1878.7.camel@nausicaa> (raw)
In-Reply-To: <1312246840.8407.2.camel@nexus.oss.ntt.co.jp>
Fernando Luis Vázquez Cao wrote:
> Update man page accordingly.
>
> Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
> ---
>
> diff -urNp iptables-orig/extensions/libxt_TOS.man iptables/extensions/libxt_TOS.man
> --- iptables-orig/extensions/libxt_TOS.man 2011-07-11 17:41:10.000000000 +0900
> +++ iptables/extensions/libxt_TOS.man 2011-08-02 09:59:27.356614494 +0900
> @@ -28,9 +28,9 @@ Binary XOR the TOS value with \fIbits\fP
> \fIbits\fP\fB/0\fP. See NOTE below.)
> .PP
> NOTE: In Linux kernels up to and including 2.6.38, with the exception of
> -longterm releases 2.6.32.42 (or later) and 2.6.33.15 (or later), there is a bug
> -whereby IPv6 TOS mangling does not behave as documented and differs from the
> -IPv4 version. The TOS mask indicates the bits one wants to zero out, so it needs
> -to be inverted before applying it to the original TOS field. However, the
> +longterm releases 2.6.32 (>=.42), 2.6.33 (>=.15), and 2.6.35 (>=.14), there is
> +a bug whereby IPv6 TOS mangling does not behave as documented and differs from
> +the IPv4 version. The TOS mask indicates the bits one wants to zero out, so it
> +needs to be inverted before applying it to the original TOS field. However, the
> aformentioned kernels forgo the inversion which breaks --set-tos and its
> mnemonics.
Ping?
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-08-24 2:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 0:41 [PATCH 1/2] netfilter: IPv6: initialize TOS field in REJECT target module pablo
2011-06-06 0:41 ` [PATCH 2/2] netfilter: IPv6: fix DSCP mangle code pablo
2011-06-06 13:44 ` Maciej Żenczykowski
2011-06-06 14:41 ` Jan Engelhardt
2011-06-16 8:36 ` [PATCH] iptables: document IPv6 TOS mangling bug in old Linux kernels Fernando Luis Vazquez Cao
2011-06-16 15:06 ` Jan Engelhardt
2011-06-16 15:15 ` Patrick McHardy
2011-06-17 1:11 ` Fernando Luis Vázquez Cao
2011-06-17 1:14 ` Fernando Luis Vázquez Cao
2011-06-17 3:47 ` Patrick McHardy
2011-08-02 1:00 ` [PATCH] iptables/man: IPv6 TOS mangling fix was backported to 2.6.35-longterm too Fernando Luis Vázquez Cao
2011-08-24 2:55 ` Fernando Luis Vazquez Cao [this message]
2011-08-26 13:16 ` Jan Engelhardt
2011-06-07 1:58 ` [PATCH 2/2] netfilter: IPv6: fix DSCP mangle code Fernando Luis Vázquez Cao
2011-06-07 4:15 ` Maciej Żenczykowski
2011-06-07 4:51 ` Fernando Luis Vázquez Cao
2011-06-07 4:55 ` Fernando Luis Vázquez Cao
2011-06-07 6:03 ` Maciej Żenczykowski
2011-06-06 17:36 ` [stable] [PATCH 1/2] netfilter: IPv6: initialize TOS field in REJECT target module Greg KH
2011-06-07 2:39 ` Fernando Luis Vázquez Cao
2011-06-15 0:11 ` Greg KH
2011-06-15 6:19 ` Fernando Luis Vázquez Cao
2011-06-15 19:25 ` Greg KH
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=1314154554.1878.7.camel@nausicaa \
--to=fernando@oss.ntt.co.jp \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--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).