[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130218131901.GA24346@eerihug-hybrid.ki.sw.ericsson.se>
Date: Mon, 18 Feb 2013 14:19:01 +0100
From: Erik Hugne <erik.hugne@...csson.com>
To: YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>
CC: netdev <netdev@...r.kernel.org>, netfilter-devel@...r.kernel.org
Subject: Re: [RFC PATCH net-next (V2, RESENT)] ipv6: Queue fragments per
interface for multicast/link-local addresses.
On Sun, Feb 17, 2013 at 01:44:38AM +0900, YOSHIFUJI Hideaki wrote:
> We should queue fragments for the same link-local address on
> different interfaces (e.g. fe80::1%eth0 and fe80::1%eth1) to the
> different queue, because of nature of addressing architecture.
>
> Similarly, we should queue fragments for multicast on different
> interface to the different queue. This is okay because
> application joins group on speicific interface, and multicast
> traffic is expected only on that interface.
>
Your patch does solve the reassembly problem when macvlans are defined, thanks!
A tad unrelated, but i think there's still some ipv6 multicast filtering
work to be done in the macvlan driver. If you for example join an all scope
mcast address, ff09::1 on macvlan 0 it will implicitly be 'joined' on all
other macvlans aswell..
I can buy that linklocal multicast packets are cloned out to all macvlan devices,
but if a specific prefix is joined on one of them, i dont think it's correct that
all sibling devices should receive that traffic, unless they asked for it.
//E
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists