Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Alexander Aring <aar@pengutronix.de>
Cc: Xue Liu <liuxuenetmail@gmail.com>, linux-wpan@vger.kernel.org
Subject: Re: Register two 802.15.4 devices/interfaces in one driver
Date: Thu, 16 Feb 2017 14:44:26 -0500	[thread overview]
Message-ID: <32430.1487274266@obiwan.sandelman.ca> (raw)
In-Reply-To: <193c0df2-d259-9076-c442-5731f6124e50@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]


Alexander Aring <aar@pengutronix.de> wrote:
    > I think the important thing is here (I suppose) the device can somehow
    > handle TWO address filters. Meaning you can operate on TWO source
    > pan-ids and having address filtering on.

I imagine that yes, this is what the device is offering.

    > PAN is not just software if you have address filtering. Sure you can
    > turn off the address filter, but for some transceivers this is only
    > possible to go into promiscuous mode and then you disable all filters.

I think that this is exactly the point: you can (have to) do address
filtering in software if you have turned on promiscuous mode.  If you have
hardware that does this, then you can take the PANID from the hardware.
We could literally overload the entire VLAN process for this as for the
moment, 802.15.4 does not have 802.1Q, but I understand 802.15.10 will
change that.

    > Setting Destination PAN for a 6LoWPAN 802.15.4 interface -> we can talk
    > about that, this is software only. But listen source PAN -> problematic
    > because you change address filter parameter while receiving is on. :-/
    > If you do so, you also could miss some frames from other PANs...

Yes, a good point.
I'm not trying to be dynamic here, but rather to leverage the capabilities of
devices...

--
]               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: 487 bytes --]

  reply	other threads:[~2017-02-16 19:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16  8:56 Register two 802.15.4 devices/interfaces in one driver Xue Liu
2017-02-16 14:36 ` Michael Richardson
2017-02-16 15:55   ` Johann Fischer
2017-02-17 11:05     ` Xue Liu
2017-03-01 17:14       ` Stefan Schmidt
2017-03-06 13:53         ` Xue Liu
2017-03-07 19:04           ` Stefan Schmidt
2017-02-16 18:41   ` Alexander Aring
2017-02-16 19:44     ` Michael Richardson [this message]
2017-02-17  7:26       ` Alexander Aring
2017-02-17 11:01         ` Xue Liu
2017-02-19  7:09           ` Alexander Aring
2017-02-17 16:12         ` Michael Richardson
2017-02-20  8:34           ` 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=32430.1487274266@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=aar@pengutronix.de \
    --cc=linux-wpan@vger.kernel.org \
    --cc=liuxuenetmail@gmail.com \
    /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