Hi, On Sat, Mar 10, 2018 at 12:29 PM, <anton@xxxxxxxxxxx> wrote: > On Wed, Mar 07, 2018 at 10:43:09AM -0500, Alexander Aring wrote: > >> >> You need to use monitor interfaces to make it somehow working but be prepared: >> >> 1. no hardware address filtering >> 2. no hardware ack handling >> >> Have fun! >> > > Thank you for detailed answer, can you give more info about why monitor interface is > required? > There exists two filter mechanism: - Hardware (e.g. address filter, CRC, etc.) - Software (e.g. address filter, CRC, etc.) Of course we do it again in Software, because we don't trust hardware filters... Anyway advantage of hardware filters is only: you get less IRQs With monitor interfaces you disable hardware side and Software side as well... (CRC on tx not, but this is another issue which we cannot change directly..., because UAPI changes. Anyway we need to fix this mess somehow). NOW... some feature which I have in my mind but doesn't exists yet... Disable Software filter and enable Hardware filters... Then using RAW sockets... _IMPORTANT_ Then address settings of user space stacks e.g. OpenThread, RIOT need to be in sync with Hardware (which is possible by doing some netlink foo). Anyway this goes too far for me and is a use case for running user space stacks only, which means: I don't like it, but I think we could accept such feature... It's just node interface without monitor... - 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
