On Tue, Sep 23, 2014 at 04:43:15PM +0200, Alexander Aring wrote: > Hi Jukka, > > On Tue, Sep 23, 2014 at 05:20:42PM +0300, Jukka Rissanen wrote: > > Hi Alex, > > > > On ti, 2014-09-23 at 11:35 +0200, Alexander Aring wrote: > > > Jukka, > > > > > > I/Simon mainly add you here in cc because this bug what Simon fixed here > > > is also inside of bluetooth 6lowpan. > > > > > > I see now [0]. And it seems to me that this also occurs at bluetooth > > > branch. Do you have any questions on how the fix now is? Sorry, but I > > > need to clarify that you understood this issue and you/others prepare a > > > patch for this. > > > > I was trying to test this issue and send multicast packets to Bluetooth > > 6lowpan until I realized that the interface does not have IFF_MULTICAST > > enabled :) So this issue is not valid atm for Bluetooth. > > > > Sorry that confusing me now completely. I don't know how 6LoWPAN > Bluetooth works. But sending MULTICAST packets is part of IPv6 so > 6LoWPAN need the possibility to send MULTICAST packets at L3. > > On L2 (that's 802.15.4) we don't support MULTICAST but we sending > BROADCAST frames out. So we have a LOGICAL MULTICAST over BROADCAST. > See [0]. That's also what the neighbor discovery do when no special multicast address map generation is implemented. So 802.15.4 and bluetooth running at the moment into the default branch which is always the BROADCAST address -> then this is LOGICAL MULTICAST over BROADCAST. Sorry for the upper case words. :-) - Alex [0] http://lxr.free-electrons.com/source/net/ipv6/ndisc.c#L263 -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
