From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Cc: radvd-devel-l@litech.org, unstrung-hackers@lists.sandelman.ca,
mkl@pengutronix.de, marcel@holtmann.org
Subject: 802.15.4 6LoWPAN ARPHRD changed
Date: Sat, 14 Mar 2015 19:56:21 +0100 [thread overview]
Message-ID: <20150314185620.GA1545@omega> (raw)
Hi,
the 6LoWPAN ARPHRD interface type is changed and will be at linux kernel
version 4.1 or later to: ARPHRD_6LOWPAN, before it was ARPHRD_IEEE802154.
The reason was that a 802.15.4 and 6LoWPAN interface used the same
ARPHRD_IEEE802154 type, that occurs several issues on other applications
which can't decide if it's a 802154 or 6LoWPAN (IPv6) interface.
Since bluetooth 6LoWPAN introduced the ARPHRD_6LOWPAN we also decide
that we using ARPHRD_6LOWPAN now.
The most applications getting the EUI64 address from the interface
by evaluating the ARPHRD_IEEE802154. This should be the same for BT
6LoWPAN and 802.15.4 6LoWPAN, because both uses has an EUI64 address.
Also the applications use-case for BT 6LoWPAN and 802.15.4 6LoWPAN
should be the same. We can also introduce some other mechanism to detect
the L2 interface type of an ARPHRD_6LOWPAN, if this is necessary.
For backwards compability it should be safe to add a:
case ARPHRD_6LOWPAN before or after ARPHRD_IEEE802154.
Example radvd in function update_device_info [0]:
switch (ifr.ifr_hwaddr.sa_family) {
...
case ARPHRD_IEEE802154:
case ARPHRD_6LOWPAN:
...
break;
...
}
But this handling is still a little bit wrong because ARPHRD_IEEE802154
are 802.15.4 interfaces which don't have IPv6 functionality.
Nevertheless I just want to leave a note to current common userspace
applications which evaluating this UAPI value. That's why I cc'ed radvd
and unstrung here.
- Alex
[0] https://github.com/reubenhwk/radvd/blob/master/device-linux.c#L82
reply other threads:[~2015-03-14 18:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150314185620.GA1545@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mkl@pengutronix.de \
--cc=radvd-devel-l@litech.org \
--cc=unstrung-hackers@lists.sandelman.ca \
/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