From: Alexander Aring <alex.aring@gmail.com>
To: Simon Vincent <simon.vincent@xsilon.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: 6lowpan raw socket problems
Date: Tue, 2 Sep 2014 18:26:31 +0200 [thread overview]
Message-ID: <20140902162630.GD15189@omega> (raw)
In-Reply-To: <5405EB08.5040006@xsilon.com>
On Tue, Sep 02, 2014 at 05:06:32PM +0100, Simon Vincent wrote:
> This is not a problem. There is a fix elsewhere for that.
>
> I am using local-link addresses.
>
> I am seeing funny things like:
> lowpan0: received packet from fe80::203:9a00:41:c864 ->
> 7707:ffff:300:0:9a:300:7b3b:3a1a
>
> Src address fe80::203:9a00:41:c864 does not exist on the network and
> destination address 7707:ffff:300:0:9a:300:7b3b:3a1a does not.
>
Where do you capture this? You know that wireshark on a lowpan interface
is broken?
- Alex
next prev parent reply other threads:[~2014-09-02 16:26 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
[not found] <5419ABD6.70607@xsilon.com>
2014-09-17 15:43 ` Simon Vincent
2014-09-18 7:46 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
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
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=20140902162630.GD15189@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).