All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Baptiste Clenet <bapclenet@gmail.com>
Cc: Stefan Schmidt <stefan@osg.samsung.com>, linux-wpan@vger.kernel.org
Subject: Re: What is SAM value? "ieee802154 phy0 wpan0: SAM value 0x3 not supported"
Date: Mon, 27 Jul 2015 13:30:58 +0200	[thread overview]
Message-ID: <20150727113054.GE18090@omega> (raw)
In-Reply-To: <CAPpUg6N0K-w_F0My0Wivi7W8MfYee-YSTr=8q2iDuFXFznQbtQ@mail.gmail.com>

On Mon, Jul 27, 2015 at 12:52:42PM +0200, Baptiste Clenet wrote:
> 2015-07-27 12:38 GMT+02:00 Alexander Aring <alex.aring@gmail.com>:
> > On Mon, Jul 27, 2015 at 12:31:28PM +0200, Baptiste Clenet wrote:
> >> 2015-07-27 12:21 GMT+02:00 Alexander Aring <alex.aring@gmail.com>:
> >> > On Mon, Jul 27, 2015 at 12:08:18PM +0200, Baptiste Clenet wrote:
> >> > ...
> >> >>
> >> >> Receiving side:
> >> >> [  176.921637] CID flag is set, increase header with one
> >> >> [  176.931640] NH flag is set, next header carried inline: 02
> >> >> [  176.942502] SAC bit is set. Handle context based source address.
> >> >> [  176.954397]
> >> >> [  176.957352] ieee802154 phy0 wpan0: SAM value 0x3 not supported
> >> >>
> >> >
> >> > Yes this is not what it was transmitted before from the other node.
> >> > That's why I would ask for some sniffing device, somewhere in the lower
> >> > layers mac or phy it will fill your frame with garbage.
> >> >
> >> > I can't tell you now if it's the transmitted node or the receiving node.
> >> > You need to debug it there.
> >> Yeah, I agree.
> >>
> >> >
> >> > To ensure the transmitted node don't send garbage I would like to check
> >> > it with some sniffer device. If you see garbage on the sniffer device
> >> > then it's something wrong with the transmitting.
> >> Ok, but I did sniffing with monitor0 on the receiver as I mentioned earlier.
> >> How may I sniff a packet ont the sender? Because I can't set up
> >> lowpan0 on top of monitor0.
> >> How may I sniff on lower layers?
> >>
> >
> > In short:
> >
> > Monitor is just for sniffing, we don't parse any payload data on it. You
> > can't create a lowpan interface on it, please use the L2 interface
> > (wpan0). See [0], you maybe need a third node which running as monitor.
> 
> I don't think I've got it, you want me to set up a network of 3 nodes with:
> 1            2             3
> sender   receiver    receiver
> wpan0    wpan0      monitor0
> 
> But I will see exactly the same things as earlier.

You can save the dump (e.g. tshark I think with -w $FILE) somewhere or
doing pipe via ssh, refer [0].

I don't know what "But I will see exactly the same things as earlier" I
don't know now if the sender transmit correct things and the receiver do
some garbage then OR the sender already transmit incorrect data.

When you have such dump file you can easily open this dump with
wireshark, wireshark will autodetect the 6LoWPAN header then from the
wpan interface and shows "hopefully" correct 6LoWPAN decompressed data
(IPv6) which should be the same like what lowpan interface shows.

> And I won't sniff phy layer.
> 

Yes, we all don't want to decode the phy layer manually. :D I don't have
the equipment and knowledge for doing this.

- Alex

[0] http://wpan.cakelab.org/#_sniffing

  reply	other threads:[~2015-07-27 11:30 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
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 [this message]
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=20150727113054.GE18090@omega \
    --to=alex.aring@gmail.com \
    --cc=bapclenet@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=stefan@osg.samsung.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.