All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: Mark Butsch <Mark.Butsch@myfuelmaster.com>,
	"linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: Re: things not working - newbie questions
Date: Tue, 30 Mar 2021 09:30:07 +0200	[thread overview]
Message-ID: <a993264a-8bc5-586b-5dac-34d50adfe7b2@datenfreihafen.org> (raw)
In-Reply-To: <SN6PR01MB364865A6E7BF0E559808BD9587649@SN6PR01MB3648.prod.exchangelabs.com>

Hello.

On 23.03.21 22:14, Mark Butsch wrote:
> Hello,
> 
> Sorry if this has all been asked before.
> 
> I am trying to setup a 6lowpan network using a Raspberry Pi 400 and Atmel REB233-XPRO modules (AT86RF233). I have 2 of each.
> 
> I have wired the radio modules to the Raspberry Pi GPIO connector.
> 
> If have created a device tree overlay that I think works when applied because I see this in the dmesg output:
> 
> [   36.388574] at86rf230 spi0.0: Detected at86rf233 chip version 2
> 
> I have installed 'wpan-tools' and 'lowpan-tools'

You will need wpan-tools only. lowpan tools is deprecated for a long 
time now.

> 
> I get what looks like good output when I run:
> 
> $ iwpan dev wpan0 info
> Interface wpan0
>          ifindex 4
>          wpan_dev 0x1
>          extended_addr 0xc62e26eced5de562
>          short_addr 0xffff
>          pan_id 0xffff
>          type node
>          max_frame_retries 3
>          min_be 3
>          max_be 5
>          max_csma_backoffs 4
>          lbt 0
>          ackreq_default 0
> 
> I tried to setup a 6lowpan network (based on things I googled) but pings didn't work, so I am starting over trying to confirm the lower level parts are working first.
> 
> I set the pan_id to 0xabba on both systems.
> 
> I set the short_addr to 0x0001 on one and 0x0002 on the other.
> 
> When I try using wpan-ping (from 0x0001), I get:
> 
> $ wpan-ping -a 0x0002 -c 5
> PING 0x0002 (PAN ID 0xabba) 5 data bytes
> Hit 500 ms packet timeout
> Hit 500 ms packet timeout
> Hit 500 ms packet timeout
> Hit 500 ms packet timeout
> Hit 500 ms packet timeout

Do you actually run wpan-ping in server mode on the other node? Without 
it there would be no reply. Its different from the normal ping utility.

> I used "ip link set wpan0 up" (on both systems) and the result is the same, but I can see packets in wireshark on wpan0.
> 
> A hardware person here suggested using a near field probe to see if we could detect any transmission. We didn't. So I don't know if the radios are actually transmitting.
> 
> Any suggestions on where to go next?

For wpan-ping you need to ahve the server on the other node as stated above.

For your 6lowpan ping6 problem I have not enough description of the 
actual problem to help you.

regards
Stefan Schmidt

  reply	other threads:[~2021-03-30  7:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 21:14 things not working - newbie questions Mark Butsch
2021-03-30  7:30 ` Stefan Schmidt [this message]
2021-04-08 13:59 Mark Butsch
2021-04-08 16:46 ` Alexander Aring
2021-04-09 13:29   ` Mark Butsch
2021-04-09 14:27     ` Alexander Aring
2021-04-09 16:59       ` Mark Butsch
2021-04-12 12:28         ` Alexander Aring
2021-04-12 13:20           ` Mark Butsch

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=a993264a-8bc5-586b-5dac-34d50adfe7b2@datenfreihafen.org \
    --to=stefan@datenfreihafen.org \
    --cc=Mark.Butsch@myfuelmaster.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.