Re: handling multiple MAC instances (multiple address filters)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jul 12, 2017 at 04:00:01PM -0400, Michael Richardson wrote:
> 
> Alexander Aring <alex.aring@xxxxxxxxx> wrote:
>     > Then the discussed stopped after I took a shower and realized we lost
>     > ack handling when going into promiscuous mode... The transceiver will
>     > simple ack every frame which it's received then if we don't stop ack
>     > handling.
> 
> The issue is that with the filters off, we will ack packets aimed at other
> nodes.
> 

ok.

>     > Now, after I looked because RX_SAFE_MODE into af86rf2xx datasheets
>     > again. I think we could try to do the following:
> 
> So don't get too hung up on the limitations of the af86.  It could be that
> it is impossible with that device, but that another device will make it
> possible.
> 

We need to talk about this point, see below.

>     >  - RX done irq comes - Grab buffer information - Doing fast a source
>     > address lookup and check if we have a mac interface currently running
>     > which has the address and ack is requested.  - If so trigger pin to
>     > send ack.  - If not do nothing and drop (because we are not meant)
> 
> This sounds very cool.
> 

ok.

>     > Another question is: Is running multiple interfaces on one PHY the
>     > thing what we "need". I think yes, because the 802.15.4 spec describe
>     > only one source PAN to operate on. Another idea would be to override
> 
> I'd really like to be able to operate on multiple PANs at the same time.
> I think that 6LBRs will need this.
> 

The 802.15.4 SPEC defines "macPANId" where stands:

"The 16-bit identifier of the PAN on which the device is operating. If this value
 is 0xffff, the device is not associated."

So this is for me "we can only have a non-changing _source_ PAN". But
you could run more than one 802.15.4 MAC instances on one 802.15.4 PHY.
Which allows to run multiple wpan interfaces with different source PANs.

Now according to 6LoWPAN interface generation you can specify on which
destination pan you want to operate, or even per sendmsg(2). If not
specified it will use intra-pan communication destination pan == source
pan.

In short: You cannot handle multiple pan support on the same interface,
you need create other interfaces to run on other pans then. Is that what
you are looking for? I know unstrung need to have support to deal with
multiple interfaces then...

- Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux