From: Michael Richardson <mcr@sandelman.ca>
To: Alexander Aring <aar@pengutronix.de>
Cc: linux-wpan@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCHv4 bluetooth-next 3/8] ieee802154: 6lowpan: fix intra pan id check
Date: Tue, 26 Jul 2016 07:24:08 -0400 [thread overview]
Message-ID: <14582.1469532248@obiwan.sandelman.ca> (raw)
In-Reply-To: <4f73efde-c6f8-c7e9-dcc9-1efbf42025cb@pengutronix.de>
Alexander Aring <aar@pengutronix.de> wrote:
> I had some dicussion at IETF that the destination pan id could be
> different than the source pan. So we need to change it "again" to remove
> it. :-)
> On rx side:
> - dst pan id can be everything (also 0xfff?)
> - src pan cannot be 0xffff, which should be filtered before reaching
> packet layer.
> On tx side:
> - We some mechanism to tell the destination pan, we need anyway a
> 6lowpan netlink api, so we could add 802.15.4 6lowpan option on it,
> to change the destination panid per interface.
> Or we do what vlan does:
> # ip link add link eth0 name eth0.100 type vlan id 100
> e.g.
> # ip link add link wpan0 name lowpan0 type lowpan pan id 0xbeef
> which can be handled by ip plugin command stuff.
I suggest that panid be handled in the same way as vlan tags: by creating new
virtual lowpanX interfaces. That requires some work below...
--
] 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 [
next prev parent reply other threads:[~2016-07-26 11:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 21:32 [PATCHv4 bluetooth-next 0/8] ieee802154: pending/new fixes and cleanup/features Alexander Aring
2016-07-06 21:32 ` [PATCHv4 bluetooth-next 1/8] ieee802154: add ieee802154_skb_dst_pan helper Alexander Aring
2016-07-06 21:32 ` [PATCHv4 bluetooth-next 2/8] ieee802154: add ieee802154_skb_src_pan helper Alexander Aring
2016-07-06 21:32 ` [PATCHv4 bluetooth-next 3/8] ieee802154: 6lowpan: fix intra pan id check Alexander Aring
2016-07-23 11:03 ` Alexander Aring
2016-07-25 6:31 ` Alexander Aring
2016-07-26 11:24 ` Michael Richardson
2016-07-26 11:24 ` Michael Richardson [this message]
2016-07-06 21:32 ` [PATCHv4 bluetooth-next 4/8] ieee802154: fix skb get fc on big endian Alexander Aring
2016-07-06 21:32 ` [PATCHv4 bluetooth-next 5/8] 6lowpan: ndisc: set invalid unicast short addr to unspec Alexander Aring
2016-07-06 21:32 ` [PATCHv4 bluetooth-next 6/8] atusb: don't change csma settings while set channel Alexander Aring
2016-07-06 21:32 ` [PATCHv4 bluetooth-next 7/8] ieee802154: cleanup WARN_ON for fc fetch Alexander Aring
2016-07-08 11:23 ` Stefan Schmidt
2016-07-06 21:32 ` [PATCHv4 bluetooth-next 8/8] fakelb: allow to run as monitor Alexander Aring
2016-07-08 11:25 ` Stefan Schmidt
2016-07-08 11:24 ` [PATCHv4 bluetooth-next 0/8] ieee802154: pending/new fixes and cleanup/features Marcel Holtmann
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=14582.1469532248@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=aar@pengutronix.de \
--cc=kernel@pengutronix.de \
--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.