From: Adika Bintang Sulaeman <firstname.lastname@example.org>
Subject: No device found for binding socket ieee802.15.4
Date: Mon, 28 Mar 2016 22:21:08 +0700 [thread overview]
Message-ID: <CALqexQURMozJfgAeLsBUaO_zRwSiS7ZHQQubuLS5Eoo8BcbjXg@mail.gmail.com> (raw)
Dear all linux-wpan developers and users,
This is my first time exploring 6LoWPAN and I would like to ask you
some questions. Before getting into questions, these are the devices
and set up that I use:
-Raspberry Pi Model B Rev 2
-kernel from bluetooth-next ver 4.5.0-rc5+
After setting up and installing the wpan-tools, I got my interface
work by prompting "ip link show" and there is something like:
3: wpan0 <BROADCAST,NOARP> mtu 123 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ieee802.15.4 ee:3b:07:84:64:8c:2a:71 brd ff:ff:ff:ff:ff:ff:ff
The first thing I notice strange is why after the command "sudo ip
link add link wpan0 name lowpan0 type lowpan" the output in "ip link
show" is a bit different, especially in link/:
7: lowpan0 <BROADCAST,MULTICAST> mtu 1280 qdisc noop state DOWN mode
DEFAULT group default qlen 1
link/ ee:3b:07:84:64:8c:2a:71 brd ff:ff:ff:ff:ff:ff:ff
So this is the FIRST QUESTION:
1. Is that normal/ok to have link/ instead of link/ieee802.15.4?
The second thing I notice strange is after "sudo ip link set wpan0 up"
for both wpan0 and lowpan0, the "ifconfig" command shows that these
network interfaces have "Link encap:UNSPEC". If I'm not mistaken, Link
encap shows the hardware family of the interface, right?
So the SECOND QUESTION is:
2. Is that normal/ok to have Link encap:UNSPEC? Because this thing
makes me suspicious about the next problem that I face.
I tried to run wpan-ping daemon from /wpan-tools/wpan-ping by
prompting "wpan-ping --daemon" but the output is "bind: No such
device". I tried to make my own code to make a server program which
listen to this socket interface. But when binding with bind(), I got
the same error status "No device found".
This leads to my THIRD QUESTION:
3. Why "no device found" appears? The transceiver is attached, the
hardware address exists, the interface is up, and I am able to ping
between two devices using ping6. I am suspicious that the problems
that I ask you before have caused this problem.
Do you know what's wrong here?
Thank you for your time and help
next reply other threads:[~2016-03-28 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 15:21 Adika Bintang Sulaeman [this message]
2016-03-28 15:46 No device found for binding socket ieee802.15.4 Adika Bintang Sulaeman
2016-03-29 8:37 ` Alexander Aring
2016-03-30 1:43 ` Adika Bintang Sulaeman
2016-03-30 8:29 ` Stefan Schmidt
2016-03-30 19:21 ` Adika Bintang Sulaeman
2016-03-30 20:42 ` Stefan Schmidt
2016-03-30 20:49 ` Adika Bintang Sulaeman
2016-03-30 20:58 ` Stefan Schmidt
2016-04-03 17:09 ` Adika Bintang Sulaeman
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.