From: Patrick McHardy <kaber@trash.net>
To: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
Cc: netfilter-devel@lists.netfilter.org, usagi-core@linux-ipv6.org
Subject: Re: [NETFILTER]: ip6_tables: Support MH match.
Date: Fri, 26 Jan 2007 15:26:06 +0100 [thread overview]
Message-ID: <45BA0F7E.70206@trash.net> (raw)
In-Reply-To: <200701260953.l0Q9rvV8006278@toshiba.co.jp>
Yasuyuki KOZAKAI wrote:
> Hi, Patrick and all,
>
> This introduces match for Mobility Header (MH) described by Mobile IPv6
> specification (RFC3775). User can specify the MH type or its range to be
> matched.
>
> MH is defined as extention header in RFC3775, but this patch handles it
> as layer 4 protocol header like ICMPv6 header.
>
> The reasons are
> - The reason why it's defined as extentin header is mainly for
> 'piggy back'. But that feature was not specified in RFC3775 after all.
> - No header follow MH. RFC3775 says
> Implementations conforming to this specification SHOULD set
> the payload protocol type to IPPROTO_NONE (59 decimal).
> - Many parts in RFCs assume that it's like layer 4 protocol header.
> - Actually Linux IPv6 stack, XFRM, setkey, iproute2... handle it as if
> it's layer4 protocol.
>
> So we concludes people expect to do 'ip6tables -p mh ...', not
> 'ip6tables -m mh ...'.
>
> Please consider to apply this. If no objection, I'll commit
> attached the patch for ip6tables as well.
Looks good, I've queued it for 2.6.21. Thanks.
next parent reply other threads:[~2007-01-26 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200701260953.l0Q9rvV8006278@toshiba.co.jp>
2007-01-26 14:26 ` Patrick McHardy [this message]
2007-01-26 9:53 [NETFILTER]: ip6_tables: Support MH match Yasuyuki KOZAKAI
2007-01-27 15:34 ` Rémi Denis-Courmont
[not found] ` <200701290507.l0T57mwf015698@toshiba.co.jp>
2007-01-30 4:23 ` Masahide NAKAMURA
2007-02-01 1:41 ` Yasuyuki KOZAKAI
2007-02-02 11:05 ` Jozsef Kadlecsik
2007-02-09 6:22 ` Masahide NAKAMURA
2007-02-10 8:32 ` Masahide NAKAMURA
2007-02-12 10:09 ` 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=45BA0F7E.70206@trash.net \
--to=kaber@trash.net \
--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).