From: Michael Richardson <mcr@sandelman.ca>
To: Alexander Aring <aring@mojatatu.com>
Cc: netdev@vger.kernel.org, linux-wpan@vger.kernel.org,
linux-bluetooth@vger.kernel.org
Subject: Re: netdevice notifier and device private data
Date: Sat, 09 Jun 2018 15:01:18 -0400 [thread overview]
Message-ID: <29706.1528570878@localhost> (raw)
In-Reply-To: <20180609152921.hqfmprmd4ryttaie@x220t>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
Alexander Aring <aring@mojatatu.com> wrote:
> Futhermore user space programs e.g. radvd will do 6lowpan specific
> handling on 6lowpan dev->type, it will not work either on tun
> devices.
> I know that wpantund from NestLabs do this switch, I am very
> curious about the reason but I think they do it because the name
> is 6LoWPAN. But wpantund is just a SLIP like protocol with
> additional radio/foo commands.
How do they change it then, and what does it do?
It totally seems like broken behaviour. Maybe it's not even intentional.
Maybe they are just foobar.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 464 bytes --]
next prev parent reply other threads:[~2018-06-09 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 17:34 netdevice notifier and device private data Alexander Aring
2018-06-08 18:14 ` Stephen Hemminger
2018-06-08 19:41 ` Alexander Aring
2018-06-08 19:37 ` Michael Richardson
2018-06-09 15:29 ` Alexander Aring
2018-06-09 19:01 ` Michael Richardson [this message]
2018-06-10 15:39 ` Alexander Aring
2018-06-11 2:09 ` Michael Richardson
2018-06-12 13:22 ` 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=29706.1528570878@localhost \
--to=mcr@sandelman.ca \
--cc=aring@mojatatu.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@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).