| To: | David Stevens <dlstevens@xxxxxxxxxx> |
|---|---|
| Subject: | Re: MLD compatibility mode doesn't account for extension headers [PATCH] |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Fri, 21 Nov 2003 16:46:21 -0800 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <OF7F1DDE00.E61D92DC-ON88256DE6.00004F45@xxxxxxxxxx> |
| References: | <OF7F1DDE00.E61D92DC-ON88256DE6.00004F45@xxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Fri, 21 Nov 2003 17:08:07 -0700 David Stevens <dlstevens@xxxxxxxxxx> 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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | MLD compatibility mode doesn't account for extension headers [PATCH], David Stevens |
|---|---|
| Next by Date: | TCP Retx per tcp-flow, bedboi |
| Previous by Thread: | MLD compatibility mode doesn't account for extension headers [PATCH], David Stevens |
| Next by Thread: | Re: MLD compatibility mode doesn't account for extension headers [PATCH], David Stevens |
| Indexes: | [Date] [Thread] [Top] [All Lists] |