From: "David S. Miller" <davem@redhat.com>
To: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Cc: netfilter-devel@lists.netfilter.org, netdev@oss.sgi.com,
usagi-core@linux-ipv6.org
Subject: Re: [PATCH]: invaild TCP/UDP matching when ipv6 extension header exists
Date: Thu, 26 Feb 2004 12:37:32 -0800 [thread overview]
Message-ID: <20040226123732.6132fdbc.davem@redhat.com> (raw)
In-Reply-To: <200402260406.NAA16034@toshiba.co.jp>
On Thu, 26 Feb 2004 13:05:50 +0900 (JST)
Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp> wrote:
> This patch is for linux 2.4.26-pre1 .
>
> Summery:
> tcp_match() and udp_match() in ip6tables.c assume that previous header
> of TCP/UDP header is IPv6 Header. So, for example, 1st of fragmented UDP
> packet, AHed packets can't correctly match the rules which use
> "--sport" and so on.
Also applied, thank you.
prev parent reply other threads:[~2004-02-26 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200401310649.PAA00050@toshiba.co.jp>
2004-02-20 6:12 ` [PATCH]: invaild TCP/UDP matching when ipv6 extension header exists Yasuyuki Kozakai
2004-02-20 17:31 ` David S. Miller
2004-02-26 4:05 ` Yasuyuki Kozakai
2004-02-26 20:37 ` David S. Miller [this message]
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=20040226123732.6132fdbc.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=usagi-core@linux-ipv6.org \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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).