From: "David S. Miller" <davem@redhat.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: netdev@oss.sgi.com
Subject: Re: MLD compatibility mode doesn't account for extension headers [PATCH]
Date: Fri, 21 Nov 2003 16:46:21 -0800 [thread overview]
Message-ID: <20031121164621.277f283d.davem@redhat.com> (raw)
In-Reply-To: <OF7F1DDE00.E61D92DC-ON88256DE6.00004F45@us.ibm.com>
On Fri, 21 Nov 2003 17:08:07 -0700
David Stevens <dlstevens@us.ibm.com> wrote:
> The MLD v1 compatibility mode checks don't account for the
> fact that extension headers are included in the ipv6 payload_len field.
> That makes MLDv1 queries that include extension headers (like
> Router Alert) appear to be v2 packets.
> The below patch fixes the problem.
Looks good. I assume that all extension headers must appear
_before_ the igmp stuff, and therefore no other headers may
appear afterwards.
I'll apply this, thanks.
next prev parent reply other threads:[~2003-11-22 0:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-22 0:08 MLD compatibility mode doesn't account for extension headers [PATCH] David Stevens
2003-11-22 0:46 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-22 2:29 David Stevens
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=20031121164621.277f283d.davem@redhat.com \
--to=davem@redhat.com \
--cc=dlstevens@us.ibm.com \
--cc=netdev@oss.sgi.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 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).