linux-wpan.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Butsch <Mark.Butsch@myfuelmaster.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: "linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: RE: things not working - newbie questions
Date: Fri, 9 Apr 2021 16:59:39 +0000	[thread overview]
Message-ID: <SN6PR01MB3648864C8E0A272EAC656AEA87739@SN6PR01MB3648.prod.exchangelabs.com> (raw)
In-Reply-To: <CAB_54W4j7G53YT8G32GdM4pNET8i0v9_zkNMe=0dwdfbHvEXFg@mail.gmail.com>

Hello,

> On Friday, April 9, 2021 10:28 AM, Alexander Aring <alex.aring@gmail.com> wrote:
> 
> please tell us all the steps which you are doing with mac802154_hwsim, the
> good part of that I can type it here as exactly what you do and then I can tell
> you why it's not working.

I ran these commands to setup the simulated devices:
-----
modprobe mac802154_hwsim

iwpan dev wpan0 set pan_id 0xbeef
iwpan dev wpan1 set pan_id 0xbeef

iwpan dev wpan0 set short_addr 0x0001
iwpan dev wpan1 set short_addr 0x0002

ip link add link wpan0 name lowpan0 type lowpan
ip link add link wpan1 name lowpan1 type lowpan

ip link set wpan0 up
ip link set wpan1 up

ip link set lowpan0 up
ip link set lowpan1 up
-----

Running ifconfig yielded:
-----
pi@raspberrypi:~ $ ifconfig
lowpan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1280
        inet6 fe80::bcef:ff:fe00:1  prefixlen 64  scopeid 0x20<link>
        inet6 fe80::8847:2953:b010:47c8  prefixlen 64  scopeid 0x20<link>
        unspec 8A-47-29-53-B0-10-47-C8-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 15  bytes 2222 (2.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 19  bytes 2558 (2.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lowpan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1280
        inet6 fe80::308e:2e6b:58a7:1ae0  prefixlen 64  scopeid 0x20<link>
        inet6 fe80::bcef:ff:fe00:2  prefixlen 64  scopeid 0x20<link>
        unspec 32-8E-2E-6B-58-A7-1A-E0-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 15  bytes 2222 (2.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 19  bytes 2558 (2.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wpan0: flags=195<UP,BROADCAST,RUNNING,NOARP>  mtu 123
        unspec 8A-47-29-53-B0-10-47-C8-00-00-00-00-00-00-00-00  txqueuelen 300  (UNSPEC)
        RX packets 27  bytes 2086 (2.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 27  bytes 2383 (2.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wpan1: flags=195<UP,BROADCAST,RUNNING,NOARP>  mtu 123
        unspec 32-8E-2E-6B-58-A7-1A-E0-00-00-00-00-00-00-00-00  txqueuelen 300  (UNSPEC)
        RX packets 27  bytes 2086 (2.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 27  bytes 2383 (2.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
-----


Then I ran "wpan-ping -d"
-----
pi@raspberrypi:~/devicetree $ wpan-ping -d
Server mode. Waiting for packets...
-----

I then opened a 2nd window and ran "wpan-ping -a 0x0001 -c 5 -i wpan0
-----
pi@raspberrypi:~ $ wpan-ping -a 0x0001 -c 5 -i wpan0
PING 0x0001 (PAN ID 0xbeef) 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

--- 0x0001 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss
rtt min/avg/max = 2147483.750/0.000/0.000 ms

pi@raspberrypi:~ $ ifconfig
lowpan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1280
        inet6 fe80::bcef:ff:fe00:1  prefixlen 64  scopeid 0x20<link>
        inet6 fe80::8847:2953:b010:47c8  prefixlen 64  scopeid 0x20<link>
        unspec 8A-47-29-53-B0-10-47-C8-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 31  bytes 3997 (3.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 36  bytes 4405 (4.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lowpan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1280
        inet6 fe80::308e:2e6b:58a7:1ae0  prefixlen 64  scopeid 0x20<link>
        inet6 fe80::bcef:ff:fe00:2  prefixlen 64  scopeid 0x20<link>
        unspec 32-8E-2E-6B-58-A7-1A-E0-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 32  bytes 4069 (3.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 35  bytes 4333 (4.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wpan0: flags=195<UP,BROADCAST,RUNNING,NOARP>  mtu 123
        unspec 8A-47-29-53-B0-10-47-C8-00-00-00-00-00-00-00-00  txqueuelen 300  (UNSPEC)
        RX packets 47  bytes 3460 (3.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 53  bytes 4112 (4.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wpan1: flags=195<UP,BROADCAST,RUNNING,NOARP>  mtu 123
        unspec 32-8E-2E-6B-58-A7-1A-E0-00-00-00-00-00-00-00-00  txqueuelen 300  (UNSPEC)
        RX packets 53  bytes 3529 (3.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 47  bytes 3977 (3.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
-----

I tried it with wpan1 as well:
-----
pi@raspberrypi:~ $ wpan-ping -a 0x0001 -c 5 -i wpan1
PING 0x0001 (PAN ID 0xbeef) 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

--- 0x0001 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss
rtt min/avg/max = 2147483.750/0.000/0.000 ms

pi@raspberrypi:~ $ ifconfig
lowpan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1280
        inet6 fe80::bcef:ff:fe00:1  prefixlen 64  scopeid 0x20<link>
        inet6 fe80::8847:2953:b010:47c8  prefixlen 64  scopeid 0x20<link>
        unspec 8A-47-29-53-B0-10-47-C8-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 32  bytes 4069 (3.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 36  bytes 4405 (4.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lowpan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1280
        inet6 fe80::308e:2e6b:58a7:1ae0  prefixlen 64  scopeid 0x20<link>
        inet6 fe80::bcef:ff:fe00:2  prefixlen 64  scopeid 0x20<link>
        unspec 32-8E-2E-6B-58-A7-1A-E0-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 32  bytes 4069 (3.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 36  bytes 4405 (4.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wpan0: flags=195<UP,BROADCAST,RUNNING,NOARP>  mtu 123
        unspec 8A-47-29-53-B0-10-47-C8-00-00-00-00-00-00-00-00  txqueuelen 300  (UNSPEC)
        RX packets 48  bytes 3504 (3.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 58  bytes 4192 (4.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wpan1: flags=195<UP,BROADCAST,RUNNING,NOARP>  mtu 123
        unspec 32-8E-2E-6B-58-A7-1A-E0-00-00-00-00-00-00-00-00  txqueuelen 300  (UNSPEC)
        RX packets 58  bytes 3554 (3.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 48  bytes 4032 (3.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
-----

I feel I am missing some crucial detail.

Thanks,
Mark


  reply	other threads:[~2021-04-09 16:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08 13:59 things not working - newbie questions 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 [this message]
2021-04-12 12:28         ` Alexander Aring
2021-04-12 13:20           ` Mark Butsch
  -- strict thread matches above, loose matches on Subject: below --
2021-03-23 21:14 Mark Butsch
2021-03-30  7:30 ` Stefan Schmidt

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=SN6PR01MB3648864C8E0A272EAC656AEA87739@SN6PR01MB3648.prod.exchangelabs.com \
    --to=mark.butsch@myfuelmaster.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 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).