From: Alexander Aring <alex.aring@gmail.com>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: Simon Vincent <simon.vincent@xsilon.com>,
linux-wpan@vger.kernel.org, marcel@holtmann.org
Subject: Re: [PATCH linux-wpan v4] ieee802154: 6lowpan: ensure header compression does not corrupt ipv6 header
Date: Wed, 24 Sep 2014 09:11:57 +0200 [thread overview]
Message-ID: <20140924071156.GA24530@omega> (raw)
In-Reply-To: <1411542601.4860.85.camel@jrissane-mobl.ger.corp.intel.com>
On Wed, Sep 24, 2014 at 10:10:01AM +0300, Jukka Rissanen wrote:
> Hi Alex,
>
> On ti, 2014-09-23 at 16:43 +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.
>
> Yes, I know. I was just saying that IFF_MULTICAST is not set for the
> interface in current Bluetooth 6lowpan implementation. This will be
> fixed for sure.
>
Okay. :-)
- Alex
next prev parent reply other threads:[~2014-09-24 7:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 15:52 [PATCH linux-wpan v4] ieee802154: 6lowpan: ensure header compression does not corrupt ipv6 header Simon Vincent
2014-09-22 16:21 ` Alexander Aring
2014-09-22 17:02 ` Alexander Aring
2014-09-23 9:13 ` Jukka Rissanen
2014-09-23 9:26 ` Alexander Aring
2014-09-23 9:35 ` Alexander Aring
2014-09-23 10:14 ` Jukka Rissanen
2014-09-23 10:33 ` Alexander Aring
2014-09-23 10:45 ` Jukka Rissanen
2014-09-23 15:23 ` Marcel Holtmann
2014-09-23 15:36 ` Alexander Aring
2014-09-23 16:19 ` Marcel Holtmann
2014-09-24 9:47 ` Alexander Aring
2014-09-24 9:55 ` Marcel Holtmann
2014-09-24 10:04 ` Alexander Aring
2014-09-24 12:24 ` Marcel Holtmann
2014-09-24 12:49 ` Alexander Aring
2014-09-23 14:20 ` Jukka Rissanen
2014-09-23 14:43 ` Alexander Aring
2014-09-23 15:03 ` Alexander Aring
2014-09-24 7:10 ` Jukka Rissanen
2014-09-24 7:11 ` Alexander Aring [this message]
2014-09-23 10:16 ` Jukka Rissanen
2014-09-22 17:20 ` Alexander Aring
2014-09-24 9:50 ` Alexander Aring
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=20140924071156.GA24530@omega \
--to=alex.aring@gmail.com \
--cc=jukka.rissanen@linux.intel.com \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=simon.vincent@xsilon.com \
/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.