From: Alexander Aring <alex.aring@gmail.com>
To: Baptiste Clenet <bapclenet@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: What is SAM value? "ieee802154 phy0 wpan0: SAM value 0x3 not supported"
Date: Fri, 24 Jul 2015 10:31:10 +0200 [thread overview]
Message-ID: <20150724083106.GA2655@omega> (raw)
In-Reply-To: <CAPpUg6PNNipdf-kXvy9EOo6_8HtauGXMR0WAjXG_gY82DQEY_g@mail.gmail.com>
Hi,
On Fri, Jul 24, 2015 at 09:56:49AM +0200, Baptiste Clenet wrote:
> Hi,
>
> What is SAM value? I got "ieee802154 phy0 wpan0: SAM value 0x3 not
> supported" when I receive a ping from another board.
>
I think you hit [0]. You got that because we received some 6LoWPAN frame
with context based address compression (the source address). See also [1].
Your options are:
- That the other board use stateless (means SAC = 0, see [1]) address
compression.
- Implement context based address compression, there was recently a
RFC patch series which implemented it. This maybe depends also for
handling 6CO field correctly.
- Alex
[0] http://lxr.free-electrons.com/source/net/6lowpan/iphc.c#L147
[1] https://tools.ietf.org/html/rfc6282#section-3.1
next prev parent reply other threads:[~2015-07-24 8:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 7:56 What is SAM value? "ieee802154 phy0 wpan0: SAM value 0x3 not supported" Baptiste Clenet
2015-07-24 8:31 ` Alexander Aring [this message]
2015-07-24 8:47 ` Baptiste Clenet
2015-07-24 9:02 ` Baptiste Clenet
2015-07-24 9:45 ` Baptiste Clenet
2015-07-24 9:53 ` Alexander Aring
2015-07-24 9:48 ` Alexander Aring
2015-07-24 9:56 ` Baptiste Clenet
2015-07-24 10:18 ` Alexander Aring
2015-07-24 12:03 ` Baptiste Clenet
2015-07-24 12:13 ` Alexander Aring
2015-07-24 12:53 ` Baptiste Clenet
2015-07-24 13:07 ` Alexander Aring
2015-07-24 14:45 ` Baptiste Clenet
2015-07-24 14:51 ` Stefan Schmidt
2015-07-24 15:14 ` Baptiste Clenet
2015-07-24 16:24 ` Stefan Schmidt
2015-07-26 21:03 ` Baptiste Clenet
2015-07-27 8:03 ` Baptiste Clenet
2015-07-27 8:06 ` Baptiste Clenet
2015-07-27 8:32 ` Alexander Aring
2015-07-27 8:58 ` Baptiste Clenet
2015-07-27 9:05 ` Baptiste Clenet
2015-07-27 9:30 ` Alexander Aring
2015-07-27 10:08 ` Baptiste Clenet
2015-07-27 10:21 ` Alexander Aring
2015-07-27 10:31 ` Baptiste Clenet
2015-07-27 10:38 ` Alexander Aring
2015-07-27 10:52 ` Baptiste Clenet
2015-07-27 11:30 ` Alexander Aring
2015-07-27 12:29 ` Baptiste Clenet
2015-07-27 12:42 ` Alexander Aring
2015-07-27 12:45 ` Baptiste Clenet
2015-07-27 15:13 ` Baptiste Clenet
2015-07-27 15:55 ` Baptiste Clenet
2015-07-27 16:35 ` Alexander Aring
2015-07-27 17:28 ` Alexander Aring
2015-07-27 17:43 ` Baptiste Clenet
2015-07-27 19:10 ` 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=20150724083106.GA2655@omega \
--to=alex.aring@gmail.com \
--cc=bapclenet@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox