From: Vlad Yasevich <vyasevic@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Ben Greear <greearb@candelatech.com>,
Erik Hugne <erik.hugne@ericsson.com>,
netdev@vger.kernel.org, kaber@trash.net, ataschner@suse.com
Subject: Re: [MacVLAN] failure to deliver reassembled IPv6 multicast traffic
Date: Fri, 15 Feb 2013 21:25:24 -0500 [thread overview]
Message-ID: <511EEE14.8050902@redhat.com> (raw)
In-Reply-To: <1360956930.19353.24.camel@edumazet-glaptop>
On 02/15/2013 02:35 PM, Eric Dumazet wrote:
> On Fri, 2013-02-15 at 11:27 -0800, Ben Greear wrote:
>
>> For some reason I was thinking this wasn't fully fixed for IPv4, but
>> maybe it is..the bug in our internal tracker only mentions IPv6
>> as having issues...
>>
>> We'll do some testing on IPv4 sometime soon to make sure, and can test
>> IPv6 patches as well...
>
> This worries me a bit, as I wrote this patch because you reported the
> issue.
>
> commit bc416d9768aa9a2e46eb11354a9c58399dafeb01
> Author: Eric Dumazet <eric.dumazet@gmail.com>
> Date: Thu Oct 6 10:28:31 2011 +0000
>
> macvlan: handle fragmented multicast frames
>
> Fragmented multicast frames are delivered to a single macvlan port,
> because ip defrag logic considers other samples are redundant.
>
> Implement a defrag step before trying to send the multicast frame.
>
> Reported-by: Ben Greear <greearb@candelatech.com>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
>
Yep, IPv4 is there. IPv6 is not and is a lot harder/more interesting
since IPv6 may be disable, but reassembly may still need to work to
service the taps connected to VMs. :(
The only reason I say this is because I've ran into too many people who
turn IPv6 off for "security reasons".
-vlad
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-02-16 2:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 17:00 [MacVLAN] failure to deliver reassembled IPv6 multicast traffic Erik Hugne
2013-02-15 18:08 ` Eric Dumazet
2013-02-15 19:07 ` Ben Greear
2013-02-15 19:18 ` Eric Dumazet
2013-02-15 19:27 ` Ben Greear
2013-02-15 19:35 ` Eric Dumazet
2013-02-16 2:25 ` Vlad Yasevich [this message]
2013-02-16 2:57 ` Vlad Yasevich
2013-02-16 8:48 ` Erik Hugne
2013-02-19 22:22 ` Ben Greear
2013-02-19 22:37 ` Ben Greear
2013-02-19 22:38 ` Eric Dumazet
2013-02-19 22:47 ` Ben Greear
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=511EEE14.8050902@redhat.com \
--to=vyasevic@redhat.com \
--cc=ataschner@suse.com \
--cc=eric.dumazet@gmail.com \
--cc=erik.hugne@ericsson.com \
--cc=greearb@candelatech.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
/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.