Re: "encryption failed" warnings in dmesg

[anton@picapica.im]

On Sun, Mar 11, 2018 at 09:34:39AM -0400, Alexander Aring wrote:
> 
> > Seems working so far, at least instances are able to see each
> > other, pair up and even occasionally ping each other from CLI.
> 
> be prepared that the kernel will filter some stuff, you should change
> it that it will not do it. I think we would accept a patch to make
> that possible. The kernel is filtering -> you don't running a user
> space stack.

I tried to remove llsec_encrypt/llsec_decrypt from kernel, recompiled/rebooted,
pings started passing only after that, but still not all IPv6 addresses are pingable.
Seems that half of the packets are still filtered out somewhere.
What could be the other possible places in kernel where raw packets can be dropped?

Now I am trying to compare tcpdump dumps from both devices, with "node" type interfaces.

> 
> > Maybe more proper way is to set everything over netlingk,
> > but seems that extended addr cannot be changed on the fly anyway,
> > without bringing interface down
> >
> 
> The reason why we don't change address filtering at runtime is that we
> are in RX mode and we don't change RX parameters when we are in
> receive mode. If OpenThread, RIOT, etc. do that it's fine, but I see
> problems with that.
> 
> - Alex