From: Patrick McHardy <kaber@trash.net>
To: Shan Wei <shanwei@cn.fujitsu.com>
Cc: netfilter-devel@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: Re: [IPTABLES][PATCH 1/2] xt_sctp: Trace DATA chunk that supports
Date: Tue, 08 Jun 2010 12:16:08 +0000 [thread overview]
Message-ID: <4C0E3488.6040402@trash.net> (raw)
In-Reply-To: <4C0BE408.7070606@cn.fujitsu.com>
On 06.06.2010 20:08, Shan Wei wrote:
> 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.
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: Shan Wei <shanwei@cn.fujitsu.com>
Cc: netfilter-devel@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: Re: [IPTABLES][PATCH 1/2] xt_sctp: Trace DATA chunk that supports SACK-IMMEDIATELY extension
Date: Tue, 08 Jun 2010 14:16:08 +0200 [thread overview]
Message-ID: <4C0E3488.6040402@trash.net> (raw)
In-Reply-To: <4C0BE408.7070606@cn.fujitsu.com>
On 06.06.2010 20:08, Shan Wei wrote:
> 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.
Applied, thanks.
next prev parent reply other threads:[~2010-06-08 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-06 18:08 [IPTABLES][PATCH 1/2] xt_sctp: Trace DATA chunk that supports SACK-IMMEDIATELY Shan Wei
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 ` Patrick McHardy [this message]
2010-06-08 12:16 ` 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=4C0E3488.6040402@trash.net \
--to=kaber@trash.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=shanwei@cn.fujitsu.com \
/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.