All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Erik Hugne <erik.hugne@ericsson.com>
Cc: 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 10:08:10 -0800	[thread overview]
Message-ID: <1360951690.19353.20.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130215170028.GG12219@eerihug-hybrid.ki.sw.ericsson.se>

On Fri, 2013-02-15 at 18:00 +0100, Erik Hugne wrote:
> If macvlan's are configured on a device, IPv6 multicast
> traffic received on the underlying ethernet device is not
> delivered properly to higher layers. Large amounts of packets are lost, and
> the problem seems to get worse the more macvlans are defined
> on top of the device, up to the point where no traffic is delivered
> at all...
> 
> 
> Steps to reproduce (2 hosts required)
> On host 1, set up some macvlans:
> ip link add link eth0 name macvlan0 type macvlan mode bridge
> ip link add link eth0 name macvlan2 type macvlan mode bridge
> ip link add link eth0 name macvlan3 type macvlan mode bridge
> ip link set link dev macvlan0 up
> ip link set link dev macvlan2 up
> ip link set link dev macvlan3 up
> 
> Start a server that binds to ff02::1 scoped to eth0
> ./server6 -sff02::1 -eeth0
> 
> 
> On host 2:
> ./client6 -dff02::1 -eeth0
> 
> 
> This seems to only occur for large (fragmented) IPv6 multicast traffic.
> If you bind to :: instead (-s:: on the server) and send to
> the linklocal address of Host1/eth0, packets are delivered just fine.
> 
> Source for client6/server6 on github:
> git clone git@github.com:Hugne/udp_mc.git

I guess we need to defrag before doing the broadcast,
as we did for IPv4 in commit bc416d9768aa9a2e4
(macvlan: handle fragmented multicast frames)

  reply	other threads:[~2013-02-15 18:08 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 [this message]
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
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=1360951690.19353.20.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=ataschner@suse.com \
    --cc=erik.hugne@ericsson.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.