From: Simon Vincent <simon.vincent@xsilon.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: 6lowpan raw socket problems
Date: Thu, 18 Sep 2014 10:03:15 +0100 [thread overview]
Message-ID: <541A9FD3.2030104@xsilon.com> (raw)
In-Reply-To: <20140918085433.GC3774@omega>
There is just a single mrf24j40 on the host.
Some of the messages are sent to multicast addresses so this could be
causing it!
In particular the multicast address is ff02::1a. (all RPL nodes) I guess
it is likely this has not been implemented in the Linux kernel...
Simon
On 18/09/14 09:54, Alexander Aring wrote:
> On Thu, Sep 18, 2014 at 10:45:15AM +0200, Alexander Aring wrote:
>> On Thu, Sep 18, 2014 at 09:37:40AM +0100, Simon Vincent wrote:
>>> Sorry if I confused you, It is not a fakelb problem I get the same problem
>>> if I run using real 802.15.4 hardware (mrf24j40). The packet is put out by
>>> the driver but also sent to the RAW socket.
>>>
>> Two mrf24j40 on the same host?
> I mean, my theory is that there are two IPv6 _interfaces_ are on the
> same host. Then Linux do some optimization and necessary callbacks for
> replacing 6LoWPAN header header will never called. Linux do this
> optimization because Linux see it's local.
>
> Then doesn't matter if two mrf24j40, fakelb, etc... or some combinations
> of them. :-)
>
> - Alex
next prev parent reply other threads:[~2014-09-18 9:03 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 7:46 6lowpan raw socket problems Simon Vincent
2014-09-18 8:33 ` Alexander Aring
2014-09-18 8:37 ` Simon Vincent
2014-09-18 8:45 ` Alexander Aring
2014-09-18 8:54 ` Alexander Aring
2014-09-18 9:03 ` Simon Vincent [this message]
2014-09-18 9:44 ` Alexander Aring
2014-09-18 9:45 ` Alexander Aring
2014-09-18 14:02 ` Simon Vincent
2014-09-18 14:19 ` Alexander Aring
2014-09-18 15:54 ` Simon Vincent
2014-09-18 16:30 ` Alexander Aring
2014-09-18 16:37 ` Alexander Aring
2014-09-18 17:03 ` Simon Vincent
2014-09-18 17:09 ` Alexander Aring
2014-09-19 8:27 ` Simon Vincent
2014-09-19 9:33 ` Alexander Aring
2014-09-19 9:57 ` Simon Vincent
2014-09-19 10:15 ` Alexander Aring
2014-09-19 10:39 ` Alexander Aring
2014-09-19 11:08 ` Alexander Aring
2014-09-19 11:27 ` Simon Vincent
2014-09-19 11:45 ` Alexander Aring
2014-09-19 11:50 ` Alexander Aring
2014-09-19 11:59 ` Alexander Aring
2014-09-19 12:00 ` Simon Vincent
2014-09-19 12:06 ` Alexander Aring
2014-09-19 12:38 ` Alexander Aring
2014-09-19 12:44 ` Simon Vincent
2014-09-19 12:55 ` Alexander Aring
2014-09-19 12:57 ` Alexander Aring
2014-09-19 14:14 ` Simon Vincent
2014-09-19 14:21 ` Alexander Aring
2014-09-19 14:22 ` Alexander Aring
[not found] <5419ABD6.70607@xsilon.com>
2014-09-17 15:43 ` Simon Vincent
[not found] <1409567774.3120.57.camel@jrissane-mobl.ger.corp.intel.com>
2014-09-01 11:38 ` 6lowpan status Alexander Aring
2014-09-02 6:08 ` Jukka Rissanen
2014-09-02 7:12 ` Alexander Aring
2014-09-02 7:26 ` Alexander Aring
2014-09-02 14:21 ` 6lowpan raw socket problems Simon Vincent
2014-09-02 14:43 ` Alexander Aring
2014-09-02 14:51 ` Simon Vincent
2014-09-02 15:18 ` Alexander Aring
2014-09-02 15:37 ` Alexander Aring
2014-09-02 16:06 ` Simon Vincent
2014-09-02 16:26 ` Alexander Aring
2014-09-02 18:53 ` Martin Townsend
2014-09-08 10:43 ` Alexander Aring
2014-09-17 13:30 ` Simon Vincent
2014-09-17 13:57 ` Alexander Aring
[not found] ` <5419A9DD.5070804@xsilon.com>
2014-09-17 16:03 ` Alexander Aring
2014-09-17 16:17 ` Alexander Aring
2014-09-18 7:55 ` Simon Vincent
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=541A9FD3.2030104@xsilon.com \
--to=simon.vincent@xsilon.com \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@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.