From: Shan Wei <shanwei@cn.fujitsu.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: [IPTABLES][PATCH 1/2] xt_sctp: Trace DATA chunk that supports SACK-IMMEDIATELY
Date: Sun, 06 Jun 2010 18:08:08 +0000 [thread overview]
Message-ID: <4C0BE408.7070606@cn.fujitsu.com> (raw)
SACK-IMMEDIATELY extension has defined in:
http://tools.ietf.org/html/draft-tuexen-tsvwg-sctp-sack-immediately-03.
And the latest kernel has added a I flag in DATA chunk to support this extension.
So let iptables/netfilter can trace it.
Signed-off-by: Shan Wei<shanwei@cn.fujitsu.com>
---
extensions/libxt_sctp.c | 2 +-
extensions/libxt_sctp.man | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/extensions/libxt_sctp.c b/extensions/libxt_sctp.c
index 441f12e..92bdb07 100644
--- a/extensions/libxt_sctp.c
+++ b/extensions/libxt_sctp.c
@@ -97,7 +97,7 @@ struct sctp_chunk_names {
/*'ALL' and 'NONE' will be treated specially. */
static const struct sctp_chunk_names sctp_chunk_names[]
-= { { .name = "DATA", .chunk_type = 0, .valid_flags = "-----UBE"},
+= { { .name = "DATA", .chunk_type = 0, .valid_flags = "----IUBE"},
{ .name = "INIT", .chunk_type = 1, .valid_flags = "--------"},
{ .name = "INIT_ACK", .chunk_type = 2, .valid_flags = "--------"},
{ .name = "SACK", .chunk_type = 3, .valid_flags = "--------"},
diff --git a/extensions/libxt_sctp.man b/extensions/libxt_sctp.man
index 1ecf05c..01a2e79 100644
--- a/extensions/libxt_sctp.man
+++ b/extensions/libxt_sctp.man
@@ -11,7 +11,7 @@ Chunk types: DATA INIT INIT_ACK SACK HEARTBEAT HEARTBEAT_ACK ABORT SHUTDOWN SHUT
chunk type available flags
.br
-DATA U B E u b e
+DATA I U B E i u b e
.br
ABORT T t
.br
--
1.6.3.3
WARNING: multiple messages have this Message-ID (diff)
From: Shan Wei <shanwei@cn.fujitsu.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: [IPTABLES][PATCH 1/2] xt_sctp: Trace DATA chunk that supports SACK-IMMEDIATELY extension
Date: Mon, 07 Jun 2010 02:08:08 +0800 [thread overview]
Message-ID: <4C0BE408.7070606@cn.fujitsu.com> (raw)
SACK-IMMEDIATELY extension has defined in:
http://tools.ietf.org/html/draft-tuexen-tsvwg-sctp-sack-immediately-03.
And the latest kernel has added a I flag in DATA chunk to support this extension.
So let iptables/netfilter can trace it.
Signed-off-by: Shan Wei<shanwei@cn.fujitsu.com>
---
extensions/libxt_sctp.c | 2 +-
extensions/libxt_sctp.man | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/extensions/libxt_sctp.c b/extensions/libxt_sctp.c
index 441f12e..92bdb07 100644
--- a/extensions/libxt_sctp.c
+++ b/extensions/libxt_sctp.c
@@ -97,7 +97,7 @@ struct sctp_chunk_names {
/*'ALL' and 'NONE' will be treated specially. */
static const struct sctp_chunk_names sctp_chunk_names[]
-= { { .name = "DATA", .chunk_type = 0, .valid_flags = "-----UBE"},
+= { { .name = "DATA", .chunk_type = 0, .valid_flags = "----IUBE"},
{ .name = "INIT", .chunk_type = 1, .valid_flags = "--------"},
{ .name = "INIT_ACK", .chunk_type = 2, .valid_flags = "--------"},
{ .name = "SACK", .chunk_type = 3, .valid_flags = "--------"},
diff --git a/extensions/libxt_sctp.man b/extensions/libxt_sctp.man
index 1ecf05c..01a2e79 100644
--- a/extensions/libxt_sctp.man
+++ b/extensions/libxt_sctp.man
@@ -11,7 +11,7 @@ Chunk types: DATA INIT INIT_ACK SACK HEARTBEAT HEARTBEAT_ACK ABORT SHUTDOWN SHUT
chunk type available flags
.br
-DATA U B E u b e
+DATA I U B E i u b e
.br
ABORT T t
.br
--
1.6.3.3
next reply other threads:[~2010-06-06 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-06 18:08 Shan Wei [this message]
2010-06-06 18:08 ` [IPTABLES][PATCH 1/2] xt_sctp: Trace DATA chunk that supports SACK-IMMEDIATELY extension Shan Wei
2010-06-08 12:16 ` [IPTABLES][PATCH 1/2] xt_sctp: Trace DATA chunk that supports Patrick McHardy
2010-06-08 12:16 ` [IPTABLES][PATCH 1/2] xt_sctp: Trace DATA chunk that supports SACK-IMMEDIATELY extension 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=4C0BE408.7070606@cn.fujitsu.com \
--to=shanwei@cn.fujitsu.com \
--cc=kaber@trash.net \
--cc=linux-sctp@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 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.